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

[TT 1932] CC Turtles (Wireless Disabled) Deadlocks #790

Closed
Drehmini opened this issue Jun 20, 2013 · 6 comments
Closed

[TT 1932] CC Turtles (Wireless Disabled) Deadlocks #790

Drehmini opened this issue Jun 20, 2013 · 6 comments
Assignees
Labels

Comments

@Drehmini
Copy link

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

@Drehmini
Copy link
Author

Also, sorry for being such a pain in the ass Nallar!

@LunNova
Copy link
Member

LunNova commented Jun 20, 2013

That's a crash, not a deadlock.

Looks like something broke a chunk - set the chunkTileEntityMap field to null for some reason? :s

LunNova added a commit that referenced this issue Jun 20, 2013
Signed-off-by: Ross Allan <rallanpcl@gmail.com>
@Drehmini
Copy link
Author

set the chunkTileEntityMap field to null for some reason?

I'm sorry I don't understand what this means, do you want me to set a setting or is it set already?

@LunNova
Copy link
Member

LunNova commented Jun 20, 2013

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.

LunNova added a commit that referenced this issue Jun 20, 2013
Signed-off-by: Ross Allan <rallanpcl@gmail.com>
@Drehmini
Copy link
Author

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.

@ghost ghost assigned LunNova Jun 20, 2013
@LunNova
Copy link
Member

LunNova commented Jun 20, 2013

I was checking the 1.5 line numbers, this is actually caused by a block somewhere which has an invalid ID.

LunNova added a commit that referenced this issue Jun 20, 2013
Signed-off-by: Ross Allan <rallanpcl@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants