-
Notifications
You must be signed in to change notification settings - Fork 0
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
a disband order should show distinctly that a power had a forced dislodged/disband not just "disband" #9
Labels
good first issue
Good for newcomers
Comments
The resolution of #8 will mask this situation in random orders, so solve this first, or preserve a unitTestScenario. |
duffy-ocraven
changed the title
entitled to a build, a disband order should show "void" not "disband"
a disband order should show distinctly that a power had a forced dislodged/disband not just "disband"
Jul 25, 2020
duffy-ocraven
added a commit
that referenced
this issue
Jul 25, 2020
The slightly different loadDiplomacyGame code needed for illustrating #9
Here is the diffs needed in engine/game.py to resolve Issues #9, #10, and #13.
and the needed corresponding change needed to utils/export.py for Issue #10
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
L1094-20
when in Fall a forced dislodged/disband occurred, but then a skipped Fall Retreats phase, then in the Winter adjustments, the order should somewhere show up, and the "results" expressed not just as "disband"
from ./sccs/games/dipusa/unitTestPureGame.json/5 or 4
The text was updated successfully, but these errors were encountered: