Create

Create

86M Downloads

[1.16.5-0.3.2f] Rope pulley lowers contraptions farther than physical limit on chunk load

NoahJGersh opened this issue ยท 2 comments

commented

I'm using a rope pulley elevator, but twice now I've had an issue where (on chunk load) the rope pulley has lowered its attached contraption down several blocks, even when it would be stopped by blocks in its path.

The issue seems to be unrelated to the direction of power, as it's done this even when anchored at the top of the shaft. It also seems to only be related to the chunks themselves fully unloading and then reloading. This is occurring on a 1.16.5 server.

The following screenshot shows it having loaded in several blocks below where it should be (the arches should be flush), despite the pulley receiving upwards rotational input. The pulley magnet was still fully attached, but I needed to remove it to fix the issue.
2021-11-20_12 52 54

In its normal top position, it should have loaded like so, where it was left.
2021-11-20_13 09 49

There are also issues with the lower platform, but I didn't save a screenshot at the time, but I have images of where the elevator should be, and the nature of the blocks stopping it. In this case, it had clipped through the bottom supports (and into the lakebed) such that the linear chassis at the top of the structure was in the place of the top center support log. In this situation, the pulley magnet block was attached to the structure, but the rest of the rope was gone. A separate pulley magnet still existed in the rope pulley block at the top. Most of the structure needed to be disassembled in order for it to be retrieved again- the superglued arch portions no longer worked correctly, though the linear and radial chassis blocks were fully functional.

2021-11-20_13 11 36
2021-11-20_13 11 44

I'm curious what might cause this issue? Is there some sort of chunk loading synchronicity issue, or Create isn't properly storing the location (relative or otherwise) of the anchored blocks? They place in both cases.

Thanks in advance!

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.