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

Keybind all abilities #186

Open
Anusien opened this issue Jan 11, 2022 · 1 comment
Open

Keybind all abilities #186

Anusien opened this issue Jan 11, 2022 · 1 comment
Labels
question Further information is requested

Comments

@Anusien
Copy link
Owner

Anusien commented Jan 11, 2022

Arsonist, Shifter, Time Lord, Seer, Medic, Arsonist, Altruist and Sheriff's abilities are bound to the 'Q' key. This makes it really inconsistent between roles. We should do something here and sync it up for everyone.

As an example, The Other Roles bound all killing abilities to 'Q' and others to 'F'.

@Anusien Anusien added the question Further information is requested label Jan 11, 2022
@VirusTLNR
Copy link

slightly unrelated, but i was thinking about keybinds/keys/buttons/etc

if we take the crew.. they have no buttons.. 0
if we take the impostor, they have 1.. a kill button

now roles which kill generally have their kill button in the same place as the kill button for impostor, so that should be Q.

but what about roles that have the button in the same place, but that isnt a kill button? for example. the engineer.

honestly, i dont use hotkeys... but i always click in the same place for every ability in the kill button location.

with updating to the new among us version, i assume like other mods have, buttons will be laid out better.

so i feel like if a button is in the kill button space.. it should use Q, even if you cant kill

then if a role has 3 buttons... then it would be 3 keybinds..

Q, F and something else thats comfortable and unused, then buttons in the same positiuon on the screen, would use the same key.. and rather than them being though of as "kill" abilities... the key would just be associated with the button position.

think of it like "ability 1, ability 2, ability 3"

makes more sense than assigning a different key to a same placed button right?

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

No branches or pull requests

2 participants