Create

Create

86M Downloads

Harvester contraption becomes "broken" in certain chunks

Malien opened this issue ยท 3 comments

commented

Originally I found an issue close to what I'm having (#1239), but I've decided to bring my findings in a "less stale" issue (Also I'm not sure original issue describes my problem).

To quote my findings in #1239:

I can confirm that I'm having a similar issue with the harvesters attached to the windmill. After a short while it stops harvesting (thermal boomshrooms in my case). It also does not stop to connect with the portable item interface.

The most curious thing, it that after deactivating windmill in this "broken" state, the whole structure (apart from windmill bearing itself) "teleports" like ten-ish blocks away from it's original position.

Here's the couple of screenshots for clarity.

It would be kinda hard for me to isolate this being purely create. It seems like that position is the only one where such thing happen. My guess is that somehow that chunk is fucked but I have no concrete proof nor a solid way of reproducing the bug. My investigation continues...

Btw, it's 1.16.5, create v0.3.2c

I can now confirm that the issue is chunk-specific. None of the surrounding chunks examine this issue. The chunk is in this broken state in the save itself. No matter the placement position of the contraption (or windmill bearing to be specific) inside of the chunk borders. the contraption places itself at the same exact position when deactivated (can be seen on screenshots).

It may be something related to #1898, since the issue may have risen after I've chunkloaded (and then removed it) via FTBChunks.

I would love to try and setup a dev environment and try to go through it in debugger (the bizarre "teleportation" of the structure upon deactivation seems like a good place to check out). Although it would require considerable time and effort from me, which I do not really have rn.

commented

Having the exact same issue.

commented

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

commented

This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.