|
Too many people are spreading rumors about hacking. I've listed some facts below to kill these baseless rumors.
What is/can Blizzard do to stop hackers?
They're doing everything they can. They are using Warden and they're suing the people developing/distributing the hacks. A few months ago the biggest game-hacking community site was taken down by Blizzard.
How does Warden work?
The truth is, nobody knows for sure. Warden is a black box, which keeps changing shape as it's updated. By poking, listening and sharing ideas, we've learned more and more about how it works. The following is not a fact, but a description of what most hackers generally agree upon.
Warden scans certain files/processes for changes. It does this by hashing (taking unique digital signatures) to see if the game files/processes have been altered. When you use .dll injections, you alter the game, hence changing the executing game processes memory segments, which Warden will detect when evaluating the digital signatures.
The game design has nothing to do with hacks being detectable/undetectable.
Are some hack undetectable?
As I explained hacks which uses .dll injections are all but undetectable. 99 percent of the hacks use .dll injections and the developers behind advertise their hacks as being undetectable because they claim you can disable Warden. The truth is, you can and many developers have succeeded doing so, but every single time when Warden updates new countermeassures against hacks are implemented and a wave of cheaters are banned (makes us all feel good, right? ). So although hacks using .dll injections and Warden disablers are not undetectable, you can consider them to be temporarily undetectable in a sense... So undetectability can't be garanteed, but getting banned can.
Now to the hacks that don't use .dll injections. These work by continuously reading from process memory to fetch unit locations, unit/structure production and use these data to render graphics on your screen displaying the amount of expansions, unit counters, current production and unit locations. These hacks are not very widespread and the ones that exists only offer a limited amount of basic features. For instance to disable FoW without using .dll injections, you must read all unit locations every 10-100ms from the SC2 process (unless you don't want real-time updates of the unit locations), render these units (huge work unless you render them as circles, dots, squares, triangles, which gives you a poor idea of what units you're looking at) and remove all rendered units from your screen, if they're in your field of view AND your field of view isn't on FoW, so you don't have the rendered twice... Any developer can tell you, this isn't a viable option... its too much work, and the end result won't be good unless you put A LOT of time in rendering the units (good luck) which is why nobody has or will implement disabling FoW without using .dll injection.
So is hacks that doesn't use .dll injections undetectable? Not anymore, because Warden scans for .exe signatures, so the only way to make a hack 100 percent undetectable is by not using it or by grabbing the source code, refactoring it and compiling your own assembly, which you never share. Every single time the game is patched, you need to spend a good couple of hours finding the offsets you use to find the unit locations, etc. etc. from the SC2 processes and how many people are capable of that? Only those whom have good time and enjoy looking at assembly code *yuck*.
Lesson learned?
- Blizzard is doing the best job they can to get rid of hacking.
- No hack that you have access to is undetectable.
- Game designs have nothing to do with hacks being undetectable.
- Hacking will eventually get you banned. If Warden doesn't bust you, sooner or later the community will.
- Don't hack. I don't mean to preach, but for your own sake, I don't want you to lose your account.
Edit: Initially I made the thread writing VAC instead of Warden, this obvious mistake is corrected after it was brought to my attention by a site administrator.
|
also sc2 is allowed by law now (in the new user agreement) to perdoically scan the pc ram to see what processes are in use, that plus a list of easy to find hacks = ban waves :D
|
- No hack that you have access to is undetectable.
Sounds like quite the statement, have you looked up everyone of them?
|
While I personally enjoy looking at assembly code, the whole ordeal seems like a lot of work. Also, I don't want to get banned.
|
Germany2896 Posts
As I wrote in your previous thread:
On February 20 2012 00:00 MasterOfChaos wrote:
I also disagree on the viability of external maphacks. Just their screen on a secondary monitor, or even second PC in the network. Rendering the map, and static images for each unit type is good enough. I'd prefer it over an internal maphack any time. You don't need to scroll around to see everything, you can stream without the stream picking up the hack,... They are also pretty easy to develop.
> Every single time the game is patched, you need to spend a good couple of hours finding the offsets you use to find the unit locations
In SC1 updating offsets took a few minutes unless blizzard updated their compiler, I even automated the process for my plugins. And even when the auto-finder failed it was typically quick, since you already know how to find them, from the first time you found them.
|
External maphacks are more viable than DLL injection, if you only go for the observer/MH stuff. If you read the stuff from memory and create the map yourself, you can actually produce an overlay. If you disable the FoW completely, you can pretty much obviously fuck up since you don't know what is scouted and what not. Furthermore: a) You don't need to update the offsets from patch to patch (proof the discontinued MH which name I won't tell still works) b) They are still not detected by warden if you don't scan the memory like fucking crazy.
Another note: **** updates regularly according to the Warden scan offsets, so even the injection is not detectable for the paying user. GG.
I don't think a maphack gets you far, ofc it lets you concentrate on your macro but it doesn't really make you better. A better macro player will always win over a maphacker, always.
|
So basically warden gets you by evolving and then getting the people who got under the old version of Warden, thats pretty genius. Basically that means the only people who will continue to cheat through the years are those who are willing to pay for SCII multiple times.
|
Blizzard should add a second layer, because this "Warden" is pretty shitty. How about nProtect or GameGuard eh?
|
I had heard a LONG time ago, that it wasn't a maphack out, but a production tab hack. You can see everything they are making without looking on the map, then it's all down to unit control. aka you can play as greedy as possible.
|
On February 19 2012 23:59 dehdar wrote:cut
countless lies.
You don't even know how hacking works, you just trust blizzard, and that is what hackers are looking for 
On February 20 2012 00:04 eYeball wrote:Sounds like quite the statement, have you looked up everyone of them?
He just hopes for it, if only he would know how things work really he would put himself in shame on this forum
On February 19 2012 23:59 dehdar wrote:
- Blizzard is doing the best job they can to get rid of hacking.
Wrong. They could eliminate hacking permanently if they would put 1% of the effort they did to make this game unpiratable
edit: At the end, I wonder: Are you an hacker , with sufficient knowledge to say what you just posted?
|
On February 20 2012 00:03 TibblesEvilCat wrote:
also sc2 is allowed by law now (in the new user agreement) to perdoically scan the pc ram to see what processes are in use, that plus a list of easy to find hacks = ban waves :D
They have done this for a while now. Back when I played WoW they did the same thing.
|
United States2813 Posts
warden didn't have a good record vs me when i map hacked + botted in d2 for years lol
|
On February 20 2012 00:04 eYeball wrote:Sounds like quite the statement, have you looked up everyone of them?
I'm assuming if you have access to it, so does Blizzard.
On February 20 2012 00:06 VoO wrote:
Blog rather than thread?
Links to hacking site, really?
External maphacks are more viable than DLL injection, if you only go for the observer/MH stuff. If you read the stuff from memory and create the map yourself, you can actually produce an overlay. If you disable the FoW completely, you can pretty much obviously fuck up since you don't know what is scouted and what not. Furthermore: a) You don't need to update the offsets from patch to patch (proof the discontinued MH which name I won't tell still works) b) They are still not detected by warden if you don't scan the memory like fucking crazy.
Another note: **** updates regularly according to the Warden scan offsets, so even the injection is not detectable for the paying user. GG.
I don't think a maphack gets you far, ofc it lets you concentrate on your macro but it doesn't really make you better. A better macro player will always win over a maphacker, always.
The site has been taken down.
No doubt, if I was personally going to develop and use a hack, I'd base it on RPM and not .dll injection. However DLL injection is by all means a better option (except issues with being detectable). You write a lot of ifs, but you can toggle FoW off/on, there is even a very well documentated wikia, which explains how you can disable FoW without your units attacking enemy units on ramps. It's quite hard to comprehend how much time people invest in maintaining this wikia... you'll also find plenty of code examples, tutorials, updated offsets, etc. etc. Off topic!
I fully agree with your last statement though. In SC2 the better player will always win, maphack or not... unless they are even.
|
On February 20 2012 00:31 dehdar wrote:Show nested quote +On February 20 2012 00:04 eYeball wrote:- No hack that you have access to is undetectable. Sounds like quite the statement, have you looked up everyone of them? I'm assuming if you have access to it, so does Blizzard. Show nested quote +On February 20 2012 00:06 VoO wrote:
Blog rather than thread?
Links to hacking site, really?
External maphacks are more viable than DLL injection, if you only go for the observer/MH stuff. If you read the stuff from memory and create the map yourself, you can actually produce an overlay. If you disable the FoW completely, you can pretty much obviously fuck up since you don't know what is scouted and what not. Furthermore: a) You don't need to update the offsets from patch to patch (proof the discontinued MH which name I won't tell still works) b) They are still not detected by warden if you don't scan the memory like fucking crazy.
Another note: **** updates regularly according to the Warden scan offsets, so even the injection is not detectable for the paying user. GG.
I don't think a maphack gets you far, ofc it lets you concentrate on your macro but it doesn't really make you better. A better macro player will always win over a maphacker, always. The site has been taken down. No doubt, if I was personally going to develop and use a hack, I'd base it on RPM and not .dll injection. However DLL injection is by all means a better option (except issues with being detectable). You write a lot of ifs, but you can toggle FoW off/on, there is even a very well documentated wikia, which explains how you can disable FoW without your units attacking enemy units on ramps. It's quite hard to comprehend how much time people invest in maintaining this wikia... you'll also find plenty of code examples, tutorials, updated offsets, etc. etc. Off topic! I fully agree with your last statement though. In SC2 the better player will always win, maphack or not... unless they are even.
Yeah, I heard from the offset Wikia and the tutorials, but didn't bother to search. I was on the site a few days ago to decompile Q*zz*'s for fun. I wrote my own external maphack/macro trainer and played with in custom games, don't think it is detectable since it doesn't read that often and runs in the JVM - just to verify my expertise with this topic... I don't think the offsets changed for 3-4 major patches, which is almost 6-7 months.
|
On February 20 2012 00:28 Silidons wrote:
warden didn't have a good record vs me when i map hacked + botted in d2 for years lol
haha those were the days, where people would look confused to you if you'd have no maphack
|
On February 20 2012 00:03 TibblesEvilCat wrote:
also sc2 is allowed by law now (in the new user agreement) to perdoically scan the pc ram to see what processes are in use, that plus a list of easy to find hacks = ban waves :D
That's pretty fucking retarded, just saying. As a hack-free user, I dont like the idea that some guy in arizona can look through my computer and see whats running and what's not. I thought it was against the law to read stuff like that.
I guess not, the government is controlled by corporations such as blizzard.
|
Honestly i have nothing against them not having a program that is able to detect all the hacks all the time,the risk for he hacker to get caught is likely not worth the reward.
But its annoying that they don't ban master + players hacking based on there replays ( aka the anti hack thread on tl ), especially now that they are openly against stream cheating which means that banning someone for map hacking when hey were stream cheating is still on par with there policy ( hell, not even perma banning, ban them for 1 month or 2 weeks to "scare" them ).
And from my previous experience with blizzard games in which you could boot ( wow ) i can tell you for a fact that i wasn't caught in my last year of playing even tho i booted, hell everyone was booting if they didn't had enough money and blizzard didn't give a shit ( hence why I started booting, you can't compete in a boot economy if you don't boot/already have money so that you can do what its called "play the ah"...but won't go into details since i assume a few guys here are/were wow players ).
You have to consider that booting was basically half of the problem with wow economy ( which is, if you compare it to what it was, messed up as hell... or at least as when i left ) so if a player booted it affected everyone, unlike sc2, yet they did not ban booters, i have to wonder why ? Is booting that hard to detect ?
I doubt that they care more about hacking in sc2 which is a game that will provide them with about 900 millions ( out of which i have no clue what is actual profit ) considering that the expansions are sold as much as the original, while wow provided them with about 1-2 billions a year only from subscriptions ( again, no clue what was the actual profit they made was ).
|
On February 19 2012 23:59 dehdar wrote:
As I explained hacks which uses .dll injections are all but undetectable.
So if they are all but undetectable, doesn't that mean they are everything except undetectable, in other words easy to detect? I think you used that phrase incorrectly.
Just trying to clear up some confusion.
|
Warden is an interesting little creature. So elusive. So... rogue.
I wonder how many people actually know it's there.
|
On February 19 2012 23:59 dehdar wrote:
Too many people are spreading rumors about hacking. I've listed some facts below to kill these baseless rumors.
The truth is, you can and many developers have succeeded doing so, but every single time when Warden updates new countermeassures against hacks are implemented and a wave of cheaters are banned (makes us all feel good, right? ).
What i seen so far on cheating forums is that all this cheats disable themself when they detect new warden version.
So noone get banned.
Lesson learned?
- Blizzard is doing the best job they can to get rid of hacking.
They do the best they can. Problem is, the best they can is very bad, compare to best others can.
- No hack that you have access to is undetectable.
in theorie yes. But easy to be undetectable for Blizzard.
Blizzard failes in anti-cheating in all there games. They did so from beginning to now. why do people act like they are good in it or even try hard. Its obvious not the case.
|
|
|
|
|
|
EPT
