Rails/rotors stopped with a rail speed controller can start moving/spinning when they shouldn't when the entity is loaded in.
They move a few blocks first, then the speed controller kicks in and disables it. It's probably a loading issue although in this case the speed controller was very close to the rail (maybe not in the same chunk?)
unload/load that sector and it will have moved
-QA Testing-
Rotators and rails that were stopped with a rail speed controller, still let those entities move a block.
Maybe logic doesn't load fast enough?
<replace this line with the file content>
<replace this line with the file content>
Rails will now wait until everything in the parent+raildocks entity is loaded. This also prevents docks to drive further into each other on loading
-QA Testing-
Rotators and rails that were stopped with a rail speed controller, still let those entities move a block.
Maybe logic doesn't load fast enough?