Blizzhackers

If you are only hooking in to capture whats currently on the screen are the chances good they will ban for that or be able to detect it?

If your not making any changes, or modifying anything in memory, it's generally pretty safe.

This of course is based on past experience, and Blizzard might be really gungho at the D3 launch to try any catch anything they can.

As always I think it's best to consider that you may get caught, and then decide whether or not you still want to do it.

Quick heads up though, there's a fancy lil button called "PrtScn" or "Print Screen" depending on your keyboard, and I'm pretty confident that will do what your looking for, with no risk of getting banned.

Problem is with Aero on you don't get anything doing that. Then again disabling Aero is probably worth the extra the safety of not injecting.

I wouldn't hack D3 for the first few months, until they finish banning all the retards. Get all your hacking out during the beta, and then wait patiently until they stop caring or you KNOW of an undetected method. If you discover something, keep it to yourself.

Another way to do it might be to run d3 from a virtual machine. Then do the screen scraping from the parent OS.

what fun is a secret if you have no one to share it with?

Why take all the time to run D3 from a virtual machine... You could either do what nGnalucarD said or just hook VirtualQuery in KERNELBASE. Whenever it scans, just remove the modifications, and re-enable them when it isn't (if your not capable of making full anti-warden). This method should keep you safe as long as you don't share the hack.

Then again, you could codecave the hook (as long as you don't share the hack). Also what FireFromTheSky said is so true. There's people like me who wants to do that, but people like Sheppard who just wants to release everything for a "knowledge database". I don't have a D3 beta; I'm waiting for the game to be released. I never played any Diablo game and I wanna play with my friends. A simple safe map hack and some exploits will do for me .

Security through obscurity it is.

People with too much time want to babysit warden every ~6-8 weeks or play cat and mouse with "pemanent" solutions.

There is a time and a place for everything. If you find something so-so, share it, but if you find something game-breaking, keep that shit to yourself and make some money; I'm not rich. After you squeeze the market for every last penny, release it and watch everyone rage (so hard). I've had so many "friends" fuck me over its unbelievable.

case 1: the program you wrote is not publicly available: no, you won't get banned for that. There are a bunch of applications that take ingame videos or screenshots by hooking into the application. To not annoy costumers using these programs Blizzard only uses a blacklist of known-to-be-bad modules.

case 2: you release what you wrote. Blizzard will hash it (if you are important enough so that warden-guy bothers to do so), find it in their applications memory and ban you. If you don't stop warden that is.

Do Blizzard care if you use MPQ editing or memory injection to change things that have no baring on gameplay and couldn't possibly be used to cheat? Such as the appearance of your character?

Also, considering the fact you can't take your single player characters over into multiplayer, do they care what you do as far as hacking goes in SP only?

There is no single player only in D3.

Fraps does this. I'm fairly certain that they will not be banning for Fraps.

not sure how their detection will work with d3 but if its memory signatures then it doesnt really matter what it is your hack does, they will need a sample of it and will detect it no matter how it works unless you manage to stop it

Yes, FRAPS does D3D/OGL function hooking (on the Present() call that blits to the screen). So you have the option of injecting your screen scraper into FRAPS and then just grab the frame as FRAPS draws its little yellow numbers overlay.