[Program] WoW Lua Enabler

[Robske]

And who didn't really expect this?

Making this public could only result in lockdown sooner or later. Every sane person would see that disabling the LUA protection is far beyond that of common 'hacks/tools' like fishers, scanners, clientside model tools and so on. The amount of content to be exploited and advantage to be gained from this (oh hi, smart counterspell macro) is enormous.

Blizzard's lazy dev team didn't bother too much with extra protection because hell, only a very select few (relative to the total player base) could be arsed to learn the basics to be able to copy/paste from the memory-editing section.

I wondered why you made this a public tool because I'm sure you knew what consequences it would have Kynox.



Meh, more than one way to Rome, this one is closed.

[arigity]

Blizzard's lazy dev team didn't bother too much with extra protection because hell, only a very select few (relative to the total player base) could be arsed to learn the basics to be able to copy/paste from the memory-editing section.

I wondered why you made this a public tool because I'm sure you knew what consequences it would have Apoc.

i doubt blizzard bases its protection scheme on how well people can copy/paste code from the memory editing section on mmowned.

kynox not apoc :O

[Robske]

i doubt blizzard bases its protection scheme on how well people can copy/paste code from the memory editing section on mmowned.

kynox not apoc :O

Whops, got distracted there


I think they do follow what gets released here. And when something so powerfull yet userfriendly gets released to the 'masses' they will (and did) take actions.

[kynox]

Making this public could only result in lockdown sooner or later.

Welcome to the Hack Development process.

Every sane person would see that disabling the LUA protection is far beyond that of common 'hacks/tools' like fishers, scanners, clientside model tools and so on. The amount of content to be exploited and advantage to be gained from this (oh hi, smart counterspell macro) is enormous.

Blizzard's lazy dev team didn't bother too much with extra protection because hell, only a very select few (relative to the total player base) could be arsed to learn the basics to be able to copy/paste from the memory-editing section.

I wondered why you made this a public tool because I'm sure you knew what consequences it would have Kynox.



Meh, more than one way to Rome, this one is closed.

Honestly, i didn't think Blizzard would react so fast, it surprised me that they did. Then again, that is Blizzard for you; you never know what you can expect from them.

In regards to "Why you made this public", well, i discovered the possibly to exploit it and did so. I personally don't use the tool, but i realized other people may, thus the release.

If people are too stupid to read the first post from here on out, i take no responsibility for your ban and you can cry me a river.

[chrismcv]

well within two hours of using this program i get a nice email -
* * * NOTICE OF FINAL WARNING * * * Account Name: DREADSKULL Account Action: 72-Hour Account Suspension and Password ResetReason for Action: Exploitation Policy Violation - Unapproved Third Party Software After a thorough investigation, we have found that a player of the account listed above has used unauthorized game modifications. The use of these modifications violates the World of Warcraft Terms of Use. We ask that you take a moment to review these terms at WoW -> Legal -> Terms of Use. You may not use cheats, bots, mods, hacks or any other software designed to gain an unfair advantage in World of Warcraft.

just a heads up

Lol a heads up?

Obviously someone didn't read my post back a bit

[GordonGekko]

well, everyone should know abot the risk. so from my view kynox took the right deision to make it public. thx a lot for this!

[kynox]

So one of the two new memory scans with 3.0.8 at

[20.01.2009 22:03]: offset: 0077e07e, len: 5, arg: 0

was your tool?

Hey harko, nice to see you here mate. Yes, that is what i patched.

[Karrde]

well within two hours of using this program i get a nice email -
* * * NOTICE OF FINAL WARNING * * * Account Name: DREADSKULL Account Action: 72-Hour Account Suspension and Password ResetReason for Action: Exploitation Policy Violation - Unapproved Third Party Software After a thorough investigation, we have found that a player of the account listed above has used unauthorized game modifications. The use of these modifications violates the World of Warcraft Terms of Use. We ask that you take a moment to review these terms at WoW -> Legal -> Terms of Use. You may not use cheats, bots, mods, hacks or any other software designed to gain an unfair advantage in World of Warcraft.

just a heads up

Yeah. The first post was updated a bit before this one to say that it is detected.

[Lenn]

Got a 72 hours warning too. That tool is still a very nice release, making it private would have been a perfect deal, for customers, and for developper.

[h1pp0]

This is amazing, gotta +REP you for it!

[r3d0gr3]

yea i was very surprised at the speed of which warden detected this program, i mean i had used maphacks in d2 and warcraft 3 for months before getting banned. i was never banned in warcraft 3 and the only reason i was banned in d2 was because i failed to update my d2loader the day it came out. i think either; the warden detection system has alot more manpower behind it or the fact that in the d2 maphack and warcraft 3 maphacks case there was a loader program attached that attempted to mask the users ip address and the specifics of the program that did the actual work. oh well, if i had waited a bit, i wouldve tried the /console tricks posted earlier. this program is still very valuable, it just needs to be masked from warden, maybe via a warcraft loader? at any rate i know enough about blizzard and hacks to know that any hack created is in a perpetual game of cat and mouse with warden, and that warden is not an all seeing eye

[Vladinator]

Wonder if this is totally dead or possible to fix with new offsets, hmm...

[kynox]

Easy to fix, though i cbf fighting Blizzard on it so i'm not going to release another version. Feel free to lock, mods.

[Robske]

Wonder if this is totally dead or possible to fix with new offsets, hmm...

This particular implementation is 'dead'. There still are other routes to be taken.

I don't think there will be another public tool
Edit: Kynox, I always wondered, what stops them from monitoring the entire function?

We're losing offsets fast out here!

[kynox]

Nothing stops them from monitoring the function. They just don't check the whole function for performance reasons.