What steps will reproduce the problem?
1. Try to set a cheat-protected variable like "timescale"
2. Try to set "sv_cheats"
You'll get a read-only error... which doesn't really make any sense since we
have an entire aimbot included that can be enabled via the unprotected aim
cvar. Enabling cheats would allow for settings such as timescale, which would
be perfect to adapt the game better for the limited precision and
responsiveness of touchscreen aiming:
With cheats, a macro could (for example):
Slow down time to 20%
Zoom in 10%
Decrease mouse sensitivity to 20%
Making a shot much easier, but still more satisfying than with the aimbot.
Original issue reported on code.google.com by hansschm...@gmail.com on 25 Jun 2011 at 1:22
Original issue reported on code.google.com by
hansschm...@gmail.comon 25 Jun 2011 at 1:22