[Release] LuaNinja - Run protected Lua code

[OrangeKingdom]

2950 gs fury warrior down the tuuuuube lol.

Bad Cypher! Bad!

[Ranik]

I gots a WoWInfinity account you can have if you want OrangeKingdom, im not gonna need it

[Ssateneth]

same... not gonna need my wi account. anyone want to buy?

[Despair]

I got perma banned and now Im threatening to sue blizzard if I am not given every single little detail about it. I will claim I was hacked and knew nothing about it.

You are ****ing retarded, I'm glad you are banned.

[armen]

No.

Reread the part where the guy said he wrote his own addon to manage spellcasting.

If you take appropriate precautions, not a single macro you run will be logged by Blizz servers.

Are you kidding me? Do you know what an addon is? It's just Lua code with additional statements for UI elements. If someone writes an addon that takes advantage of running API protected macros it's the same exact thing.

Is it really that hard for people to understand that every (protected) function that has been called all these months was being logged server-side? Caching has nothing to do with detection or historical data.

I had a bad feeling every time I got a pop-up regarding forbidden macros, and an even worse feeling when I decided to squash those warnings with yet another silencing function.

Oh well, Mass Effect 2 and Star Trek Online is upon us!

[danimal]

2950 gs fury warrior down the tuuuuube lol.

Bad Cypher! Bad!

5k feral druid.

65 pally, 5 19 twinks and more.

[kynox]

Are you kidding me? Do you know what an addon is? It's just Lua code with additional statements for UI elements. If someone writes an addon that takes advantage of running API protected macros it's the same exact thing.

Is it really that hard for people to understand that every (protected) function that has been called all these months was being logged server-side? Caching has nothing to do with detection or historical data.

I had a bad feeling every time I got a pop-up regarding forbidden macros, and an even worse feeling when I decided to squash those warnings with yet another silencing function.

Oh well, Mass Effect 2 and Star Trek Online is upon us!

You're spouting bullshit. Lua commands literally just execute the engine functions. When you call CastSpellByName, its no different on the server's end than pressing an action key.

Do you realise how retarded you're sounding?

[Greyman]

Are you kidding me? Do you know what an addon is? It's just Lua code with additional statements for UI elements. If someone writes an addon that takes advantage of running API protected macros it's the same exact thing.

Is it really that hard for people to understand that every (protected) function that has been called all these months was being logged server-side? Caching has nothing to do with detection or historical data.

I had a bad feeling every time I got a pop-up regarding forbidden macros, and an even worse feeling when I decided to squash those warnings with yet another silencing function.

Oh well, Mass Effect 2 and Star Trek Online is upon us!

Sigh. Tell me, what do you know about the internals of the scripting engine in WoW? How much of it have you personally reversed?

You're wrong, and what's worse is you're confidently backing up your assertions whilst being completely unencumbered with any actual knowledge on the subject.

You need to understand the difference between an API and a Macro in the context of WoW scripting. When you do, come back and we can have a conversation. Until then, please stop propagating bold statements that you clearly have no clue on.

[armen]

And I refuted the fact that Lua commands are just engine functions? My point was that if you are using 'protected' engine functions within your addon it is identical to what you would be doing if you execute a macro with the same command. By that same token, if Blizz has been logging these functions, then it does not matter if someone was using an addon or a macro.

Also, kynox/cypher, instead of moderating us noobs, why not figure out what happened? I know it stings to have lost a lot of cred tonight, but I can assure you trying to pick apart my posts will not get you back all those banned accounts.

toodles.

[Greyman]

My point was that if you are using 'protected' engine functions within your addon it is identical to what you would be doing if you execute a macro with the same command.

No, it's not. Until you fix that flawed assumption, bullshit will continue to flow out of your posts like a river unto the sea.

Fire up IDA, and look at how this stuff is implemented. Come back a little bit informed instead of regurgitating something you clearly didn't understand in the first place.

[kynox]

And I refuted the fact that Lua commands are just engine functions? My point was that if you are using 'protected' engine functions within your addon it is identical to what you would be doing if you execute a macro with the same command. By that same token, if Blizz has been logging these functions, then it does not matter if someone was using an addon or a macro.

Also, kynox/cypher, instead of moderating us noobs, why not figure out what happened? I know it stings to have lost a lot of cred tonight, but I can assure you trying to pick apart my posts will not get you back all those banned accounts.

toodles.

You're trying to talk on a matter that you have observed through hear-say. How about you brush up on your credible intel before making absurd accusations with no backing?

When a macro or lua addon calls a function, its processed by the engine and then passed off to the function which sends off the packet to blizzard. They do not get a request containing the lua call, or anything even remotely similar to what you're saying.

I really could care less about the accounts people had banned (unless you are insinuating that we lost accounts; which is quite frankly silly ) - it's a risk taken with using EULA breaking tools.

[armen]

