Alrighty, so I know a lot of you are so tired of people asking for EUD help.
But! This one is not like the others. I am not attempting to stop them via SC Maps, I am going to create a third-party app. to stop hacks.
I never messed with CE before, I used Ollydbg.. but I can't remember how to use it/don't have it anymore.
(So if you want you can help with either CE or ollydbg)
Basically, I need to know how to find the address, thats it. Just need to know the address that is changed/added when a hack is injected.
Any help would be appreciated, thanks
None.
You can search for ollydbg to find your old thread. What happened to your friend who knew how to use it?
I'm afraid we'll need the assembler gurus to help you with this, as when I tried olly, I couldn't figure it out either. I think the hacks are variable, so you can't look in just one location (so you need your third party app to do so).
If your third party app doesn't actually change SC's memory, it's probably in line with SC's EULA, and thus legal (I use artmoney to view download status because it can't/shouldn't be detected by warden).
"Parliamentary inquiry, Mr. Chairman - do we have to call the Gentleman a gentleman if he's not one?"
An artist's depiction of an Extended Unit Death
Basically, I need to know how to find the address, thats it. Just need to know the address that is changed/added when a hack is injected.
1. Attach CE to an instance of StarCraft.
2. Start a search with an unknown initial value.
3. Search for "Unchanged value" repeatedly to get rid of instances of constantly changing values. This is to get pseudo-static values.
4. Inject hacks
5. Search once for "Changed value" to find the addresses that had their values changed when the hack was injected.
6. Close StarCraft and open it to remove the hack injection.
7. Re-attach CE to StarCraft. Keep the current search.
8. Repeat 3-7 until you have a confident list that these addresses are being altered by hacks.
That's pretty much it. A lot of the addresses you'll find will eventually change when you do things in the program, so while doing step #3, you may want to click menus, join games, etc. to get rid of values that are less static. Then it's just picking the right addresses and values to read to detect when a hack is injected.
If you want to detect this through other clients, you can do these steps, except with a friend injecting the hack (both join a game, run through steps 1-3, have him do #4 in the channel, join a game again, run through steps 5-7). It would probably work in the lobby, too, so you could do it as a host without having to leave and create a new game.
This is what I would do, and what I remember doing when trying to make anti-hack EUDs. Hopefully it's some use to you.
