Memory patch is up, RIP D3

[Ramon125]

My guess is that Blizzard anti hacking team figured out a way to trap all 3rd tier software users in a more reliable way.
This obfuscation thing is a just a lure. The way to bypass it, will be the way to catch you.

Are you scared?

[Zt1mQ]

My guess is that Blizzard anti hacking team figured out a way to trap all 3rd tier software users in a more reliable way.
This obfuscation thing is a just a lure. The way to bypass it, will be the way to catch you.

Are you scared?

they are retarded, 100% sure this change is smth like new standard for their product, mb provided by activision not by blizzard.
However, this game without th is piece of unfinished raw slack-baked mater, how to play it without th lul?)))
if blizzard will start to ban for th - i accept the ban #fuck_wyatt_cheng

[Koogar]

Not even afraid !! Without th d3 will be tasteless, if they ban all those who use it, D3 will be more than a big childcare, rip D3 in this case

[nibbee]

Im just wondering that what are the ods that this will work again? 50/50 or even worse?

[ch25]

Odds are as high as programmer motivation

[ak47.mobil]

My guess is that Blizzard anti hacking team figured out a way to trap all 3rd tier software users in a more reliable way.
This obfuscation thing is a just a lure. The way to bypass it, will be the way to catch you.

Are you scared?

Y. Scared^^ Of course. Stop trolling pls^^

Im just wondering that what are the ods that this will work again? 50/50 or even worse?

Stay patient. Wait till friday or some days after season start. Friday maybe a new little patch/hotfix. Why should he work twice? Play without it^^

KillerJohn, thx for great work for diablo community for many many years ))

[Indecency]

I just found out about THUD on the d3 forum today, didn't even know it existed... (((

[mrpopos10]

Game really isnt playable for me without TH lol. Shame really

[ADV2015]

Game really isnt playable for me without TH lol. Shame really

Hi !

you just need a little time to get used to playing properly.
Just w8 & see...

[--Archangel--]

Well this sucks. I was counting on S13 holding me over until Surviving Mars releases in a couple of weeks. If it's a false alarm I wish KJ good luck in quickly getting around it. If it truly does kill THUD, I'll just thank KJ for his hard work and greatly extending D3s life for me. I agree with those who say they really can't enjoy the base game alone anymore, if THUD is gone, D3 will probably be uninstalled to free up some much needed HD space.

[adventuremode]

if you try the 32bit there is no more message about can't read memory the new message now says it can't detect battletag and the 64bit says can't read memory so not sure what the diffrence is just thought id share

[0vektor]

Any chances it's a) just a regular patch -> easy fix?
If it's b) protection added, is it hard to fix?

[KillerJohn]

There is no easy fix for this.

Structs had static addresses in the past. At each patch (due to recompilation) those changed and I had to "teach" HUD to the new addresses.
Now the static addresses are gone, and they are dynamic every single time you start the game (I am not sure if they can change while the game is running).

Even if HUD could dynamically detect those addresses, it would be slow (full memory scan) and the other problem is a new kind of "trap" which cause a game client crash if you reach the trap.
So a full memory scan is not even easy to archive, however there is a solution: pause the game process, scan the memory for the addresses and then resume.

Also there are other changes (for example, a very vital property called PlayerDataIndex is gone from the memory and it is/was used to know which player is yours in the game) which makes the life even more complex...

Based on the above, I think there is only slight chance that HUD will ever work.

[xblade2k7]

The dynamic memory (DMA) usually changes in each load, that is, when starting the game, when entering another game mode or in the maps load/changes.

But if you use ASM for example, obtaining a dynamic address whenever you need it is not difficult, for example mov eax, dword ptr [esi + 00000358](32 bits)

64 bits mov rax, qword ptr [rsi + 00000358]

in EAX/RAX ESI/RSI + 358 is saved, therefore ESI/RSI could always be saved in this way.

Mov [my code], esi

always in my code will be the base ESI/RSI and + 358 will have the address we are looking for and will never fail, then you can add flags if you need to make comparisons and get the same results.

[JarJarD3]

From MSDN:
EncodePointer function

Encodes the specified pointer. Encoded pointers can be used to provide another layer of protection for pointer values.

Encoding globally available pointers helps protect them from being exploited. The EncodePointer function obfuscates the pointer value with a secret so that it cannot be predicted by an external agent. The secret used by EncodePointer is different for each process.