Forge above 47.1.3 is not supported
Technici4n opened this issue · 12 comments
for me it dosnt work it crashen on startup if i put in the 15.0.5 version for 1.20.1 15.0.4 works fine
i have the forge version 47.1.3
for me it dosnt work it crashen on startup if i put in the 15.0.5 version for 1.20.1 15.0.4 works fine i have the forge version 47.1.3
Please open an issue and provide the necessary info (the issue template will tell you what).
It's in progress. CF only started offering a NeoForge flag yesterday.
It's not really in progress it's just a continuation of Forge without breaking changes with 1.20.1. It works perfectly fine.
Rollout of NF throughout the launcher ecosystem is in progress.
CF just added file-flagging support, but no launcher support as of yet.
Modrinth added file-flagging but has no launcher anyway (yet).
I don't know the state in other launchers.
It also doesnt even display NeoForge on the website, so Forge users are getting notified of an update as well.
That was actually an upload error that should be fixed. The file is no longer marked as supporting Forge.
At the moment this is how it displays, so oddly enough, there is some type of CurseForge issue occuring here.
It appears the devs did not hear when it was said the Launcher didnt support NeoForge yet...
Great Job bumping the forge dep to an non-existant version, really appreciated...
For those wanting to know:
CurseForge Launcher doesnt support or even allow making NeoForge profiles.
It also doesnt even display NeoForge on the website, so Forge users are getting notified of an update as well.
At the moment this is how it displays, so oddly enough, there is some type of CurseForge issue occuring here.
Well, "kinda". You are right that their launcher does not support it natively yet, but they do support tagging files appropriately.
For the time being, the fixes on top of the last AE2 version supporting Forge 47.1.3 aren't important enough that players need to upgrade right now. And since we switched the dev-env to NeoForge and no longer test on Forge, I declared the new builds as NeoForge only.
The situation may change, and we may start tagging newer builds for both, even though we didn't test them on Forge 47.1.3+ :-(
Depends on how long CF takes to actually add the Launcher support.
Interesting, that was quicker than expected. But I doubt they add launcher support so quickly, right?
