Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
see its that ♥♥♥♥♥♥♥ simple and devs cant put a ♥♥♥♥♥♥♥ toggle into the game. the q autorun thing is janky I'm sure. Because I'm using autoaim with RMB and it is janky. sometimes it fails to start aiming, it requires a second button to stop aiming. There is no ♥♥♥♥♥♥♥ way you are going to argue that this shouldnt be properly implemented in the game
Yes, that doesn't help in combat though.
that is jank. they could do proper toggle same lazy way and allow binding a proper toggle through console.
By proper toggle I mean on and off on the same button and correctly interacting with other input, like sprint toggle interrupting your aim toggle. But here the behaviors are inconsistent and glitchy. Also in Rust they are not fully interrupted
Thanks a lot. Nonetheless everyone who thinks this is sufficient is part of the problem.
look at amounts of upvotes on reddit and extrapolate
And I am making my own game, and you can be sure it will toggle correctly.