Sign in to follow this  

Detecting Turbo Controllers

This topic is 3409 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, I don't want people using turbo controller when playing my game, so I need a way of detecting them. One thing I thought of is that turbo controllers register in a pattern while human tapping is inconsistant. I was wondering if there is a better way of detecting turbo controllers. Thanks.

Share this post


Link to post
Share on other sites
That depends on what exactly you mean by a "turbo controller". Assuming it's a controller with a feature that allows it to send multiple button presses (As on, off, on, off, on, off signals) when a button is just being held, the only way to detect that would be by doing pattern recognition on the input as you suggested. The autofire is likely implemented in hardware, so there's no other way to detect it.

Share this post


Link to post
Share on other sites
It's trivial to attach to the process image at runtime, figure out which branch to cut and disable that whole branch such that your "anti-turbo" code never gets executed. And it's equally trivial to kill any mechanisms to prevent attaching to the process (or detection thereof), so don't even bother with that.

What you should be asking, rather, is how you can redesign your game such that cheating (if you call turbo buttons cheating) does not give a significant advantage. The "oh god people will cheat in our game" is often a sign of very poor design with respect to the gameplay mechanics.

Share this post


Link to post
Share on other sites
You're wasting your time. Besides, why would you want to do that to your customers? Designing your game so it doesn't work with your customer's hardware is a great way to drive them away.

Share this post


Link to post
Share on other sites
This depends alot on the "thing" you're trying to prevent the players from doing.

If it were the fire rate for example, and you wished to prevent them from firing a million more bullets than required; it should be simple to engineer the code to prevent a certain number of bullets fired off in a given time (or another way, simple to prevent a certain number of bullets "existing" at the same time).

It's possible to program around this, rather than alienating turbo controls completely.

Share this post


Link to post
Share on other sites

This topic is 3409 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this