No, it's not. Until you fix that flawed assumption, bullshit will continue to flow out of your posts like a river unto the sea.

Fire up IDA, and look at how this stuff is implemented. Come back a little bit informed instead of regurgitating something you clearly didn't understand in the first place.

Your obvious mastery of the language is only masking the fact that you wish to continue to insult me. It's ok, it makes it easier for me to picture you at your keyboard

Anyways, I have been programming using the WoW API (docs/api - World of Warcraft Programming: A Guide and Reference for Creating WoW Addons) for months now. I have also written a few addons for personal use in conjunction with the luaninja injection. I suppose you would like to quiz me, if that's what you're into, however, I don't quite understand what you're arguing about here?

Obviously Blizzard was able to trap every protected function that people used with this injection. The only other alternative is a flawed approach by Cypher with regard to the actual injection and Warden's ability to catch it. I am taking kynox's word that there haven't been any deltas in what Warden has been scanning.

Trust me, I don't want to really flame; a lot of people put a great amount of time thanks to this hack (I mean look at all the work people like Viral did on the macro threads). We all want to figure out what happened so we can learn and be smarter the next time we hack.

I will continue to contribute to this site regardless, however, due to the fun months that this and other hacks have brought to the drudgery of WoW.

G'night.

[Greyman]

Your obvious mastery of the language is only masking the fact that you wish to continue to insult me. It's ok, it makes it easier for me to picture you at your keyboard

You can have a picture of me if you like - is that what you're asking?

Anyways, I have been programming using the WoW API (docs/api - World of Warcraft Programming: A Guide and Reference for Creating WoW Addons) for months now. I have also written a few addons for personal use in conjunction with the luaninja injection. I suppose you would like to quiz me, if that's what you're into, however, I don't quite understand what you're arguing about here?

Programming in LUA and understanding the internals of the script engine implentation in the WoW executable are fundamentally different. You are making bold (and incorrect) assertions based on the latter, not the former.

Obviously Blizzard was able to trap every protected function that people used with this injection. The only other alternative is a flawed approach by Cypher with regard to the actual injection and Warden's ability to catch it. I am taking kynox's word that there haven't been any deltas in what Warden has been scanning.

Not quite. They have in fact been able to trap a particular method of calling protected functions. As an example, my own bots (which use a completely different method of calling protected LUA functions) remain unbanned.

Also note that Warden is not the only anti-cheat mechanism that WoW utilizes. It is simply the most well known and the most pervasive. It is entirely possible that LuaNinja et al have escaped Warden detection only to be picked up by something else embedded deeply in seemingly innocuous code.

Trust me, I don't want to really flame; a lot of people put a great amount of time thanks to this hack (I mean look at all the work people like Viral did on the macro threads). We all want to figure out what happened so we can learn and be smarter the next time we hack.

Correct. Unfortunately something you considered to be a contribution was not, because it was based on a set of flawed assumptions. Your initial response to being called out on that wasn't entirely productive, hence the 'flame' responses from Kynox and myself.

I will continue to contribute to this site regardless, however, due to the fun months that this and other hacks have brought to the drudgery of WoW.
G'night.

That's all anyone can ever ask. Flame war over, imo.

[DeMoN]

in short

- main account: banned (last used luaninja or any sort of hack tool about a month or so ago)

-4 alt accounts: not banned (logged in through same wow install as main accoutn)

i would like to say thank you to cypher for the brief time of false disillusion that he wasn't some dumb ass elitist kid living in his mothers basement with way to much time on his pepperoni faced hands...simply put hey cypher f u c k you

take care and good bye mmowned.
-DeMoN

[Cypher]

Your obvious mastery of the language is only masking the fact that you wish to continue to insult me. It's ok, it makes it easier for me to picture you at your keyboard

Anyways, I have been programming using the WoW API (docs/api - World of Warcraft Programming: A Guide and Reference for Creating WoW Addons) for months now. I have also written a few addons for personal use in conjunction with the luaninja injection. I suppose you would like to quiz me, if that's what you're into, however, I don't quite understand what you're arguing about here?

Obviously Blizzard was able to trap every protected function that people used with this injection. The only other alternative is a flawed approach by Cypher with regard to the actual injection and Warden's ability to catch it. I am taking kynox's word that there haven't been any deltas in what Warden has been scanning.

Trust me, I don't want to really flame; a lot of people put a great amount of time thanks to this hack (I mean look at all the work people like Viral did on the macro threads). We all want to figure out what happened so we can learn and be smarter the next time we hack.

I will continue to contribute to this site regardless, however, due to the fun months that this and other hacks have brought to the drudgery of WoW.

G'night.

You really don't want to get in an arugment like this with Kynox or Greyman. Both of them are over 9000 times smarter than you when it comes to this stuff.

You're obviously a massive dipshit, so just sit in the corner and shut the **** up. Kthx.