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

Network tile split related issues. #20

Closed
2xsaiko opened this issue Aug 28, 2017 · 14 comments
Closed

Network tile split related issues. #20

2xsaiko opened this issue Aug 28, 2017 · 14 comments
Assignees
Labels

Comments

@2xsaiko
Copy link

2xsaiko commented Aug 28, 2017

Using Minecraft 1.12.1, Forge 14.22.0.2463, Teckle 1.12-5.378-SNAPSHOT.

Placed Sorting Machine, attached to some tubes and chests on either side to test. When I tried to load the world again, this happened: https://hastebin.com/ecorehaxan.md

@darkevilmac
Copy link
Member

1.12.2? That doesn't exist as far as I know 🤔

Having trouble reproducing this. Any chance you can give some more detailed steps or an image?

@TheDeviantCrafter
Copy link

I can confirm the crash. Here's how it happened:

  1. Loaded a singleplayer world
  2. Spawned a sorting machine using JEI
  3. Place the sorting machine on the ground. It was either facing east or west.

This crashed my client, with this crash log: https://hastebin.com/ajoyehajim.py

Loading back into the world gave me this crash: https://hastebin.com/ipovaxabaf.py

I was using 1.12.1, Forge 14.22.0.2462, teckle-1.12-5.363.jar

@darkevilmac
Copy link
Member

darkevilmac commented Aug 28, 2017 via email

@2xsaiko
Copy link
Author

2xsaiko commented Aug 29, 2017

Great. Now I can't reproduce it either, although I did the very same thing now. And yes, you're right, there's no 1.12.2. :P

@2xsaiko
Copy link
Author

2xsaiko commented Aug 29, 2017

There's still definitely some weird stuff going on with saving and loading: https://youtu.be/hw6rIJH4dHs

@darkevilmac
Copy link
Member

darkevilmac commented Aug 29, 2017 via email

@darkevilmac
Copy link
Member

darkevilmac commented Aug 30, 2017

Leaving a note here for myself, working on the weird sorting machine bug and found the source. Not sure how I'm going to go about a fix quite yet.

ItemNetworkAssistant will call onNodePlaced during onNeighbourChange when it cant find a network tile. This is fine in some cases but it results in a sorting machine creating a secondary network when the node is destroyed. This causes a new network to be created that shouldn't exist and with no block to tell it to stop existing it simply stays in limbo, then when serialization is attempted there's an attempt to reference the network tile that doesn't exist which causes an error and eventually a crash.

@darkevilmac
Copy link
Member

Copy of #21

Using Minecraft 1.12.2, Forge 14.22.0.2463, Teckle 1.12-5.378-SNAPSHOT.

When activating a transposer, it doesn't pull an "OH SHIT TECKLE BROKE" message appears in the log. The item might or might not get removed from the attached inventory.

Log: https://hastebin.com/ejabicapuw.md

@darkevilmac
Copy link
Member

I made a bunch of changes in https://ci.elytradev.com/job/elytra/job/Teckle/job/1.12/94/

Please try this version and see if you still have any of these issues (or if anything else pops up)

@darkevilmac darkevilmac self-assigned this Aug 31, 2017
@darkevilmac darkevilmac changed the title Sorting machine crashes client when world is loaded Network tile split related issues. Aug 31, 2017
@2xsaiko
Copy link
Author

2xsaiko commented Aug 31, 2017

Using 5.385 from maven (should be the same as the one on CI?), after saving and loading, this exception occurs (which is similar to the first one I've encountered). Again, this only occurred once, I can't reproduce it again with a new world. Strange. Haven't encountered any other errors though.

@2xsaiko
Copy link
Author

2xsaiko commented Aug 31, 2017

And there's another one, again on loading the world. This time it didn't crash the client entirely, just took all the items out of the attached chest and tubes https://hastebin.com/tazivicoxe.md (might or might not be related to my block, still testing)

And the transposer bug is kind of still there: this occurs because the transposer's bufferData is null (not always, though)

@darkevilmac
Copy link
Member

Was the world that you loaded from the previous version? If so that would probably be why, I hadn't tested with an older world.

@darkevilmac
Copy link
Member

I've made a few changes to fix bugs I've been finding myself.

Try the most recent builds and see if they work.

@darkevilmac
Copy link
Member

Closing due to inactivity, if you find any more issues that haven't been mentioned here please open a new issue.

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

4 participants