Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Forge version #1231

Merged
merged 1 commit into from
Jul 17, 2023
Merged

Update Forge version #1231

merged 1 commit into from
Jul 17, 2023

Conversation

Mgazul
Copy link
Contributor

@Mgazul Mgazul commented Jul 15, 2023

Fixed incompatibilities caused by changes in forge-47.1.6

@Cheaterpaul
Copy link
Member

Why the hell did they add a breaking change. They fixed it in 47.1.29 but only non functional.

Thanks for bringing this up and implementing this.

@Cheaterpaul Cheaterpaul merged commit 72251e3 into TeamLapen:1.20 Jul 17, 2023
@TelepathicGrunt
Copy link
Contributor

@Cheaterpaul due to Neoforged being a thing and just about all of the staff that was under Lex moved to neo, Lex has now free reign over Forge. To show that no one was holding him back before, he has been merging in PRs without fully testing them or reviewing them. Picture that just about sums up why me and several modders are restricting our Forge version to 47.1.3 and older as these Forge versions are stable. Modpacks are probably going to build against 47.1.3 or the recommended build of 47.1.0 so might as well target this and bee free of anymore future breaking changes that Forge could get
Untitled

@Cheaterpaul
Copy link
Member

Regarding the changes see #1236

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants