Seafaring errors after port destroyed

Bug #1228718 reported by Justin Love
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
widelands
Fix Released
Undecided
Unassigned

Bug Description

Playing the "Volcanic Winter" map with r6748 against AI. This map has several port spaces.

I built a port on the central penisula at 69,75, only to find I was in sight range of the other player. Despite the large distance in buildable area, he was able to send solders around the inlet and quickly destroy the port. Afterwards, there were several seafaring errors.

- I tried to start a new expedition, but it stalled on the last wood, even though there were plenty in the port istself. I added another sawmill, increased the economy target, changed priority, and adjusted the store targets without effect. Finally I canceled the expedition; the next was able to finish.

- I'm less certain of this, but I believe that as soon as the second expedition completed, a third completed, basically as quickly as the wares could be shuffled.

- I started a new port in the south 40,119. However, as soon as I built a lumberjacks hut, a ship loaded up and sailed to the first (destroyed) port space and sat there. I tried sinking ships a few times but ship always sailed to the first port space. Finally I gave up and destroyed the southern port. When I rebuilt it, things started working, just in time for the other player to show up and kill the site ;^)

I've got the replay, although it seems to get stuck in PAUSE before I gave up on the southern port. It might have been a background program that kicked off the fullscreen for a dialog box while I was playing. (Sorry about the all the economic stalls, you'll have to fast forward a lot ;^) )

Tags: seafaring
Revision history for this message
Justin Love (wondible) wrote :
  • Replay Edit (226.6 KiB, application/octet-stream)
Revision history for this message
SirVer (sirver) wrote :

Sounds like very real issues and annoying. However I think it is unwise to target them for b18, otherwise we will never get it out of the door.

Leaving as new as I can not investigate right now.

Changed in widelands:
milestone: none → build19-rc1
Revision history for this message
SirVer (sirver) wrote :

I think most if not all of the issues should be fixed in r6789.

Changed in widelands:
status: New → Incomplete
status: Incomplete → Fix Committed
milestone: build19-rc1 → build18-rc1
Revision history for this message
SirVer (sirver) wrote :

Released in build-18 rc1.

Changed in widelands:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.