Maybe the new protect function in Chinese WOW Client

[why2004007]

Hi guys,

These days I found that dll files injected into my client can't be called.If u called it the client will stop work and getting closed.

I don't know if it is a new protect function.Cause we got a different build number 15079.It's higher than other contries.

I'm not a programmer and I just tested some hacks.Maybe I was wrong.But if it is the new function I think a small patch will come up soon.

Here's the link to my wow.exe(4.3.0.15079): Filebeam - Beam up that File Scottie!

I'm glad if it helps u.

P.S. Maybe the different offset of client cause this problem.

[Jadd]

It'll be the hack trying to call functions with the wrong offsets. Blizzard don't care about hacks any more.

[homer91]

It'll be the hack trying to call functions with the wrong offsets. Blizzard don't care about hacks any more.

What do you mean by that? How come they dont care anymore?

[Jadd]

What do you mean by that? How come they dont care anymore?

Warden hasn't been updated in a long time... they add scanning addresses sometimes (very rarely), but it's been a very long time since they've actually added any new methods of protection.

[Require]

Warden hasn't been updated in a long time... they add scanning addresses sometimes (very rarely), but it's been a very long time since they've actually added any new methods of protection.

Probably because they know they aren't able to protect everything. Maybe it has something to do with the fact they don't want to waste any time into protection when new games are in development?

[xalcon]

I wouldn't say they don't care. There are too much players who pay for the game, they would loose a big chunk of them, when they "don't care" anymore :P Like Require said, they might not have enough ressources to reverse every hack on the "market" and implement a fix against it, but they still try to find us :> Warden is not the only thing they have to find out, that we do things they don't like... I wouldn't wonder when they have a department of people who are looking for suspicious players.

[miceiken]

How about we let the pros answer what is easy to recognize and not? Enough of the theoretic bullshit already

[Xelper]

The last 'ban wave' was in March 2011. This wasn't a result of any client side detection. The developer of PiroxBots got lazy and instead of reading memory from the client to determine digsite locations for archaeology, he sent a script command to WoW which sent chat to the server in a private channel. This caused the server to send the locations back to the player in the channel, which apparently Pirox already had code in place to monitor. Blizzard does however log all chat, so it was simply a matter of running a script to search all of their chat logs for data that matched the bot's data format.

The previous banwave before that was in January 2010, for LuaNinja. Blizzard implemented a brand new system of detection just to find LuaNinja, Cypher had explained it at one point or another.

I think it is safe to say that if Pirox hadn't gone and pretty much screamed "I am running a bot, ban me!" at Blizzard, the last real update by Blizzard for WoW over 2 years ago.... that is an eternity when it comes to hacks and the gaming industry.