Should be the last thing we do before release, to minimize the amount of time the latest mc-vr-api version isn't compatible with the latest ImmersiveMC.

Either that, or I should just release a minor release that supports the new version. Note that if I do that, I'd have to cherry-pick both the dupe fix and the 1.3.0 changes

Right, we have to do a minor release, since #196 depends on this

Will release 3.0.0 into beta. Once ImmersiveMC 1.3.0 releases, I'll promote it out of beta

Done!