[WingmanReloaded] Auto (Flask, Quit, Mine, Spell) & Loot (Manage, Filter, Click)

[Selmia]

After having some troubles I was able to fix everything except Auto Mines, any suggestion how to make it work I ran the wizard and everything but everytime I place mines is doesnt do anything. Except of that really amazing thing you created here, you definitely earned a donation from me aswell.

[noneyatemp]

How would the item filter look for having boots that have > 50 life and > 75 in total resists look like?

[thebbandit]

After having some troubles I was able to fix everything except Auto Mines, any suggestion how to make it work I ran the wizard and everything but everytime I place mines is doesnt do anything. Except of that really amazing thing you created here, you definitely earned a donation from me aswell.

There is a method of determining the status of any of the pixel checks, you will need to use Show Gamestates. Try and calibrate your Detonate mines, then go and open the Show Gamestates menu to confirm if the mines are being detected. If you see that they are being detected but are not being fired, it may be caused by a different hotkey assigned ingame than "D"

How would the item filter look for having boots that have 50 life and 75 in total resists look like?

Something like this would be what you want to make:

{"Affix":{"Affix1":"MaximumLife","Affix1Eval":">","Affix1Min":"49","Affix2":"PseudoTotalResist","Affix2Eval":">","Affix2Min":"74"},"Prop":{},"Stats":{"Stats1":"ItemClass","Stats1Eval":"~","Stats1Min":"boot"}}

Just copy the above text to the clipboard and hit Import Loot Filter in the CLF.

The itemclass is under stats, and the affixes you were looking for are PseudoTotalResist or PseudoTotalEleResist and MaximumLife

[Genocyber]

20191201213151 , Client Log Found , C:\Program Files (x86)\Grinding Gear Games\Path of Exile\logs\Client.txt
20191201213151 , First Load Results , The Southern Forest , Took 0.016588 Seconds
20191201213322 , Client Log Found , C:\Program Files (x86)\Grinding Gear Games\Path of Exile\logs\Client.txt
20191201213322 , First Load Results , Oriath , Took 0.030668 Seconds
20191201213340 , Zone Change Detected , Baleful Hideout , Took 0.001978 Seconds

The script seens to have worked fine here.

Also, the new update working flawless. Just the hud still hidding the quicksilver flask status, this is minor tho.
TY

[thebbandit]

Also, the new update working flawless. Just the hud still hidding the quicksilver flask status, this is minor tho.
TY

That's good to hear, I had a feeling it was the file object assignment.

I have some good news about multithreading coming soon! Will be sharing more as I work on it

[berkefe]

That's good to hear, I had a feeling it was the file object assignment.

I have some good news about multithreading coming soon! Will be sharing more as I work on it

So thats why after client.txt file update wingman using so much cpu. It's around 20% with ryzen 3600. It was around 1% with 7.04 version.

[noneyatemp]

Been messing around with the loot filter and I can't figure out the stat "EleDPS". I figured out the PhyDPS stat but the EleDPS looks not to honor the value or I don't know how it calculates EleDPS.

On poeprices.info has the rare bow EleDPS @ 115. The filter is set to save it if > 70. However, it sells the bow to the vendor.

-Export from WingmanReloaded
{"Affix":{},"Prop":{"Prop1":"RarityUnique","Prop1Eval":"!=","Prop1Min":"1"},"Sta ts":{"Stats1":"ItemClass","Stats1Eval":"~","Stats1Min":"bow","Stats2":"EleDps"," Stats2Eval":">","Stats2Min":"70"}}

Any ideas?

[thebbandit]

So thats why after client.txt file update wingman using so much cpu. It's around 20% with ryzen 3600. It was around 1% with 7.04 version.

It should definitely not use that much cpu resources, at most it should be around 3.5%. You are getting that cpu load with the newest patch 07.12?

Been messing around with the loot filter and I can't figure out the stat "EleDPS". I figured out the PhyDPS stat but the EleDPS looks not to honor the value or I don't know how it calculates EleDPS.

