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

Freeaim should be configure-able client side #219

Open
Chameleonhider opened this issue Jun 10, 2015 · 2 comments
Open

Freeaim should be configure-able client side #219

Chameleonhider opened this issue Jun 10, 2015 · 2 comments

Comments

@Chameleonhider
Copy link

I would like to suggest a couple new settings:
Client: boundaries, in % of screen. 0% means no freeaim; 100% means being able to move xhair to a side of the screen before moving point of view (default 0%)
Server: a)force freeaim (whether b value would be forced on clients or not, default off) b) forced freeaim value (default 0%).

So by default values clients would be able to use freeaim if they want to. Also they'd be able to fine-tune it. I doubt that those who use this feature would get a lot better, as it has its downsides too. Freeaim helps to stay aware of other targets while tracking down one. It makes recoil less headache inducing. On the other hand, it is harder to move around and doesn't help in CQB.
Also introducing % of screen as measurement value in Freeaim settings would solve (#217)[https://github.com//issues/217]

@epicfacethe3rd
Copy link

that's not a bad idea. there should probably also be an option for the server to block client settings and force it's own, although it would be set to client side by default.

@Chameleonhider
Copy link
Author

That's what I meant.

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

No branches or pull requests

3 participants