-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
Add dialog to choose between Auto Combat and Quick Combat #9180
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clang-Tidy
found issue(s) with the introduced code (1/1)
…to auto-resolve
use drawOnState, exit dialog only upon action change
@oleg-derevenetz, I'm done pushing changes to this branch now. If you have the chance to look over the changes from resolve/instant to quick then that would be greatly appreciated. |
Thank you! I'll make an effort to take a look during tomorrow. |
@LeHerosInconnu, I've addressed your text suggestions. I shortened this text because As for this description I changed the part about while you observe because it sounds like the game is forcing you to sit down and watch. |
Hello @zenseii,
The words "resolved" and "ended" mean the same thing, and the "and ended" part makes the sentence a bit cumbersome. What about:
The "at the currently set combat speed" part of the sentence will raise a question in the user's mind: "What does that mean?"; whereas the text should be descriptive and clear.
This indicates that the user will be watching the combat (it's simply a description of what happens in this mode), and that he will be able to observe the AI's actions, which may be beneficial to his understanding of how the AI works.
Since "by pressing" is used for keys and is not really suitable for clicks (mouse or other, we press a button not a click), there is need to use a more appropriate term for clicks and in the same style as "by pressing", "by performing" is fine. Why replace the word "time" with "moment"? What about: This can be interrupted at any time by pressing the Auto Combat hotkey or the default Cancel key, or by performing a left or right click anywhere on the game screen." |
Looks nice.
I agreed. Mentioning speed is useless in the description. What about more short and simple? "The computer continues the combat for you in auto mode/automatically"? |
@LeHerosInconnu and @Branikolog. Let's make it simple and just say "The combat is resolved from the current state." The simpler we can make it, the better. I also agree with "The computer continues the combat for you." Continue does imply some similarity to how you were doing the battle up to that point and therefore implies that you can observe it, if you wish. Or you can go and make a sandwich in the meantime. The "while you watch" part sounds like the game is telling you that you have to watch. As @Branikolog points out, it's implied that you can watch it. As for changing time with moment, this isn't only just a matter of taste. Generally words from Latin/French, like moment, are considered more formal than their more casual Germanic counterparts, like time. Another example is the difference between "in a fight" and "in combat" which technically mean the same, but fight being the Germanic word means it is more casual. Therefore, considering the language used in the game in general, like in the videos and the dialogs, moment fits better than time in my opinion. |
@Branikolog and @zenseii, So, I am fine to go with: "The combat is resolved from the current state. This cannot be undone." and: "The computer continues the combat for you. This can be interrupted at any moment by pressing the Auto Combat hotkey or the default Cancel key, or by performing a left or right click anywhere on the game screen." |
@zenseii , many thanks for this useful feature! |
This will let more users notice the Quick Combat feature and it will give touch devices access to Quick Combat.
This PR also adds basic shine effect to the generated buttons' edges.
Related to #9095 and #9100
Fix #9094