On poeprices.info has the rare bow EleDPS @ 115. The filter is set to save it if > 70. However, it sells the bow to the vendor.

-Export from WingmanReloaded
{"Affix":{},"Prop":{"Prop1":"RarityUnique","Prop1Eval":"!=","Prop1Min":"1"},"Sta ts":{"Stats1":"ItemClass","Stats1Eval":"~","Stats1Min":"bow","Stats2":"EleDps"," Stats2Eval":">","Stats2Min":"70"}}

Any ideas?

Take the item, and then use item info hotkey, it will show the graph page with information about the item. If you look at the stats section you will see the dps readouts. For ele dps its simply the weapon attack speed multiplied by the average elemental damage.

[noneyatemp]

It should definitely not use that much cpu resources, at most it should be around 3.5%. You are getting that cpu load with the newest patch 07.12?



Take the item, and then use item info hotkey, it will show the graph page with information about the item. If you look at the stats section you will see the dps readouts. For ele dps its simply the weapon attack speed multiplied by the average elemental damage.

Thanks. "EleDps: 52.470000" . EleDPS !edps.

[berkefe]

It should definitely not use that much cpu resources, at most it should be around 3.5%. You are getting that cpu load with the newest patch 07.12?



Take the item, and then use item info hotkey, it will show the graph page with information about the item. If you look at the stats section you will see the dps readouts. For ele dps its simply the weapon attack speed multiplied by the average elemental damage.

Yes i'm getting so much cpu load after you added client.txt file feature. With 07.04 its just 1%..

[thebbandit]

Yes i'm getting so much cpu load after you added client.txt file feature. With 07.04 its just 1%..

That's definitely not good, but I am not showing any kind of difference on my end. The script is still running between .1 and .7 % CPU load, I popped open task monitor and watched on the second monitor. it never went above .7%

Gather this information:

1. Does the script seem to still work, or does it hang when this occurs?
2. Does it always occur at script start or only when you do something or use a specific hotkey?
3. How large is your client.txt file
4. What AHK version do you have installed?
5. please use the testbench in your wingman directory and copy the results from the error.txt file
   Make sure you load into a few zones for testing purposes.
6. Exit the script, and open it in a text editor. Find line # 2014 in the PoE-Wingman.ahk file and put the ; character in the start of the lines

   	;Gosub, CheckLocation
   	;SetTimer, CheckLocation, 15

   Start up the script and then see if that resolves the CPU load issue.
7. If that doesn't affect it, try using fresh install folder with no INI, then configure your log location.
   See if that makes a difference
8. Then your desktop resolution
9. If you don't have 1080 height, have you resampled your FindText strings?

Then if you would submit all of that onto a new Bug Report thread, we can attempt to get to the bottom of that.

[Robertuss10]

Is there an option to hide Autoflasks, Qs and Autoquit from showing on my Health orb? Or atleast move it somewhere else? I would prefer to hide it or move to top right corner.

[thebbandit]

Version .07.12 December/03/2019
--------------------------------------------------------------------------------
Reworked how the Id/Vend/Stash hotkey starts
    Now scans for just OnChar and OnInventory at very start
    Using the location status it determines if it should look for the stash
    Searching for vendor after stash now only happens in hideout
        thinking of adding vendors for each town to use in town as well
    now opens inventory nearly instantly when out in the field
        press twice to open inventory and then Id everything

Fix for CLF edit menu and Export msgbox not being AlwaysOnTop
    Will once again display over the main window

Warning for Missing Client.txt file is now always on top

Fresh install will default to Client text in steam library on the C: drive

Big thanks to tsivilay for their contribution of a reworked log parser!
    They have created an alternative method of gathering the current location
    Massively faster than the previous method, measuring in MicroSeconds
    Now it checks all lines since the last loop, and should ALWAYS capture changes
        Because of this, the loop can run at a much slower rate
    Removed some of the old code that is not needed

Hope the client log issues are finally resolved for good.

[anyhtinggoes]

It was working now it's giving me this

Capture.PNG

[CornFlake101]

Getting the same error as Anythingoes!