Follow-up Comment #1, bug #18637 (project wesnoth):
In 1.13.1+dev I get assertion failures at the start of move::init() when
trying to move a planned recruit. If the assertion is ignored then there is a
crash on attempting to access a null get_unit()'s ID.
I think it makes sense to disallow planned moves for planned recruits because
(if I understand the intention of planning mode correctly) you should only
plan for what you can initiate in the current turn.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?18637>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
