Server Suggestion Org/Gov Keybind

Messages
684
Reaction score
556
Points
600
Suggestion Title: Org/Gov Keybind
Suggestion Description: Similarly to the already existing chat/team chat which are local/LOOC respectively, add a new bind to the F1 -> Key Bindings menu.

When pressed as a government employee, it'll open chat with "/gov" already typed in. When civilian, it'll open chat with "/org" already typed in.

Why should this be added?:
- QoL
- Would stop people from accidentally typing org stuff in OOC.

What negatives could this have?:
None that I could think of.

What problem would this suggestion solve?: Taking the time to write /gov or /org manually every single time you want to type something.
 
Depending on what key it is bound to, I can see it being a bit of a finger-fudge that gets people killed tbf, cause when you /org you take your phone out. If that wasn't a concern, I'd just as soon have this replace U being LOOC by default.
 
Just combine them as one button and make something like I or L

Both are pretty tough to misclick as they’re center keyboard and they’re close to the Y and U we already use.
 
Just combine them as one button and make something like I or L

Both are pretty tough to misclick as they’re center keyboard and they’re close to the Y and U we already use.
The misclick would come when you're trying to type something in local ooc, and you hit the adjacent key. Again, would only be an issue if it replaced U for LOOC or sat as another bind like T or I by default. I'm nitpicking ofc, as it's a minor issue for sure, and people misclick Z for phone fairly infrequently, but it's worth bearing in mind as a very minor drawback.
 
people accidentally pulling a phone out when under gp and trying to respond in text chat may become an issue.
This is illogical because it’s a slippery slope.

Not everyone under GP is thinking to respond to an convenient Org chat or quick typer to the level of writing detailed comms to counter play while breaching 3.4

If someone accidentally clicks one of those keys, they could’ve just as easily clicked another chatting key.

In any case, we have staff to investigate and rules to permit the death of that player which paired together defend against malicious conduct.
 
This is illogical because it’s a slippery slope.

Not everyone under GP is thinking to respond to an convenient Org chat or quick typer to the level of writing detailed comms to counter play while breaching 3.4

If someone accidentally clicks one of those keys, they could’ve just as easily clicked another chatting key.

In any case, we have staff to investigate and rules to permit the death of that player which paired together defend against malicious conduct.
I have no clue what your argument is here bro. Illogical because it's a slippery slope? Slippery slope to what? Misclicks happen, and people get punished for them all the time. Being wary about adding another way for people to introduce confusion isn't a slippery slope. I'm personally ambivalent at the prospect of this addition, (that means I don't care one way or another) however it's worth noting that depending on how it's implemented, it may lead to more misclick>accidental pulling phone under gunpoint issues like these, and that issue can't be handwaved away with "muh slippery slope"

It absolutely is an issue. A minor issue that should be considered. How big an issue it becomes depends on how it's implemented, ie: what key it is by default, and what people tend to change it to.

I don't know what the hell you mean by "they could've just as easily clicked another chatting key" Yes bro they could, but that doesn't bring their phone out, so who cares?

If misclicks weren't a concern, which they are, then I would be absolutely in favour of this. Personally I think it *could* replace U for LOOC by default, as if you're chatting a lot in LOOC then you're probably sitting on a roof in an admin sit and it's likely that nobody gives a shit if you talk in local text instead. A dedicated LOOC button isn't really necessary in my view.
 
I have no clue what your argument is here bro. Illogical because it's a slippery slope? Slippery slope to what? Misclicks happen, and people get punished for them all the time. Being wary about adding another way for people to introduce confusion isn't a slippery slope. I'm personally ambivalent at the prospect of this addition, (that means I don't care one way or another) however it's worth noting that depending on how it's implemented, it may lead to more misclick>accidental pulling phone under gunpoint issues like these, and that issue can't be handwaved away with "muh slippery slope"

It absolutely is an issue. A minor issue that should be considered. How big an issue it becomes depends on how it's implemented, ie: what key it is by default, and what people tend to change it to.

I don't know what the hell you mean by "they could've just as easily clicked another chatting key" Yes bro they could, but that doesn't bring their phone out, so who cares?

If misclicks weren't a concern, which they are, then I would be absolutely in favour of this. Personally I think it *could* replace U for LOOC by default, as if you're chatting a lot in LOOC then you're probably sitting on a roof in an admin sit and it's likely that nobody gives a shit if you talk in local text instead. A dedicated LOOC button isn't really necessary in my view.
One second your argument is all about doubling down that misclicks are this insane problem and phones get pulled.

then at the end it turns around and becomes about insisting U get replaced for this purpose?

Never mind that it’s next to Y or H or J. Lol
 

Similar threads

Back
Top