search

SpongePowered / Sponge

The SpongeAPI implementation targeting vanilla Minecraft and 3rd party platforms.
MIT License
390 stars 211 forks source link

Transition to Neoforge #4113

Closed Outfit8TSB closed 1 month ago

Outfit8TSB commented 3 months ago

Is this request specific to one implementation of Sponge?

Yes, only SpongeForge

Sponge Version

1.20.4+

What are you requesting?

SpongeForge have to make a Transition to Neoforge.

it's been a while, since the Neoforge Broken Out from forge, we have to note that the following: Neoforge No longer supports forge mods, trying to use SpongeForge on Neoforge is Nearly Impossible as this. we have a better point that the more mods will move on to Neoforge.

We addressed the problem of The Geyser Server Admins, wanting to make a Modded sponge Server still have to keep using Geyser-Standalone if they want to make a Geyser Server. this transition is Necessary as the forge Mods are transitioning to Neoforge.

Forge Downfall has begun. Please Transition it, otherwise, the SpongeAPI Users can't use More Mods and have to stay with Bukkit-Neoforge Hybrid Servers. Many Server-side mods are here, but they are still unfamous.

SawFowl commented 3 months ago

Confirming the problem. Recently I made some statistics on mods for 1.21. On version 1.20.* switching to NeoForge makes no sense in my opinion, but on version 1.21 the situation is just the opposite and switching to NeoForge becomes actually necessary. Without it, there is no point in Sponge.

Zidane commented 3 months ago

I've deleted comments that elect to name calling or attacks on members of the community. Our issue tracker is not the place for it and we will not allow them to occur. If you comment again with that, you will be banned.

Please stick solely to the merits of this potential transition and nothing more.

Outfit8TSB commented 3 months ago

okay, sorry. i was supposed to address the OldForge's Downfall, Not Insulting Someone, Whoops.

Outfit8TSB commented 3 months ago

reading whole Neoforge Repository for a Forge Classes, ill brb

Zidane commented 3 months ago

While I have closed the PR (please review and read my reasons), I won't close this issue. We welcome the discussion especially as it helps to gauge true interest. So long, as stated above, this remains civil without attacks on any community member.

SawFowl commented 3 months ago

I'd like to make a point about PR. I can't call replacing imports a big job. And can it really be called any work? When I made any PR in Sponge, I would check to see if my change would work. That is, I compiled the code and tested how it worked. My PRs were accepted as a result. The operation performed seems to have been done in a notepad. I can't explain this change otherwise. This is not work, but hackwork and banal hype.

Now as for the lack of an official decision on a possible switch to NeoForge. I and most of the servers admins I've talked to don't see the point in supporting LexForge, since that mod loader is already effectively dying, they'd rather use NeoForge. The rest either use Fabric, or they don't care what to use and even vanilla(Spigot/Paper/etc) with datapacks will suit them. As for me specifically, I can say that without this transition I see no point for me in further updating my plugins on Sponge and I will have to turn them into mods on NeoForge, I will simply have no choice but to do so. I will finish upgrading my plugins to API12 soon, but I doubt I will have any point in maintaining them in the future.

I can also say one more thing about Fabric. I don't see the point of supporting it as a server solution. This loader has many limitations and disadvantages, which can of course be mitigated, but it would be too much work. It's not worth it.

Yeregorix commented 1 month ago

We are going to officially support NeoForge. You can follow progress on this PR : https://github.com/SpongePowered/Sponge/pull/4134

Outfit8TSB commented 1 month ago

closing in favor of #4134