I made a map and I want to make it full proof from hacking.

[kewlboy120]

hehe, I know this is a cheating forum so you guys can get the map and add cheats to it and all. But, I want my map with more protection. Do you guys have any videos or any thing that can actually ADD protection to my map?

[Pseudomorph]

Its impossible to make a map fool proof from hacking. Anything you can do to protect it can be undone.

[Risen]

Correct, but there are methods that stop certain users from doing certain things to your map.

[kewlboy120]

Can you tell me some of the methods please?

[Everfades]

If he do it everyone here would know how to undo it^^. There are easy ways which works for rookie hackers, like "when someone writes the word cheats somewhere in chat he gets kicked" - that's used in Fortress Survival

[Ken]

Well, there's some stuff that's pretty ordinary. Using Vexorian's Optimizer, widgetizing the map, corrupting the MPQ header, deleting WE-only files. And there's JASS protection, which is limited only by your imagination and creativity.

Pro tip on JASS protection: Make it so obscure that even you don't know what it's doing!

[Lyerae]

There's a method of protection which essentially makes it so the JASS code cannot be edited. At all.
Yeah, it does work, but there's a problem. It uses the return bug (I2C/C2I).
It's called MapLock, and it's currently broken.

If you can find a way to get I2C and C2I to work in 1.24c (c is the new patch that is in beta), then it'll work.
If your target patch is before 1.24, then it'll work without updates.

[UndeadxAssassin]

If it uses the return bug..that means it's in JASS...which means anyone could just remove it...I'm pretty sure I've heard of this before from one of the makers of DBZ Tribute, but it's easily countered.

[Risen]

It's not a return bug anymore, it's simply a return, nowadays.

It's actually easier to detect to input of jass code by simply retrieving the starting number of handles, and comparing.

[GenDeath]

The end all statement if it can be used in WC3 it can be hacked and opened into WE.
However if you use cheat detection systems that have been obfuscated as well as kick w/o a msg and a couple 1000 lines of code it will be much harder to hack.
Also use what seems to be an anti hack method to be crucial to game play so when a nub removes lets say
Function kick_cheaters
it causes function slcsysint to not load
and etc just to make it terribly difficult to hack but not impossible.