Woot factory in multiple chunks looks wired
jkroepke opened this issue ยท 8 comments
Woot version: 0.0.8
I see this behavior after upgrading to latest woot.
Anyway, the factory is working with this glitch.
This is one case where chunkloading doesn't matter. The server thinks that the structure is completely formed which is why the factory works.
But when the client loads the chunk visually, it is not getting the "I'm formed" information.
Unfortunately it is a long-term client update issue that I was trying to fix.
Basically the client isn't being refreshed when the factory forms, in very specific circumstances.
Those being the factory across a chunk boundary and the non-heart chunk being loaded after the heart-chunk. (So the direction that you approach the factory changes the chunk loading order and changes when and if this happens).
I've uploaded a newer version of Woot (0.0.9) which rewrites the underlying multiblock code, this may or may not improve the issue.
However it looks like I need to revisit this again to work out which circumstances you are running into compared to the test scenarios that I had.
FYI: The right chunks with the heart are chunkloaded. The left chunks are loaded unless nobody is in the near.
Factory is up and running.
About the chunk borders, check the initial comment. It's still the same factory. The chunk where the factory looks valid are chunk loaded.
The factory at the left side was visually correct, but not chunkloaded.
From my side this issue is happing, if the controller and heart are in loaded chunks, but part of the factory not.
I think I need to build your exact factory position to see if I can replicate this as it is the only way of understanding why this isn't fixed by the fix.
So is the factory still running at the correct tier but is just visually wrong?
Could you show me a top down shot of your factory as that will let me see the chunk boundaries and possibly give me a hint as to what corner case I've missed.
Just out of interest and nothing to do with your issue, what is the ME connection on the factory heart - just so I don't change code one day and break something that people use.