[kovarex] [0.16.36] Items stop moving on belts

[DarkZek]

Hello, after updating my factorio client to the new version and waiting for it to convert my old world I joined my singleplayer world.
Just a few belts have stopped moving items along them and my robots keep trying to place new belts overtop of them, then they run out of charge -then go to charge and keep repeating.
When you break the belts a blueprint is already there (I dont know if this is some new weird feature or a bug which is causing it) and placing it back down fixs the issue.
While this has only happened to a few of my belts and I can certainly break and replace them I thought i'd report it anyways to make factorio a more bug free place.

I have no enabled mods and captured a gif of it
https://media.discordapp.net/attachment ... _20-35.gif

[DarkZek]

Heres the video of the ghost blueprints and the robots
https://youtu.be/uZTwBUdQxwY

[kovarex]

The two problems are connected.

Do you have any idea how it happend, that there are ghost belts over normal belts? Because it shouldn't be normally possible.
I discovered, that with usage of script/mods it can be done and fixed that for the next version, but if you didn't use any of these (which I don't know, since save game history exists only since 0.16) it is still partially unsolved issue.

So for the 0.16.37:

• Teleporting ghosts of belts & rails is disallowed (it might be allowed in 0.17, but I didn't want to make bigger changes now)
• Teleporting of wall ghost is allowed, but the target location must not be occupied by another wall already (As walls connect with ghost walls, this might actually cause desyncs)
• Teleporting entities that are not off-grid is now automatically aligned to the grid.
• When updating to 0.16.37, all walls/belts/rails ghost over built walls/belts/rails are removed upon loading.
• walls/belts/rails on top of each other, ghost of walls/belts/rails on top of walls/belts/rails are now checked in the check_consistency (which is also called automatically when transferring between different versions), so if it still happens later on, the save will be unloadable, which forces the user to report it.