Rules issues with the TripleA engine


  • Moderators Admin

    @Panther If this
    https://github.com/triplea-game/triplea/issues/5195
    was actually closed under my suggestion of it being a duplicate of
    https://github.com/triplea-game/triplea/issues/5194
    I suppose you can obliterate it.


  • Moderators Admin

    @Cernel Agreed, thanks.


  • Admin

    Thank you for going through those. I took a look and seems we just need more detailed specs to close everything out. Divide and conquer.

    With that said, #1645, #1867 and #5195 need new issues created with a more detailed specification of what to do, notably:

    • description of what the game does today with a call out on what is wrong
    • description of how to create the problem
    • save game attached at the location of the problem (nice-to-have)
    • description of the actual correct game behavior
    • listing of which rule sets the change should apply to (if no save game then a list of some sample maps)
    • yes/no on whether the rule set should be optional or always enforced.

    #3856 and #4480 probably should closed and any remaining work needed created as new issues with the same details above. (FWIW, I acknowledge it is a lot of detail. To get working code, you need a code specification. To create a code specification, you need a functional specification (ie: the what to do). The above is still not quite a functional specification, but it is quite close; hence we'll need all of that information, as developers we'll interact with the code for all of those details at an even greater level and will be creating games to exercise the changes before and after repeatedly).

    Each new issue created, ideally it's as atomic & independent as possible. It's much easier to resolve 5 small issues than it is 1 large issue.

    Above issue # 6256 is not labelled as "Impact: Bad Game Rules" on Github.

    I'm curious if choosing casualties of lowest movement is a rule, or just the better choice? Would giving players the option of choosing a higher movement plane for casualty actually then be a rule violation?


  • Moderators Admin

    @LaFayette said in Rules issues with the TripleA engine:

    Above issue # 6256 is not labelled as "Impact: Bad Game Rules" on Github.

    I'm curious if choosing casualties of lowest movement is a rule, or just the better choice? Would giving players the option of choosing a higher movement plane for casualty actually then be a rule violation?

    As I said above:

    On A&A .org this topic was intended primarily for PBF users stumbling over issues during their games. That it could serve as "summarizing tasklist" for developers and contributors, too, has been a nice side effect. ...

    So you are somehow correct. While this (#6256) is a question of "better choice" indeed, players often stumble over this issue, when the engine somehow arbitrarily takes out a unit, thus preventing the player from continuing his move as intended. So this is why this issue is part of my list: to acknowledge the fact. On the other hand one could easily conclude that the fact that the engine chooses "any" unit instead of leaving the choice to the player is a violation of the rules.

    Technically the player should be free to take out whatever eligible unit with whatever movement left. It is just for simplification purposes that taking out the unit with the least remaining movement points has been discussed.


Log in to reply