Search found 3 matches

by SneakyOne
Mon Aug 21, 2017 2:44 pm
Forum: General Gamehacking
Topic: StarCraft 1.18.1.1396
Replies: 15
Views: 5128

Re: StarCraft 1.18.1.1396

It's the same protection EAC uses, stripping handles access from the shielded process (that's why you can't debug via VEH, as injection fails) as well as several executable code integrity checks :) There's a reason I wrote a big-ass PDF explaining the cheat system in SC2. Same applies here, just us...
by SneakyOne
Thu Aug 17, 2017 5:34 pm
Forum: General Gamehacking
Topic: StarCraft 1.18.1.1396
Replies: 15
Views: 5128

Re: StarCraft 1.18.1.1396

The culprit is ClientSdk.dll , that's where the "goodies" are. And they use same Battle.net.dll techniques to shield process (anti: INT3, HWBP, all kinds of other interrupts, RDTSC, OpenProcess, etc.). Will see if my tricks still do the job up to a certain point :) Hmm.. I renamed ClientSdk.dll to:...
by SneakyOne
Thu Aug 17, 2017 5:01 pm
Forum: General Gamehacking
Topic: StarCraft 1.18.1.1396
Replies: 15
Views: 5128

Re: StarCraft 1.18.1.1396

Has anyone figured any tools or a way to use Cheatengine in this game? It seems to block writing to it. The debuggers in Cheatengine either cannot inject or the game closes when attached to. It appears it can be worked on due to the screenshot above but there is no posting how to get the game to all...