I got this assert also with bzr9094 when loading the attached savegame and the second ship arrives at the port.
The reason why i have made this savegame was: Before saving i noticed:
1. the first ship arrives at the port
2. loaded soldiers and stones
3. navigated to the close port on the west
4. removed all wares and soldiers
5. loaded the wares and soldiers again
6. navigated to the third port (also in the west but far away)
I have set the priority of soldiers on the third port, so i was surprised why the ship stops at at the second port un/reloading the wares and soldiers. I thought this is a bug and created this savegame, which shows the assert now.
I did not understand why the ship scheduling branch was merged anyway... it hasn't a bug associated and wasn't tested imho. Hopefully this is not part of build20.
I got this assert also with bzr9094 when loading the attached savegame and the second ship arrives at the port.
The reason why i have made this savegame was: Before saving i noticed:
1. the first ship arrives at the port
2. loaded soldiers and stones
3. navigated to the close port on the west
4. removed all wares and soldiers
5. loaded the wares and soldiers again
6. navigated to the third port (also in the west but far away)
I have set the priority of soldiers on the third port, so i was surprised why the ship stops at at the second port un/reloading the wares and soldiers. I thought this is a bug and created this savegame, which shows the assert now.
I did not understand why the ship scheduling branch was merged anyway... it hasn't a bug associated and wasn't tested imho. Hopefully this is not part of build20.