Construction sites don'd get ware allocated for at least 2 hours; a ware is not transported away from a flag for at least 2 hours.

[Vier Eck]

Applies to widelands version: At least bzr9019[trunk] (Release).
Related forum post: https://wl.widelands.org/forum/post/27354/.

In gameplay I encountered the situation that I have:

(1)

A couple of construction sites which wait for wares but do not get them allocated (if I click on the construction site, the icon for the ware is the light variant, meaning that not ware is allocated). The economy has more than enough of the needed wares.

When I then click on the construction site and move the sliders for the number of wares to store at the construction site to the most left, and then back to the right, wares will get allocated and the construction will finish.

[¹] I attach a screenshoot showing the location of one of those construction sites; more are to the west.
(Filename: 'construction_site_not_getting_wares_allocated.png'.)

(2)

There is a place where at a flag a wood log is lying around. It will not be transported anywhere; not to a construction site, not to a building processing it, and also not to a warehouse (there is one nearby which accepts logs).

When I open a construction site nearby which needs wood logs, then the log will be allocated for that construction site and transported there. Otherwise, it will stay lying around.

[²] I attach a screenshoot showing the location of the log which is lying around.
(Filename: 'log_lying_around.png'.)

All this I observed for at least 2 hours of gameplay (the not finishing construction sites most probably much longer, but I explcitly tested only for two hours).

[³] I attach a savegame which was done after the 2 hours of test
(Filename: 'savegame.wgf'),
and
[⁴] I attach a replay from after the two hours of test (the replay was autosaved when exiting the game)
(Filenames: 'replay.wrpl' and 'replay.wrpl.wgf'),
and
[⁵] I attach the output of running widelands with `widelands --verbose 2>&1` (combined stdout and stderr).
(Filename: 'widelands-terminal-output.log.xz' -- XZ compressed.)

(3)

After creation of the savegame [³], I did run another test, based on loading the savegame [³] (so continuing on):

I did burn down all harbours, and I connected everything into one economy by land.

I did burn down the one warehouse in the game which I ordered to move out all wares (and was in the middle of this process).

I did let it run for another 20 minutes of gameplay.

The things I observed in (1) and (2) did not change within the time of this test.

[⁶] I attach a savegame after those additional 20 minutes of test
(Filename: savegame_after_+20min_without_harbours.wgf),
and
[⁷] I attach a replay from after those additional 20 minutes of test (the replay was autosaved when exiting the game)
(Filenames: 'replay_after_+20min_without_harbours.wrpl' and (replay_after_+20min_without_harbours.wrpl.wgf'),
and
[⁸] I attach the output of running widelands with `widelands --verbose 2>&1` (combined stdout and stderr).
(Filename: 'widelands-terminal-output_after_+20min_without_harbours.log.xz' -- XZ compressed.)

[⁹] I attach (for couriosity purposes, maybe) a screenshoot showing the warehouse which I did burn down in this additional test.
(Filename: 'warehouse_orderd_emptying.png'.)

[Vier Eck (viereck)]

Related forum post: https://wl.widelands.org/forum/post/27354/

[hessenfarmer (stephan-lutz)]

I can confirm the weird behaviour in the attached savegame. Even in new constructionsites of mines only a third of the wares is allocated at first. changing the sliders or simply changing priority migth fix it. Priority is weird too. if you set it to high priority only another third of construction wares is allocated (dark Symbol) if you set it to low all wares are allocated.

my Windows release build did not write any meaningful logs though. Needs Investigation.

[kaputtnik (franku)]

I think this behavior is also described in bug 1821965

Because the other bug has a savegame with a minimal amount of buildings, i guess testing is easier in the other bug. So i mark this as a duplicate. Feel free to remove the duplicate if you think it is not the same bug.