[UNEXPECTED CHANGE] Updating to 6.0.11-alpha requires downgrading to Forge 47.1.3 #406
Labels
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Team-EnderIO/EnderIO#406
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there an existing issue for this?
Current Behavior
When upgrading from 6.0.7-alpha to 6.0.11-alpha in a game instance running Forge 47.1.43 an in game error message appears indicating that 6.0.11-alpha "requires forge between 47.1.0 and 47.1.3 (inclusive)".
Not exactly a bug; more of an unexpected change resulting from the fix for issue #402.
Expected Behavior
Newer releases continue to support Forge version of previous versions.
Steps To Reproduce
Environment
Anything else?
crash-2023-07-31_05.46.20-fml.txt
latest.log
Let me check with the dev team, but I think this might be intentional, as Forge pushed a bunch of breaking changes after 47.1.3
Looks like it was commit
832a3b3d49it is intentional, because MinecraftForge has a few breaking changes since 47.1.3 and we don't want to deal with worlds not loading, game crashes, etc.