D2R UgaPik - Barebones Free Picket - Autoit - Safe

[theitit]

Removing my program.

[greatscott]

Great job!

The code is clean and easy to understand. Thank you theitit for sharing it!

On my old i7-6700 computer with RTX3080, a 4k monitor, and Windows 10 operating system with 200% font size display, I encountered the following two problems. They are due to AutoIt but not your programming.

1. The coordinates returned by WinGetPos() is off. It's the actual value /3. For example, on the 4k monitor ($R, $B) should be (3840, 2160), but WinGetPos() returned (1280, 720). The whole coordination system seen by AutoIt seems to be working on this alternative coordination.

2. PixelSearch() function is very slow. Takes tens of seconds for one search. According to AutoIt forum, this is caused by Windows 10. I installed x64 version of AutoIt on the computer.

I am trying ways to resolve them but no success yet. In case anyone finds out a solution, please kindly share. Thank you!!

[Eesyytee]

Hi,

first time post for me...

just a warning that the clicks sent by AutoIt might be identifiable as injected due to the LLMHF_INJECTED flag. (Translates to: You might get banned!)

detect is mouse is really pressed - AutoIt General Help and Support - AutoIt Forums

I guess you might call a virtual driver like GitHub - hedgar2017/loki-hidriver: Virtual mouse and keyboard driver for Windows 7 and higher instead of using MouseClick. What do the other ppl here say?

[theitit]

Great job!

The code is clean and easy to understand. Thank you theitit for sharing it!

On my old i7-6700 computer with RTX3080, a 4k monitor, and Windows 10 operating system with 200% font size display, I encountered the following two problems. They are due to AutoIt but not your programming.

1. The coordinates returned by WinGetPos() is off. It's the actual value /3. For example, on the 4k monitor ($R, $B) should be (3840, 2160), but WinGetPos() returned (1280, 720). The whole coordination system seen by AutoIt seems to be working on this alternative coordination.

2. PixelSearch() function is very slow. Takes tens of seconds for one search. According to AutoIt forum, this is caused by Windows 10. I installed x64 version of AutoIt on the computer.

I am trying ways to resolve them but no success yet. In case anyone finds out a solution, please kindly share. Thank you!!

I actually saw a post about someone searching slow with pixelsearch on a 4k monitor. I'm not sure why that would make a difference, since the area is being limited anyways. I honestly don't know much about it, but are you able to temporarily try a different monitor? The system i wrote and tested this on is an older fx-8350 windows 10 1080p.

Sorry for another tin-foil hat theory! Hopefully you can get it sorted.

[xblade2k7]

in 3840x2160 dont work, miss clicks

[theitit]

in 3840x2160 dont work, miss clicks

It was written to be 1280x720. The reason for this is you are increasing the search box area, and before your character can reach the item it has clicked again to a new spot. The program can't tell that your character is in-transit.

If you want to make it work on that size window, you will need to reduce the searchable area. I commented the required lines to edit in the script, if you just mess around with those offsets you can make it a much reduced searchable area.

[xblade2k7]

is working, thanks man. Problem solved changing monitor resolution not only game res.

[theitit]

I ran into a bug while recording the vid I just posted, well two of them.

First, the game resolution bugged, as you can see in the vid, the game window is cut off at the bottom. Just looks like a d2 bug, changing the resolution, then changing it back fixed the issue.

Second, the script was only searching up and to the left of center. I didnt see anything wrong with the paste, so I deleted the file, restarted my comp and re-tried the process. It worked fine in test, as it did when i re-recorded the vid.

[aota2021]

tested it and no prevail. does not work. was their an update to the game that caused this to not work or does it need to be ran in x64 mode for x64 cpus?

[funchico]

tested here also, and it didnt work.

[theitit]

tested here also, and it didnt work.

Post specs, what window size you were running, resolution please. It really helps with troubleshooting.

tested it and no prevail. does not work. was their an update to the game that caused this to not work or does it need to be ran in x64 mode for x64 cpus?

I don't think there was an update, and the only thing compatibility would change is the search speed I believe.

[funchico]

my specs are a notebook dell g3
intel i5 10th gen, 8gb ram, gtx 1650.

tried it on 1920x1080, tried it on window mode and fullscreen, did exactly as the video and it didn't work.

[greatscott]

The author uses the default color to do the scan. When we registered the game, the game asked us to adjust the color. Therefore the color on our screen might not be the default color. You will need to use the RGB of the colors of unique, set, and rune items on your screen to replace the original color specified by the author.

[theitit]

The author uses the default color to do the scan. When we registered the game, the game asked us to adjust the color. Therefore the color on our screen might not be the default color. You will need to use the RGB of the colors of unique, set, and rune items on your screen to replace the original color specified by the author.

ooo, thats right. Does the brightness adjustment also affect text color?

You guys can colordip with MS Paint, and replace the color code with the result for unique set and rune. Use the most prominent shade on each text

Also, the only setting i use thats different is I have the brightness maxed from the slider at intro. Like to lounge back in my chair and see the game from strange positions lol.

[chezit]

I get this error. I tried adding EndFunc just to try. Same thing.