Permanent closure of the plugin API and the removal of China/Asia realm support

[mddy]

delete plz

[d007]

Menthal, yikes.

Most likely he meant "menthol'

[Klamist]

AFK d3 for a several months, and I'm back this season. Before reading this thread, I was wondering why PrtSc and paste in MSpaint shows a whole black picture.
Sorry for hearing those troubles.

And I have to say, some preventions like banning Asian or Chinese realm, it won't stop the few elite hackers, but only prevent normal users. and it may force them to use or even buy those hacked version instead, if they have no HUD to use.

[Kapsonfire]

Hello KillerJohn,

its been a long time im using TurboHud and I am a programmer as well.
After reading this I found 2 easy ways and one hard way to create a communication channel between TurboHud and another Proccess. One of it can be disabled by you very easily (like blocking System.IO and so on), two others of them are impossible to fix. You coul'd make it harder, but it won't be efficient. The only way to prevent is to disable the Plugin System and make some prebuilt into binary.

[d3lak]

Indeed his system has already been circumvented by a number of people It is just no longer publicly available like it was.

[KillerJohn]

Hello KillerJohn,

its been a long time im using TurboHud and I am a programmer as well.
After reading this I found 2 easy ways and one hard way to create a communication channel between TurboHud and another Proccess. One of it can be disabled by you very easily (like blocking System.IO and so on), two others of them are impossible to fix. You coul'd make it harder, but it won't be efficient. The only way to prevent is to disable the Plugin System and make some prebuilt into binary.

would you like to share the details in a private message?

[Kapsonfire]

I'd send you the informations. Added a fourth way as well.

[Dexitac]

I'd send you the informations. Added a fourth way as well.

There hasn't been an update to potential fix your findings. Did you forward the information to KJ?

[Kapsonfire]

thank you!

yep, i did

[Kapsonfire]

There hasn't been an update to potential fix your findings. Did you forward the information to KJ?

Let me say: as long as these informations are not public, i guess there's no need to rush into a non necessary patch. I sent 4 ways to do it, and 2 of them are unpatchable without removing the full plugin system.

[thewhatguy]

That's why protecting THUD against automation will not succeed, in any scenario.

I still think every user should consider for themselves if they use automation or not.
Blizzard will not go harder on THUD since "the dev does not prevent automation". They don't care.

There a public fixes for ZyHelper available, and they will come one after another after KJ fixes them...

[Vern1701]

Right now, THUD is in a use at your own risk state (it always has been, but it's officially true as of 3 weeks ago with the S19 theme exploit). Add to it, that KJ is no longer accepting donations due to lack of interest and things get even more intense. I should point out here that another patch will be coming when S20 arrives in late Feb-early March. KJ will have three or four options when that happens:

1. Keep everything as is.
2. Implement a new system within the current program that completely changes/removes the current plugin system.
3. Create a different program altogether that could be used.
4. Pull everything and remove all mention of this program and retire from this.

Blizz hasn't sent anything out yet, but it is clear that they are more involved and engaged in things. While a method to detect isn't out, they are in the process of developing something. They will not publicly state it on any official channels, either, so be wary of that.

[KillerJohn]

Hello KillerJohn,

its been a long time im using TurboHud and I am a programmer as well.
After reading this I found 2 easy ways and one hard way to create a communication channel between TurboHud and another Proccess. One of it can be disabled by you very easily (like blocking System.IO and so on), two others of them are impossible to fix. You coul'd make it harder, but it won't be efficient. The only way to prevent is to disable the Plugin System and make some prebuilt into binary.

Thank you for sharing the information with me!
Based on your findings I have to redesign the way plugins work and probably all existing plugins must be rewritten in the future.
I am still investigating the impact of removing the whole plugin system once again and go back to a declarative syntaxt which does not have access to the data inside TurboHUD though.

[KillerJohn]

in upcoming releases I'll remove the "compiled" assembly cache to make the life of the hackers a bit harder

- HUD will start slower each time (3..10 seconds slower)

[thewhatguy]

in upcoming releases I'll remove the "compiled" assembly cache to make the life of the hackers a bit harder

- HUD will start slower each time (3..10 seconds slower)

How will that affect us normal plugin coders?