-
Notifications
You must be signed in to change notification settings - Fork 103
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
[Bug]: XNet connector in crafting grid freezes game #2188
Comments
This is still an issue in 1.0.3. I went back and checked previous versions and putting XNet items into a crafting grid is fine on 1.0.0 (the advanced connector is craftable, although it looks like just putting anything from XNet into the grid causes problems). The first version where the problem presents is 1.0.1 |
It seems that rolling the sophisticated mods back to the version used in 1.0.0 fixes this issue. |
I also encountered this problem. Link to crash log: |
This happen to me as well. My step to recreate: Modpack version: ATM9 1.0.3 |
Could you please link the upstream issues? |
Sophisticated mods are several updates behind. |
This has been fixed in dev, hence the label. |
Possible Fixes
Yes
Modpack Version
1.0.2
What happened?
I made a fresh install of ATM-9, 1.0.2 using prism launcher on Linux (if that is relevant).
Create a new creative game and give yourself an XNet connector, redstone, diamond, and ender pearl in order to craft the advanced connector.
Switch to survival and try to craft an advanced connector (or just put the regular XNet connector in a crafting grid). The game simulation seems to freeze for 5 to 10 seconds. There is no crash, but all mobs freeze in place and I'm unable to interact with any other inventory or crafting grid, and it is impossible to craft the advanced connector.
This can be a much bigger problem for crafting grids that retain items because the game will freeze every time that is opened until the XNet items can be removed.
This seems to be new within the last couple of releases, because I have used XNet quite a bit in my world without having this problem.
latest.log
No response
Developer reports
No response
The text was updated successfully, but these errors were encountered: