• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 Hive's 6th HD Modeling Contest: Mechanical is now open! Design and model a mechanical creature, mechanized animal, a futuristic robotic being, or anything else your imagination can tinker with! 📅 Submissions close on June 30, 2024. Don't miss this opportunity to let your creativity shine! Enter now and show us your mechanical masterpiece!🔗 Click here to enter!

Something to combat drophack

Status
Not open for further replies.
Level 1
Joined
Jun 10, 2014
Messages
1
There are suddenly more cases of drop hacking on custom games and I was wondering if there was a way to perhaps detect and stop this with triggers on the map.

If you don't know what drop hacking is, it's something used in melee games to lag out the opponents with system lag. If my research is correct, the player who drop hacks selects a bunch of units, usually workers/worker and then presses down on some hotkey for his hacking program, usually one of the F2, F3, F4... keys. This will make the hack program issue hundreds and hundreds of commands to the units, lagging the game for everyone.
In melee drop hackers need the better system in order to win the match by lagging everyone out. However whoever the people going around drop hacking on custom games seem to just enjoy the power to end games and the prospect of "trolling" people. It's becoming an increasingly painful problem.

From experience, kicking the person drop hacking, while one can still kick in the lag, instantly solves a larger portion of the lag. So I was wondering, if there was perhaps a way with triggers to perhaps detect the abnormality of the amount of orders issued to a unit, to be able to defeat the player before he can do too much harm.
 
Level 20
Joined
Jul 6, 2009
Messages
1,885
If issuing large amounts of orders is how it's done, then you should be able to count how many orders have been given within a certain amount of time and if it goes over some limt, you can just remove the player.

Whenever a player issues an order, increment some counter and start a countdown timer. Check if the counter gets to some abnormal value and if it does drop the player. Otherwise if the countdown timer expires, reset the counter to 0.
 
Status
Not open for further replies.
Top