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

[iThinkiWin]

I don't think you are ready for this anyway, as this is just the function and not a full working script.

First you would need to get the include files, via Google search

#include <WinAPIFiles.au3>
#include <WinAPI.au3>

Func MemoryReadPixel($x, $y)
$iColor = DllCall("gdi32.dll", "int", "GetPixel", "int", $hDC, "int", $x, "int", $y)
$sColor = Hex($iColor[0], 6)

Return StringRight($sColor, 2) & StringMid($sColor, 3, 2) & StringLeft($sColor, 2)
EndFunc

and instead of "PixelSearch" you will use "MemoryReadPixel"

on start you need this:

$handle = WinGetHandle("Diablo III")
if $handle = "" Then
MsgBox(0, "", "Please run D3")
Exit
EndIf
$hDC = _WinAPI_GetWindowDC($handle)

on quit:

Func quit()
_WinAPI_ReleaseDC($handle, $hDC)
Exit
EndFunc

[MlokCZ]

In
https://www.ownedcore.com/forums/dia...erenity-2.html ([AutoIt Script] Auto press skills when off cooldown (no key spamming, perma Serenity))
he has whole script.

But If he does not recognize comment vs script, than it will probably not functionate for him. Even whole script is not enough to take and run. He have to modify coordinates and discover right color of pixel for his computer.

[kroggy]

@KillerJohn:

Disclaimer: I'm your fellow software engineer and I donated a few times to support THUD. I do not bot, but I do use macros (but they're not THUD-driven by any means).

It would sadden me greatly to see the plugin system restricted.

I have my personal plugins (which I don't think are super useful to others and/or partially overlap with other published plugins, but vary in different ways that I prefer). I don't think I'll ever go through the process of publishing them, so that will kill that part for me.

I do maintain patches for default plugins (and when I upgrade THUD I patch up my changes on top of updated code and resolve merge conflicts). I don't believe you accept patches for default plugins so locking that down will ruin that part for me as well.

I do maintain patches for some published plugins (or rewrite them completely if they're not good) and I do my own merges when I upgrade. Locking that down will ruin this part for me as well.

Also as a meta point - wouldn't your proposed solutions essentially revert configuration back to tweaking XML? I so hated that and I greatly enjoyed the freedom of using C#.

[sssstephane]

Hi, sory for my bad English ^^, i do program with same think for an older game, with same issues (auto + pixel paint).

For automation, i rewrite my code, and create a blacklist for the lines i dont want.
So when a plugins is load, only read it line by line and save all the lines that not blackilst in your Program, then launch it, so nobody can modify it.
With that, if i start my program, only function not blacklist can pass this point.

For painting, i modify the color with a random alpha, so pixel paint never work.

If you use option B, users can bypass by packet modification or make server and reroot to a fake github (ex : create a local server, msconfig the githud you need to your harddrive) , and then use any function they need.

[JohnWick]

do anyone knows how to add variation parameter to DllCall GetPixel ?
same like in default AHK:
PixelSearch, OutputVarX, OutputVarY, X1, Y1, X2, Y2, ColorID [, Variation, Mode]

[xhslqkr]

Please don't do it all over Asia.
There are many users who use TH in Korea.

[ToxicPhenom]

Would it be possible to just get the D3 pixels instead of a blackscreen ?
So like a "pass-through" when running D3 with THUD?
I know that it's already possible to get it through other ways, but it wouldn't require other method than now. (With standard implementation from autoit, ahk, ...)

[d007]

I'm a big fan of TH and it makes the game more comfortable, thx KJ!

But b/c of the overlay in the latest builds, harmless pixel readers don't work
(Me personally using UOpilot, but AFAIK neither 'Diablo3 Key Spammer' / 'D3 Hotkey' nor any other pixel reader work)
Btw it's working fine in non-active window (when TH inactive also) - so it doesn't solve the problem with the bot plugin since it always inactive

But many hours of playing by pressing buttons manually is very tiring and painful!
And if you compare visual comfort with physical fatigue - I'll prefer skills autocast for sure!

[gandalf12]

Hello KJ,

the Bazooka Macros from Ti... and Ri... are still working fine in 2.6.7a (S19) together with THUD although you implemented the black layer protection.
So, from my point of view you are hurting a lot of casual Diablo players more with the momentarely implemented protection then to hurt the "Pros" high Paragon 150 Bazooka speed runners.
For e.g. the cloud gaming platforms are not working any more and the casual players who are using for eg. autoit or ahk for simple key pressing "automatation" to protect ther fingers from beeing hurt or tired.
As mentioned before the high level players (payed) macros are still working and the casual low or mid range players are hard punished.
I would so much appreciate if you would remove the black layer protection.
Nevertheless its only on you to make the rules and to decide.
With regards..

[d3lak]

Timer and Rider macros do not use any type of pixel reading my friend. Your point is invalid.

[gandalf12]

Timer and Rider macros do not use any type of pixel reading my friend. Your point is invalid.

My "friend" and exactly thats the point. Bazooka for high level runs is still working fine. All other builds in any situation can be run with no macro (pixel reading macro) or simple time based keyboard or mouse macros.
So, KJ´s black layer protection does not effect the players at all. In no way. As mentioned above Bazooka is working al all other is played with time based solutions.
The only players who are affected are these who need to have pixel reading for other reasons then effective gameplay.
For e.g. cloud gaming platforms or recording reasons.
So again from my point of view :
punishment or effect on high level gameplay (or gameplay at all) 0,00000 %
punishment for all others 100%
I think KJ should think about it if this is the way he wanted to go..

[iThinkiWin]

you are missing the point. KJ doesn't care if you macro, he cares that people are using macros with his software, and hes right there's a blue post on diablo forums this week that was complaining about thud, stating some of it is okay but its also doing things they dont like.

again, KJ doesnt want anyones macros reading his shit.

[gandalf12]

again, KJ doesnt want anyones macros reading his shit.

I am fully up with you and KJ and support this.
But again you didn´t get the point.
NOOOOOOOOOO, one is using macros anymore who are based on TH pixel data.
You dont have to use pixel reading automation based on THUD overlay, to play high level endgame content (GR 145-150).
All needed automation can be done by time based solutions.
So black screen protection does not affect game play at all, in no way to play efficient high level content.
But it does affect players with cloud gaming platforms etc...
So, got it what i am talking about?

[xblade2k7]

Timer and Rider macros do not use any type of pixel reading my friend. Your point is invalid.

your coeficency menthal too dude

[d3lak]

your coeficency menthal too dude

Menthal, yikes.