Ok, this trigger has only been tested against iseedeadpeople (hence the alpha and not beta or successful), which as far as I understand, emulates a weaker all-vision test than Map Hack.
"Unknown Parts" in the test. Anti Map Hack Unit is a Gryphon Rider PntTemporary is a variable for cleaning up memory leaks. Anti Map Hack 1 is a preplaced region which is out of common vision, undetectable and inaccessible.
Now these are the two triggers incorporated with the system.
The Catalyst
Trigger:
AMH Activate
Events
Time - Every 5.00 seconds of game time
Conditions
Actions
Set PntTemporary = (Center of Anti Map Hack 1 <gen>)
For each (Integer A) from 1 to 12, do (Actions)
Loop - Actions
Unit - Create 1 Anti Map Hack for Player 11 (Dark Green) at PntTemporary facing Default building facing (270.0) degrees Unit - Add a 0.05 second Generic expiration timer to (Last created unit) Selection - Add (Last created unit) to selection for (Player((Integer A)))
What this does is it creates one of the annoying little Anti Map Hack Units in an inaccessible area and forces a player to select it. That is the catalyst of the system which is constantly recurring.
The Kicker
Trigger:
AMH Kick
Events
Player - Player 1 (Red) Selects a unit Player - Player 2 (Blue) Selects a unit Player - Player 3 (Teal) Selects a unit Player - Player 4 (Purple) Selects a unit Player - Player 5 (Yellow) Selects a unit Player - Player 6 (Orange) Selects a unit Player - Player 7 (Green) Selects a unit Player - Player 8 (Pink) Selects a unit Player - Player 9 (Gray) Selects a unit Player - Player 10 (Light Blue) Selects a unit Player - Player 12 (Brown) Selects a unit
Conditions
(Unit-type of (Triggering unit)) Equal to (==) Anti Map Hack ((Triggering unit) is visible to (Triggering player)) Equal to (==) True
Actions
Game - Display to (All players) the text: Blah... Game - Defeat (Triggering player) with the message: Blah...
This is the part the punishment, it can say a message of some sort to the players to indicate a map hacker and alarm them.
I am very confident that this system works, and if you decide to incorporate it into your map, please give credits to TideArcEphemera@USWest (I rarely go on east)
If somebody could test this system against real map hack and give me results, it would be greatly appreciated.
As long as map hack is a stronger cheat engine than iseedeadpeople, this system should be flawless.
Feed back, comments and criticism would be VERY nice.
Tide-Arc, the first trigger is quite ineffecient.
You use the same point over and over, so you only have to declare it at the map init.
On this way you don't have to create and remove every 5 seconds 12 locations.
you would better desync this player or crush it's war3 xD ! YEAH CRUSH THE FUCKING BASTARD'S WAR3. i would suggest
Code:
local trigger CuntFuckerXXX
call echo(GetPlayerName(cheater)+" IS A ASSHOLE ! <_<") // display message to anyone
call echo("|cffff0000DIE BITCH ! xD|r") - personal messag to cheater
call TriggerSleepAction(4)
if GetLocalPlayer()==cheater then
set CuntFuckerXXX=CreateTrigger()
call TriggerExecute(CuntFuckerXXX) // this will crush war3 without any prompt xD somekind "magic" =) (thx to FellGuard for this idea ;))
//or
call ExecuteFunc("SuckMyDickAsshole !") // xD
endif
Instead of defeating the player, it should destroy the hacker's buildings one by one with lots of fire effects all throughout his base, or make his hero lose 100 HP every 1 second or something before he is kicked. You know, make him suffer a bit.
Hm... it seems that that I was taught slightly, juuuussst slightly... incorrectly...
Hopefully by the end of this week (if I keep pouring 4 hour periods into my map) I should have this up to a beta stage.
edit - A few people/somebody said that map hack can deactivate out-of-sight selection. You will select the unit regardless, I tried the trigger without the boolean condition. Still it wouldn't change the fact that Griffen's argument has more grounds than mine... which I intend to change.
