Updated d3helper anywhere?

[sebflex]

Missing d3h since some weeks, anyone found an updated version of it???

[batzmichtot]

hi sebflex,

i think the chance to get helper back is little to none, because on 32bit it will never run again. and i dont know if someone rewrites it on 64s.

[optume]

Too bad it probably never comes back, it's like the #2 "must have" tool for diablo 3 after TH :*(

[sebflex]

hi sebflex,

i think the chance to get helper back is little to none, because on 32bit it will never run again. and i dont know if someone rewrites it on 64s.

Why it will not run on 32bit??

[batzmichtot]

because all guys only updated the 64 frame ... so no more 32 programms

[sebflex]

So 64bit is out...anyone can/wanna update 32bit one aswell pls???

[batzmichtot]

So 64bit is out...anyone can/wanna update 32bit one aswell pls???

64 bit is out? where did you find it, can you post the link.

Thanks

[getSchwifty]

What hack/mod is TH? (I'm assuming hack.)

[oXotoXo]

I am very curious as to where to find this 64 bit D3 Helper thing. On D3 Helper Forums they say otherwise. Noone has released a 64 bit yet.
Quote from Apr. 11:

Everything you need to convert d3helper to 64bit is public on enigmas github and documented in this forum. just scroll back few pages.


3 things are currently missing in the "post-obfuscation-patchwork" branch to make d3helper 64bit running:

1) Offset for ApplicationLoopcount must be updated (i think its 0x216C2A4).
2) LevelArea cant be used anymore. it was used to detect if player is in a rift. But you can find another method to detect this.for example by reading UI controls (is progressbar visible?).
3) Loaldata.IsStartupGame can't be used anymore to detect if player is in a game. Have to find other solution for this (UI control checking for example).

After this is fixed. you have to use the new Symbolpatcher (see example in the maphack sourcecode)


but to get to this point you have to convert first from the old D3.Memory to "Memorymodel" to be able to use the 64bit features. This requires A LOT of work.
Some functions and offsets which were useful for UI reading have been removed in Memorymodel. you have to port them. see examples in enigmas maphack how to read UI controls or check the legacy branch. when you start working on it and research you will find the solutions either in the github branches or in this forum.

if you have specific questions, i am sure enigma or someone here will help.

[enigma32]

What hack/mod is TH? (I'm assuming hack.)

Hard to miss, there's an entire forum section dedicated to it https://www.ownedcore.com/forums/diablo-3/turbohud/

I am very curious as to where to find this 64 bit D3 Helper thing. On D3 Helper Forums they say otherwise. Noone has released a 64 bit yet.

There is no public working version of D3Helper.

[MrOne]

There is no public working version of D3Helper.

... do you know something about non-public?

[enigma32]

... do you know something about non-public?

I do, but I'll respect the wishes of the developer to keep it private.

If someone were to post a specification of what D3Helper does (like, very specific), then I might give it a shot.

[rvj]

D3Helper cast skill if available, or you can configure settings to cast, like elite on range, trash mobs on range, skill have x%, or skill have x value, cast if other skill is avaliable, or power active, get itens from floor by press pre defined key, change paragon, etc. D3helper is much useful in Diablo 3. I really wish it had a 64bit version. Sorry for my english.

[johnbl]

I do, but I'll respect the wishes of the developer to keep it private.

If someone were to post a specification of what D3Helper does (like, very specific), then I might give it a shot.

It's strange for it to be private, considering the source was released quite a long time ago by R3peat. The only updates for it since then have been regarding offset updates and some necromancer-specific fixes.
If someone has updated it for 64-bit, they've just updated it using your framework and R3peat's source. And none of those are private.

[enigma32]

It's strange for it to be private, considering the source was released quite a long time ago by R3peat. The only updates for it since then have been regarding offset updates and some necromancer-specific fixes.
If someone has updated it for 64-bit, they've just updated it using your framework and R3peat's source. And none of those are private.

Not strange at all. Updating to 64-bit means re-write due to how my framework has changed since first D3Helper. And while re-writing, might as well add a bunch of new features.

Anyways. MrOne is helping me with specifications, so I'm looking into creating a replacement. No, I don't need beta testers, so no need spamming me. I'll create a discord or something if I get to that point.