Aoe hack pi chanel 18

[SilentWar]

FS 165 NAME IS Ghostdown HACK AOE CHANEL 18 PI
TIME 20:07
DAY 08-08-2012
SEVER MERCURY
CHECK PLS
5266

[BackForMore]

that SS shows no aoe hack lol...

[SilentWar]

that ss shows no aoe hack lol...
fix ur eyes

[cerverus3]

that SS shows no aoe hack lol...

cant u c the hp down on teh mobs on the back O.o?

[cronic21]

cant u c the hp down on teh mobs on the back O.o?
^ what he said

[Anker]

that SS shows no aoe hack lol...
yeah man fix ur eyes

[sn0wXz]

The part I don't get is why AOE modification is not prevented already, I mean these users are doing the same old method been done for years now; realistically you can keep banning accounts for it but the smarter approach would be removing the debug gm function that AOE users exploit, or make it server sided - when changed auto DC/error code, also you shouldn't EVER have a skill casting over 20-30 AOE anyway, so why let the memory address be modified to approx 100-200 depending on the field of view, since non rider AOE uses only FOV to AOE, and not sending packets to server spoofing an attack on mobs. They don't even support this version of cabal, we have it pretty good in general.

When PK exploit in town was going on, they ban and patch it directly making the address no longer function from client modifications, don't see why AOE is not already patched 3 years ago for non packet modifications using just memory editors/trainers. I sincerely think you would spend less time to just pay a dev to patch it properly, as opposed to letting average users AOE and relying on playerbase to report them adequately.

Memory AOE:
GM Debug : enable <-Force D/C, or restrict from normal client use, maybe breaklee client function only.
AOE : modified <-Should have cap or just made server sided based on skills casted.

[[GM] Kato]

Thanks for the report, SilentWar!

We'll investigate the matter and make sure the appropriate actions are taken.

Please continue to send us any suspicious activity you might find.

Regards,
[GM] Kato