URL:
<http://gna.org/bugs/?18877>
Summary: Putting a unit on the recall list can overwrite one
already on the list
Project: Battle for Wesnoth
Submitted by: sigurdthedragon
Submitted on: Fri 28 Oct 2011 05:00:06 PM GMT
Category: Bug
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Units
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: r51685
Operating System: Win 7 x64
_______________________________________________________
Details:
If two units are the same side and have the same underlying_id, and one is on
the map and the other on the recall list...
If the one on the map is put on the recall list, it will overwrite the one
already there.
Both wml [unstore_unit] and lua wesnoth.put_recall_unit can cause this.
Noticed this first in developing Custom Campaign, and this post seems to
indicate that other MP campaigns have run into this issue, and that it will
just occur given enough scenarios.
http://forums.wesnoth.org/viewtopic.php?f=8&t=34170#p496192
I've done a wml workaround, but altering underlying_id strikes me as
something a umc author shouldn't have to worry about.
Attached is a test scenario that illustrates the conflict in SP & MP using
[unstore_unit]
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Fri 28 Oct 2011 05:00:06 PM GMT Name: Test_Bed.zip Size: 1kB By:
sigurdthedragon
<http://gna.org/bugs/download.php?file_id=14301>
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?18877>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
