-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
S07 ("The Bridge is Broken") improvements #25
Comments
should address some of the points in #25 (at least partially); only partially tested (some of these changes were from after I completed the scenario)
add checks to ensure second_unit is on your side before letting it speak addresses checkbox 4 of issue #25
ok point 4 is done as of 2dd3009 |
also point 1 is kinda done as of 35c8177, but I'll wait for someone else (probably @Ashmyr or @knyghtmare) to confirm first before checking it off |
ok checking off the first one after confirmation from @Ashmyr on Discord |
ok so I've double-checked and it looks like I don't actually need to re-disallow Guardsmen recruitment again later after all; in the next scenario they're gone again as they're supposed to be... I still might want to handle their recruitment limit better, though, by, like, displaying a counter or something... |
we can now check off the 3rd checkbox in issue #25
Added a message to this effect in 6a29cd6, so I'm considering that box checked off now... |
first_time_only=no
, which would then require restructuring the whole thing to ensure you can still only choose one route after you've made your selection)(disallow their recruitment again in more places?)The text was updated successfully, but these errors were encountered: