ImmersiveMC

ImmersiveMC

2M Downloads

Migrate from Architectury API

hammy275 opened this issue ยท 5 comments

commented

We don't use many features from it; really just events that have analogues in all the modloaders, alongside Architectury API's networking. I plan to use the networking rewrite I did for MC VR API in ImmersiveMC, so the networking code is pretty abstracted as-is.

(Basically) depends on hammy275/mc-vr-api#49

Work should be done to wrap the networking system (which will also be used in #447) before tackling or alongside tackling this issue.

commented

Bumping this up into 1.5.0 Beta 2 for a couple reasons:

  • Architectury API isn't supported in Forge past 1.20.4. While people are still using Forge, I'd like to make sure they can use ImmersiveMC.
  • Would rather get something that requires this many changes out during a beta rather than 1.5.0 proper.
commented

Since I'm doing MC VR API's port away from Architectury API first, I'll be waiting until that's done before starting it for ImmersiveMC. It has a good basis of platform abstractions (mainly the networking) I'll be using in ImmersiveMC.

commented

Version tracking:

  • 1.20.4
  • 1.20.2
  • 1.20.1
  • 1.19.4
  • 1.19.3
  • 1.19.2
  • 1.18.2
commented

Just pushed the 1.20.4 version of this. Note that this does NOT suffer the same bug as hammy275/mc-vr-api#50.

commented

This hasn't been super tested, but it shouldn't need to be, given that most of the testing was done as MC VR API development work. Was still tested a couple times in Fabric dev and NeoForge dev, though, and all is well! If there's any issues, they should be caught by a final pass before the next beta goes out, so I'm marking this as done! ๐ŸŽ‰