Rules issues with the TripleA engine
-
@Cernel To be clear, in general, I believe that every time you skip a warning (also for aircrafts crashing) or edit you take upon yourself the full responsibility of that action that, if proved wrong, implies that you have intentionally made an illegal move (otherwise nothing at all is illegal, as everyone could always say he didn't intend to). If you are not sure, you should stop and discuss the matter (with a judge, if you are in a tournament or such), before skipping or editing on your own.
-
@Cernel
I see what you mean and I think we don't have a big dissent here at least regarding the consequences. I am not very happy with that FAQ-aspect that introduced the rule "You may only purchase as many units as you will have the ability to mobilize after making repairs to any damaged industrial complexes. The rules for returning excess units are intended only for inadvertent over-purchasing."
While the first sentence is a clear "law" the second sentence opens room for discussing the "human factor". Representing the latter in the TripleA engine appears to be pointless, IMHO. -
The list has been updated to include the NCM-movement regression (issue 7350).
-
@Panther the list is the same as what is returned by this link? https://github.com/triplea-game/triplea/labels/Impact%3A Bad Game Rules
Just want to be sure that we have everything properly labelled.
-
@LaFayette
Not in every case. I have compared the lists and identified the following differences:-
The above list contains issus # 1645, 1867 and 5195. Those issues have been closed on Github despite they have not been resolved.
-
Above issue # 6256 is not labelled as "Impact: Bad Game Rules" on Github.
-
Above issues # 3846 and # 4480 have been partly resolved and thus closed on Github, but there are tasks remaining.
-
Issue # 4107 on Github is not part of the above list, as it is not affecting core vx-rules.
-
Issue # 4649 on Github is not part of the above list, because the mentioned error has occurred here and there in the past independently from any ruleset.
-
Issue # 6032 on Github is not part of the above list as it is not an issue of rules gameplay but of a consequence of special editing, incorrectly handled by the engine.
-
-
@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. -
@Cernel Agreed, thanks.
-
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?
-
@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.
-
@Panther could you confirm that the OP is up to date? Better yet, could you confirm that all linked issues are tagged appropriately in bug tracking: https://github.com/triplea-game/triplea/labels/Impact%3A Bad Game Rules?
Are there any closed that actually require more work? https://github.com/triplea-game/triplea/issues?q=label%3A"Impact%3A+Bad+Game+Rules"+is%3Aclosed
I am unpinning this topic, I want to better focus this category for player-help.
-
@LaFayette said in Rules issues with the TripleA engine:
@Panther could you confirm that the OP is up to date?
I have no hint that it is not up to date. I cannot remember a single Pull Request that directly addressed any of these issues. I am aware that @Trevan has dealt with some mechanics here and there that might have partly influenced an issue.
I will put your GitHub-related questions on my todo-list.
I am unpinning this topic, I want to better focus this category for player-help.
I wonder how this topic is not a huge help to players experiencing those issues and constantly stumbling over them. Aknowledging the fact that an issue is caused within the engine is "gaming support" - exactly what this category is about.
-
@Panther said in Rules issues with the TripleA engine:
I wonder how this topic is not a huge help to players experiencing those issues and constantly stumbling over them.
I'm somewhat familiar with these issues and it still would take me a really large amount of time to go through them to find relevant information and whether they are current and what exactly they are. This is simply too 'raw' and too much information to be generally useful to the general player.
-
@LaFayette said in Rules issues with the TripleA engine:
I'm somewhat familiar with these issues and it still would take me a really large amount of time to go through them to find relevant information and whether they are current and what exactly they are. This is simply too 'raw' and too much information to be generally useful to the general player.
I disagree with both of your statements, FWIW. But I am not going to repeat a discussion about dealing with rules related issues we already had some time ago.
Do what you want.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login