[Announcement] On Forge/NeoForge

First, I wish GitHub had a proper announcement system, but it's not the end of the world that it doesn't. I won't usually use the release section for non-release things, but I feel this topic is somewhat important enough to warrant making this.

I’ve mentioned this in a comment in one of the commits to this repo, but I want to repeat it here,

Very recently, I learned of the Forge drama and the creation of NeoForge that occurred almost a year ago (I was away from programming when it all happened). ACP and several other AncientMC software utilize Forge-developed tools for many of their processes. Regular Forge is still being developed by LexManos. However, because I expect NeoForge and its components to be more actively worked on in the long run (and because of the toxic reputation associated with Lex), ACP and its related components will be switching to NeoForge-based tools in the future.

This probably won't be a difficult task, but it's a lot of work I don't want to do all at once right now. For now, ACP will still be using Forge. When I get to the next major update (after 0.2.0), I will make the shift gradually as I update each repo in the ACP toolchain.

Thanks,

Mason (moist-mason), Ancient Coder Pack developer