[kovarex] [0.17.25] (Blueprinted) train can lost it's schedule depending on build order

[jogaproger]

This bug is hard to reproduce, but it happens in the following scenario with a 1 locomotive 2 cargo train: L-C1-C2

1) First place a locomotive on a rail
2) Create a schedule for the locomotive
3) Place the second cargo (C2) first in a little bit farther from the locomotive than it's place
4) Now place the first cargo (C1) between the locomotive and the second cargo (C2).
5) Now two things can happen:
5.1) C1 is attached to the train first, and C2 is moved a little bit so it is behind C1 (this is OK)
5.2) C1 is actually attached to C2 first, then the Locomotive is moved so it is in front of C1. In this case the schedule of the train is lost.
(Maybe in this case the game tries to prefer the "schedule" of C1-C2 which is empty by default?)

The second case is a problem, because it can happen when a train is placed by construction robots on a blueprint, a case in which the schedule from the blueprint is lost.

[TruePikachu]

Can you post a blueprint string? I was under the impression entities are stored in a predetermined order, and not necessairily by build order, but that might only have been the case for things that are grid-aligned.

[jogaproger]

I tried to make a smaller blueprint which produces this error.

0eNqVl92u2jAMx98l16WK7Xxyt73GdDRxoOJUgha1hQ0h3n0pLRROM+HcEZr84vztOPZFfO6OxaEpq04sL6Jc11Urlr8uoi231WrX/9edD4VYirIr9iIT1Wrfj5pVuRPXTJTVpvgrlnD9yERRdWVXFsP62+D8uzruP4smTHis7MLSatF29SHQDnUbltRVv0/AyEycxXIBKpA3ZVOsh28mE223Gn6Ln2HbGR4f+PWxORWbxc2+GX8BMO4A33aIMOnBbHubt1/d/6hmhOIrFCNQxYYqPlSzociHmgd0V6/rfd2Vp2JOpFxK6wD1E7huysAa/SVzqyN0yzVZ8i12XGaCCp7LTHAXSF60+nisUgw53a/1qtnWiz+rbZg7R+bG2buvZK6NUdKgnjuNiFBpp8go50FqRGWkp35tWZ3CzLoJjOq428WsQXZAwqibez2jjVHZFxIwCoUYVHEzhx2YmsHUPGeAyjVp0OZ+e3RuFYKzEX8o0Fo5NMo7SWDAIPDdYXhnhLsZ1xjE8g4VhMrJOi8fp6LcYZ8h5oeSyhoP1nsrJRoZDkWTIIxzOabOOp/kOvcbOzsMIyaR1M5YrXyQ2Vt0TgOBI80W23N1Mrl3gzI3qzB3hv4jlAofguvDZZWOCHBa+N4glGkRTq8BrmJISAqob8TYc4DJGcMwoMR1BeYaSd3jw4UoGKIwkhfDBQw30Ns+OkJMSAALjhcaqNKqFP8+J6JOeUr8+7cJTWKSNe8fJ+SmDpPLKRv6cD2kMtFsiDqoDmg9aHJITqOmMeMw3OASCzuQDN18YmHHgZJk1WDyodREngkWw0Ni3ciyGdMqOxaT0io7FlOlVXYspmZ1OSPwe6X43OT8EH1D1a6/is1xN3ZUUwj0Y5ORfJoy9GzP67PLa9P00RNvTdzyqefLxKlo2iG/UHiBpcPw2Fyv/wCxU33j

Copy blueprint

Also, this bug is not determined only by how the blueprint is stored (as it only happens sometimes). I made a video about the behavior i described in the first post:
https://youtu.be/U_HuDBov9EU
I think this is the thing that happens when the schedule is lost during robots building the blueprint.

[TruePikachu]

Ah, the wording made me assume it was based on the initial build order versus the order the blueprinted entities are built when instantiating the blueprint.

[kovarex]

Thanks for the report, fixed for the next version.