-
Notifications
You must be signed in to change notification settings - Fork 6
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
Neoforge support #90
Comments
This specifically happens on 1.0.7 and previous versions (at least 1.0.5 and below, didn't test 1.0.6) worked so I see no reason to not add neoforge's latest version under the mandatory versions. |
On curseforge it is set to allow neoforge. Is it an issue on loading? |
Yes it is an issue loading because of the forge restrictions you set within the mod itself. |
Darn, I’ll fix that tonight |
This is still an issue, you need to edit the mods.toml to allow neoforge's versions |
you set the forge version to a higher version than what neoforge is forge is 47.2.2, and the latest neoforge version is 47.1.101 |
Alright, I’ll put out a patch tomorrow. Can’t guarantee everything will work perfectly though |
all you'd have to do is rollback to before you made the changes after updating to forge 47.2.2 and publish the mod with the changes and fixes you made AFTER you updated it but staying on the older forge version. i know some of those changes were made due to the forge update, but the major changes like the vertical planks being removed and such should be easy. |
1.0.9 should now run on neoforge |
The version restrictions you have added for forge make it incompatible with neoforge :(
The text was updated successfully, but these errors were encountered: