URL:
<http://gna.org/bugs/?20871>
Summary: [unstore_unit] advance=true still not always MP-safe
Project: Battle for Wesnoth
Submitted by: elvish_pillager
Submitted on: Thu 06 Jun 2013 01:18:04 AM GMT
Category: Bug
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: WML
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.10.6
Operating System: Debian Linux
_______________________________________________________
Details:
[unstore_unit] has been reported as MP-unsafe before, and "fixed"
https://gna.org/bugs/?func=detailitem&item_id=15560
https://gna.org/bugs/?func=detailitem&item_id=11359
The situations in those posts have been fixed. But in attack and attack_end
events (at least), it is still broken.
[event]
name=attack end
[message]
message=test
[/message]
[store_unit]
[filter]
side=1
[/filter]
variable=foo
[/store_unit]
{VARIABLE foo.experience 800}
[unstore_unit]
variable=foo
advance=true
fire_event=true
[/unstore_unit]
[/event]
Insert this into any MP scenario and attack. The first error is "choice
expected but none found".
The same code also causes sync errors if put in an "attack" event, but it's
fine in a "side turn" event (and probably in most other synchronized events).
The error doesn't seem to change based on whether the unit being modified is
involved in the attack or not - it's just the fact that it advanced during an
attack_end or attack event at all that causes the problem.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?20871>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
