-
-
Notifications
You must be signed in to change notification settings - Fork 991
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Delay Shroud Updates" should apply to recalls #2196
Comments
I've tried to implement this by making place_recruit return early if team::auto_shroud_updates() is false, but then I ran into the undo list handling: actions::undo::recall_action unconditionally clears the shroud. I'm not sure how to proceed. |
This appears to be due to the initiative special, and its associated events. It triggers on all prerecruit and prerecall events, breaking undo for recall and traitless recruit. |
Fixes wesnoth#2196 (in addition to ca0b503 which was HttT-specific).
Fixes wesnoth#2196 (in addition to ca0b503 which was HttT-specific).
Fixes wesnoth#2196 (in addition to ca0b503 which was HttT-specific).
Fixes wesnoth#2196 (in addition to ca0b503 which was HttT-specific).
I think there are three separate issues here:
Thanks for fixing (1), @AI0867. |
After my fix, recalls did appear to honor "delay shroud updates" in the tests I did in Hasty Alliance. |
With current master, if I start HttT anew, :create a dwarvish unit, :change_level to Hasty Alliance, enable Delay Shroud Updates and recall the unit onto (8,16), then shroud is removed from some hexes and the recall is not undoable. So it seems it's fixed for you but not for me..? |
Hi,
Recalling a unit unveils the shroud, and hence is not undoable, even while "Delay Shroud Updates" is enabled.
To reproduce, enable "Delay Shroud Updates" and recall any dwarf onto (8,16) at the very start of HttT Hasty Alliance. The recall will unveil (4,13) and be non-undoable. I expect the recall not to unveil any hexes and to be undoable, until "Update Shroud Now" is invoked.
The text was updated successfully, but these errors were encountered: