-
Notifications
You must be signed in to change notification settings - Fork 106
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
Vanilla Crafting Recipes #987
Comments
You need to run forge not vanilla. Check the client and server forge versions and make sure they are the same. I have had issues from different forge versions. Hope this helps |
Thanks for getting back to me. I'm definitely running the same forge version, (35.1.37 for both) as I did have issues with some mods not loading before when the version hadn't updated correctly. The weird thing is when I look in the JAR files, the powersuit recipes are in the same place as the tinker table, yet the powersuit recipes work fine and the tinker table has no recipe. That's mostly what's the confusing part. |
Think I found a fix. You just need to change "powersuits:mpa_workbench" to "powersuits:tinkertable" in the vanilla recipe. |
MPS is here now: https://github.com/lehjr/MachineMusePowersuits (by @lehjr) |
Thanks so much! I'm not totally sure if this is what fixed it, but I made this change amongst a couple others and it decided to start working today! |
I'm currently running a personal modpack server for me and a few friends and I'm having trouble with some of the recipes. I know that a lot of recipes are still work in progress and that's fine, however I cannot craft the tinker table despite checking the JAR and seeing that it does have a vanilla recipe. All my searching brings up 'enabling vanilla recipes' however this option does not appear in my client configs (which is just the mpa-client-only.toml config) and there's no configs at all in the server files. Am I missing something or should these configs exists so that I can enable vanilla recipes?
The text was updated successfully, but these errors were encountered: