Will try this out after current race ends.
Will try this out after current race ends.
is this working for anyone? when i hit F1 or F4 i get a notification of turning it on off / disconnecting to login, but nothing actually happens
Edit PoE_AutoFlasks.ahk
Delete or comment out the following:
Save the edit. Reload the script.Code:baseMgrPtr:= 0x677AE0 ;0x677AA0 ;0.10.1e, delete for script to try to auto-scan for it in newer versions, scan takes 4-5 seconds
The next time you press F1, a few seconds later, you will receive a notice that the new address has been found, and the script should now work.
Last edited by AK2337; 02-26-2013 at 10:59 AM.
getting this issue when i comment out the line for it to scan the new address
I've not had any issue, personally, but I do know the code in the original post has been updated. You could always just recopy it all.
Kinda noob in scripts sry.. how to change the hotkey from autoquit to menu (F4) to L Shift + P ?
Great work bdw
Last edited by Icxx; 02-27-2013 at 06:38 AM.
Awesome script, thank you so much!
hi guys, any idea what line should i change on the source code to modify the amount of hp left before it autoquits?
sorry i got no experience using ahk.
EDIT: nvmd just found it nice script thanks.
Last edited by h0v3r; 03-01-2013 at 09:47 AM.
Tried the autoquit but it's a hit and miss. Sometimes it works sometimes it just let me dies lol.
So, which is faster winkill or exit to logonscreen?
That depends, server uses different approaches when determining how fast it kicks you after you stop ponging to it's pings, for example if it happens very soon after logging int it's quite generous and you char may linger for quite some time. After some minutes it'll kick you in a little over second if you lag/trigger a breakpoint in client/whatever.So, which is faster winkill or exit to logonscreen?
Exit to loginscreen is generally considered instanteneous. But killing client window is a more reliable and precise way than sending keypresses & mouseclicks.
You can still die with this script if you get 1-shot.Tried the autoquit but it's a hit and miss. Sometimes it works sometimes it just let me dies lol.
There're a couple other factors contributing to possibility of death:
Script rechecks you life as seldom as autoPotionsWatchdogPeriod, which used to be 1 second by default. So if mobs kill you in 1 second you don't get saved. I decreased this to 100ms by default without having it eat even 1% cpu so you can go even lower to increase chances of survival.
If you network-lag script doesn't know your life is low = you don't get saved.
If you FPS-lag >> script likely fails to quit to main menu in time = you likely die.
Also previously it only pressed Esc once, so if you for example pressed esc or space yourself at rougly same time you could ruin it's chance of auto-qutting, i've changed it in latest build for it to spam Space and esc before clicking at "Exit to mainmenu" button which should probably increase it's chances of quitting.
You can also tweak autoQuitPauseBeforeClick value, which determines how long it sleeps between pressing Esc and clicking at the spot where Exit button is supposed to be, higher values make it more reliable against lags but naturally make it wait longer = may cause your death.
Also in latest build i added final failsafe of killing process in case it fails to get out to mainmenu within autoQuitSoftToleranceBeforeKill, which defaults to 2 seconds. You'll likely die anyway but who knows.
Hi, i just updated to the latest script; however, if it logs out before i die, the game will randomly seem to totally shutdown or go to the login screen. Also is it normal for the autohotkey.exe file to use about 50% of the cpu?