Encased belts retaining rotational energy after disconnection to engines.
Sudkampsen opened this issue ยท 5 comments
Forge version: 34.1.25
Create: create-mc1.16.3_v0.3+custom
Minecraft version: 1.16.3
When using encased belts along a line of machines, through some process that seems almost random, one or more encased belts will become their own source of rotational energy and keep spinning itself, and other connected belts.
It only seems to affect a few belts at a time, I've yet to see a whole cluster rotating on their own. Destruction of the glitched belts will fix the issue. The whole cluster of connected belts will become over-stressed when disconnected from an engine rather than simply stop moving. Reconnecting will often break the connecting block, and destroys gearshifts if toggled the opposite way.
Have not witnessed regular belts and shafts doing this.
Could be related to issue #319 but I've only witnessed encased belts doing this.
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.
This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.
Managed to replicate it multiple times.
First set encased belts up like so. This is the minimal amount needed to get the bug.
Then add a perpendicular row overlapping any amount of rows.
Attach a source of rotational energy, speed does not matter.
Break encased belt that is not directly connected to engine.
Encased belt that was connected to engine will continue to rotate all attached belts. Breaking that one will fix the issue.
Also experienced the bug by setting the belts in a row.
Right click the belt's face that is pointed toward you with the wrench, and then R-click the top to rotate it, and the belts will rotate when they normally wouldn't. If you simply rotate the belt via the top face without R-clicking the face toward you, it will not rotate belts further along.
You can also simply break it after first R-clicking the face toward you to replicate the bug.
If I find other ways I will update.