here i will have status updates me mateys
- Make a master branch with all the very important information soon. right now just using main for development and pushing out to other branches
- Create a v1.0.0 release for NeoForge
v1.0.0 Release. Base features like PvP and explosion protection
vX.Y.Z X being major updates, Y being minor content updates, Z being bugfixes, extremely small changes, and patches
- v1.0.0 - First version
- v1.0.X* - Minor changes for consistency
- v1.1.0 - Add in-game commands for easier use
- v1.1.X* - Polish commands
- v1.2.0 - More features, such as no breaking blocks at all, and perhaps a "whitelist" for players who are and aren't affected by spawn protection and a "blacklist" for people not allowed in spawn
- v1.2.X* - Polish and stabilize features
- v1.3.0 - Probably just more features (undecided)
- v1.3.X - Fixing stuff
- (Continue update cycle until ready for v2, will update plans if i get an idea)
- v2.0.0 - Major update, configurable protection around beacons, scaling to strength, and being able to set more than 1 area for protection
- v2.0.X - Fix stuff that could break
- v2.1.0 - Individual permissions for each protected area, allow players to change their protected areas around beacons (with UI in the beacon)
- v2.1.X - Fix bugs and polish
- (More ideas soon to come when i eventually get through these future updates)
Could end up being multiple iterations if more problems arise*
I have an itzg/minecraft-server docker container that I run to test my mod. I mainly develop for Fabric first, then make a Neoforge variant.
Will create a master branch with all of the detailed information. (might put the .jar files up in there too for easy access)
You can help me test this out. Just make an issue, and i'll whitelist you to my testing server. IP: fab.orcweb.xyz (Fabric) neo.orcweb.xyz (Neoforge)
I hate java