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
[TT 1932] CC Turtles (Wireless Disabled) Deadlocks #790
Comments
Also, sorry for being such a pain in the ass Nallar! |
That's a crash, not a deadlock. Looks like something broke a chunk - set the chunkTileEntityMap field to null for some reason? :s |
Signed-off-by: Ross Allan <rallanpcl@gmail.com>
I'm sorry I don't understand what this means, do you want me to set a setting or is it set already? |
It was a note for myself if I look at this issue again later, not something you can fix. A mod is doing something silly. |
Signed-off-by: Ross Allan <rallanpcl@gmail.com>
Gotcha, thanks again nallar. Also how would I tell if it's a crash vs a deadlock? I've read through the log and it really didn't say. |
I was checking the 1.5 line numbers, this is actually caused by a block somewhere which has an invalid ID. |
I've disabled the crafting of wireless modems for turtles and set all wireless ranges to 0 and I'm still having issues with turtle deadlocks in the latest version.
I was able to copy over the region files and load up a test server with the exact same setup (except hardware differences) and have the same deadlock issues.
https://gist.github.com/Drehmini/5822629
I didn't have deadlocks until I upgrade to the 1929 build of TT
The text was updated successfully, but these errors were encountered: