HeatherComputer
commented
2 months ago Pros :
- Less per-version initial implementation
- Less long-term maintenance, as a breaking change in the corelib wouldn't mean needing an additional change to each version
- Ability to run standalone rather than needing minecraft
Cons :
- Possible java versioning issues (the corelib needs to target java 8, and getting that code to reliably work on 21 was alreayd annoying)
- The gui will open in a separate window
- Potential module conflicts if I have to bundle any libraries
HoldYourWaffle
I've had a revelation regarding the gui.
Part of my concerns with a gui were the difficulty of maintaining a full on gui for backup restoration across that many minecraft versions - it's simply not particularly doable.
But what if the gui was able to run completely standalone, and I simply added a button to the world screen on a per-version basis that ran that gui?
This would give the rare selfhosted server owner the ability to run the gui, possibly - but more importantly, would make updating and maintaining this ui a lot nicer.
The biggest concern here though is getting a gui that works reliably on all java versions from 8 to 21. There's also a worry with library bundling - licensing, bloated file size, and module conflicts (java 17+?) are all points of concern.