Yeah, I'm not a fan of the Mania style either. They're just the same art style as the Mega Drive games but shinier.
If that's the case, then 2.3 would make modding hard by using Java of all things (which I know where this is going), then this is the first time there would be an option, like in Minecraft with its versions when it comes to modding. It also gives other previous versions a shot and more community-driven servers with no ties to the master server whatsoever. The game would finally be decentralized for good out of developers' foolish actions.
Which, speaking of which, I think the whole reason they switch to Java is because they are aware that they are breaking the GPL rules, so they must have a way to escape this situation, or else they'll be in deep trouble.
You see, every LUA script is technically GPL, and the entire SRB2 is licensed as such; even SSNTails himself said so.
What makes it interesting is when you read the FAQ of the Version 2 of GNU GPL, and it says this:
To add more to the argument, SRB2's C functions are called by LUA, which binds the former. They are connected together.
Nowadays, most LUA mods that use C functions are written within the GPL (addhook as an example is under it), meaning that anything that is created within the derivative work must be GPL-compliant. In other words, mods that use LUA must be free to edit and distributed as such. Otherwise, it is a violation of SRB2's license. Because SRB2's Lua implementation links to SRB2's own GPL-licensed code.
They change it all for the sake of the Reusability rule, which releases GPL-licensed works under different terms. Which, funnily enough, it discourages using said code that was meant to be reused because of an idiotic idea that SRB2 in general is "art-centric" and the mods are "intellectual property" (I'm not making this up, and I won't tell you how stupid it is to claim such, especially when it's based on someone's IP).
Which makes it more ironic that art in general takes and changes all the time, but I digress.
And I know full well that they are aware of this issue since there was a thread about it
https://mb.srb2.org/threads/srb2-add-ons-and-gpl-compliance.41543/. (And to be honest here, it aged like milk considering what we were talking about now, the java thing and are mostly out of emotion).
I think they do it so that they make a way to work around the reusability rule by changing it to a different code that has nothing to do with any of this. Therefore nullifying the threat that they will get sued.