Skip to content
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

Make flag throwing easier #182

Open
AfterShockFF opened this issue Apr 1, 2015 · 4 comments
Open

Make flag throwing easier #182

AfterShockFF opened this issue Apr 1, 2015 · 4 comments

Comments

@AfterShockFF
Copy link
Member

With the new flag hitbox and a good defense, flags can be somewhat stationary for extended periods, even when players touch the flag there is no guarantee the flag throw command can be given in the very short space of time before the flag is dropped again. Whilst we do want more staggered flag progression, its important that the flag does continue to move (even if slowly) rather than get stuck in one place for a long time.

In particular, it's a little irritating to have to spam the "throw flag" bind repeatedly, grab the flag, and then not throw it.

This would be solved by allowing players to instantly throw the flag when they touch it. There are two ways we could implement this:

  1. Queue the flag throw command, so that pressing throw within 0.5sec of touching the flag will throw the flag when you touch it.
  2. Change the flag throw command to be a "hold" button, so you can hold the key to instantly throw when you touch it.

There would still be depth in the decision as to whether to throw or not, since you cannot homerun or conc out with the flag if you throw it (given the "no-retouch" time).

@TYRANNOSAURUSCOW
Copy link

#2 sounds like a good idea to me.

@alaswell
Copy link
Member

alaswell commented Apr 1, 2015

The second option seems a little too easy to me, because you essentially don't even have to think about it at all to get a toss. However, I think queuing the command is an awesome solution, that still allows for some user error and skill but makes it much easier at the same time. So, the first one get's my vote.

@WiFiDi
Copy link

WiFiDi commented Apr 1, 2015

with alaswell said making it guarantee is taking way skill. solving the problem of that its a very finicky command which i have noticed is a good idea. making it a guarantee or automatic i don't like. voting for 1st idea.

@twincannon
Copy link

Just fix the "kicked for spamming commands" when you spin a mousewheel with dropitems bound too fast and it'd be perfect for me :p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants