[MOD] TurboHUD <-- The very first thread TurboHUD had ever

[apanon]

You are the first! I love it!

link please ??!?

[KillerJohn]

link please ??!?

it is in the OP.

[enigma1989]

i got a new idea for the TurboHUD
for the explosion after the champion with molten i would like to have a little timer that you can move around the screen. The timer starts as soon as one champ dies.

@ARkahr... i also just found out ingame

[Arkahr]

Those are molten .... K-Boom .

[KillerJohn]

i got a new idea for the TurboHUD
for the explosion after the champion with molten i would like to have a little timer that you can move around the screen. The timer starts as soon as one champ dies.

@ARkahr... i also just found out ingame

I am not 100% sure what you need, or how the hell can it be implemented but I will look into it. the problem is that molten has no timer but an animation, and I have no idea how make a timer based on the animation. You can see: D3 hack scene is non-existing, and I can not figure out many-many things alone. The driving force of tools, hacks, bots, etc is the hacker community, but there is very few (exactly zero) who is publishing memory structures, offsets, methods. I'm peeing blood to make things work again patches, by finding the changed memory addresses, but without any real research my hands are tied. I can only make new features based on the informations I currently have from D3's memory.

[angra311]

I am not 100% sure what you need, or how the hell can it be implemented but I will look into it. the problem is that molten has no timer but an animation, and I have no idea how make a timer based on the animation. You can see: D3 hack scene is non-existing, and I can not figure out many-many things alone. The driving force of tools, hacks, bots, etc is the hacker community, but there is very few (exactly zero) who is publishing memory structures, offsets, methods. I'm peeing blood to make things work again patches, by finding the changed memory addresses, but without any real research my hands are tied. I can only make new features based on the informations I currently have from D3's memory.

On this topic - is there a subset of your tools that you would be willing to publish to support the community looking into such things? As I understand your reasons for not opening...maybe not as it might facilitate botters.

Better yet, is there an open-source resource that you are aware of that supports memory inspection of d3 process for investigative purposes, with infrastructure and current best known info embedded? I've done a lot of binary inspection, assembly-level debugging, and reverse engineering in my day, but tbh I don't have the free time required to get ramped up with all the auxillary, non d3 related stuff that goes along for the ride in a task like this.

[mkvt]

how to manually mark players on the map?

[KillerJohn]

On this topic - is there a subset of your tools that you would be willing to publish to support the community looking into such things? As I understand your reasons for not opening...maybe not as it might facilitate botters.

Better yet, is there an open-source resource that you are aware of that supports memory inspection of d3 process for investigative purposes, with infrastructure and current best known info embedded? I've done a lot of binary inspection, assembly-level debugging, and reverse engineering in my day, but tbh I don't have the free time required to get ramped up with all the auxillary, non d3 related stuff that goes along for the ride in a task like this.

Based on TurboHUD source you can make a bot 10 times better [and safer*] than DemonBuddy... Do you really want this?

*it would be safer for 10 hours, but after that Blizzard would go enraged and ban instantly everybody who reads a single byte from D3's memory... Thanks, no...

(Almost-) every single memory address and method what TurboHUD is using is available on the Internet. I'm protecting the infrastructure behind it, because with that people would be able to make for example PvP exploits, which is against my will. Optimize farming with a HUD? Yeah I give my name for that. Annoy people in PvP - NO. Make bots and ruin the eco - NO.
And my last reason is that I don't believe in opensource. The code is mine. The offsets? The knownledge? It's common. If anybody comes here and ask my offsets to read the current area in 1.0.7 PTR? Here it is, this has to be common knowledge:
public readonly int LevelAreaAddress = !PTR ? 0x17E3F14 : 0x17FD32C;
public readonly int LevelAreaOffset = !PTR ? 0x40 : 0x44;
But I will not make my code open, sorry.

how to manually mark players on the map?

The feature to show other players on minimap is already done but I don't release it until I figure out how to make this feature NOT working in PvP (read above)

[KillerJohn]

Better yet, is there an open-source resource that you are aware of that supports memory inspection of d3 process for investigative purposes, with infrastructure and current best known info embedded? I've done a lot of binary inspection, assembly-level debugging, and reverse engineering in my day, but tbh I don't have the free time required to get ramped up with all the auxillary, non d3 related stuff that goes along for the ride in a task like this.

I have to say no, because there is no good source. A lot of offsets, reading methods, f*ck even structures and theories floating around about D3 memory reading is false. And I'm not sure that without reason... The memory reading "frameworks" (especially the autoit version) are pretty much bullshit. They don't work, but not because the offsets are waaay outdated, but because they handle memory structures badly. For example, most structures are not lists, but hashtables. Most autoit attribute reading code snippets are simply bad, they treat attributes as in a list, but that structure is a double linked list. Yeahaa...

For example I spent half of my day on last week to find the character's name in memory, related to the data record of the current player (public readonly int player_ofs_name = !PTR ? 0x7448 : 0x7450. This information can not be found on the Internet. Sad... The scene is dead. R.I.P.

[enigma1989]

I am not 100% sure what you need, or how the hell can it be implemented but I will look into it. the problem is that molten has no timer but an animation, and I have no idea how make a timer based on the animation. You can see: D3 hack scene is non-existing, and I can not figure out many-many things alone. The driving force of tools, hacks, bots, etc is the hacker community, but there is very few (exactly zero) who is publishing memory structures, offsets, methods. I'm peeing blood to make things work again patches, by finding the changed memory addresses, but without any real research my hands are tied. I can only make new features based on the informations I currently have from D3's memory.

i think an easy solution would be to check1. is it a champion with molten - > yes -> is his HP=0 (does he disappear from the minimap)? -> Yes -> start timer (it feels like 3 seconds for me but im pretty sure its always the same time)

and to the scene: i think there are some pretty good people on the blizzhackers cc forum

[KillerJohn]

i think an easy solution would be to check1. is it a champion with molten - > yes -> is his HP=0 (does he disappear from the minimap)? -> Yes -> start timer (it feels like 3 seconds for me but im pretty sure its always the same time)

and to the scene: i think there are some pretty good people on the blizzhackers cc forum

ok, thanks, I can make a workaround for this, but I am questioning the usefullness of it... Is this really a useful feature?

[azgul]

Personally - I don't really see the use case of that. When it's exploding, you move out of the explosion range. When it's not - you pick up loot.

[angra311]

Based on TurboHUD source you can make a bot 10 times better [and safer*] than DemonBuddy... Do you really want this?

Absolutely, positively not. I wasn't sure that this was the case, but given that it is, I concur 100% with your reasoning!

[enigma1989]

yea sometimes as a boom sorc you dont see the explosion... maybe a warning-sound(instead of a timer) would be nice
it can also be disabled by default...

[mrdarcy]

KillerJohn,
Can't say enough about your ideas and how you create those in-game. What you have created seems absolutely awesome. I just spent 2 hrs at work reading every post!! I will definitely be donating a beer or two, and will continue to support your work!! I love seeing innovation in the shadow of a broken (yet still fun) game. Again, major kudos to your continued perseverance.