-
Notifications
You must be signed in to change notification settings - Fork 68
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
Suggestion: Targeting for Fastest / Slowest #160
Comments
It certainly would be nice... If it's not off-topic, I'll add that you may want to check how all of these are translated... |
Since some targets do not move at a constant speed: Would you consider the current speed or the average? @LienRag Thanks for the hint. Is there a better wording in French which could fit the button size? |
Not really actually, alas... |
I would say the current speed that the tower detects when it's ready to pick a target, even if the target's speed is affected because it's glued, or becomes unglued, or is pulsating along slow then fast then slow again. One of the ideas is to be able to pluck targets that are properly glued, or that cannot be glued. Of course, I wouldn't expect something so crazy that it requires significant rewrite or CPU grind. |
Actually there's a very simple solution I hadn't thought out before, but it works only for two cases : instead of writing "le plus" whatever, for one of them you can use "le moins"... So, instead of "the most strong" and "the most weak" you can have "the most strong" and "the less strong". Another solution would be to give codes for each, like greek letters (alpha, beta, gamma,...) before the full title. |
Current targeting allows for
First
,Last
,Closest
,Weakest
andStrongest
. I would like to suggest the addition ofFastest
andSlowest
.The text was updated successfully, but these errors were encountered: