[AH Bot] HappyAuction

[DripDropFun]

though I read the API.html
I cannot understand meaning of "xSet() xGet()"

when they needed?
can I get another example?





oh, one more question

below example (beginning of script)
------------------
require('Core.Api')
require('Core.Events')
require('Core.Old')

haSetLogin('[email protected]','ikilledblizzard')
-------------------------------

should I insert all that 3 requires?
If I dun use old API names at all, can I remove Core.Api?

[ChuiChu]

@Fg + Rodeo: sounds like something wrong with xReset as you suggest. ill investigate next.... plz let me know how your scripts are arranged (where you place xSetLogin, how you edit login event, etc) or just PM them to me. i hate bugs i cant reproduce myself! lol.

@Chand
xSleep(1) not 500... and if youre saying the stat is not included in search sometimes just put the sleep before the search. this sounds like a d3 bnet bug.... especially if you search again without changing those filters and you get different/correct results.

@drip
xset/get is to let you maintain your own variables that persist throughout the lifetime of the HA process.... so between script resets and multiple clients.
you dont need Core.Old if youre not using the old api at all.

[Orbiter87]

I noticed that when running .41 the message box that appears when changing currency would close it self automagically after using haClick, this is not the case with .48 however. Any idea why?

[ChuiChu]

i had a popup closer every script frame (between every function call) which i removed for performance reasons

[Orbiter87]

i had a popup closer every script frame (between every function call) which i removed for performance reasons

Allright, it's no biggie. xGetGold() and haGetGold() both return 0 on .48 though, which makes things complicated. Any reason as to why xGetGold returns 0 and not nil (or -1) on fail? Makes it hard to differentiate between an actual 0 value and an error.

[dacoshild]

How to put search for multiple items? For example 1. search will check ring and 2. search will check amulet with another stats. My script looks like this so far and I have no idea where to put another one with its stats. Thanks for help and awesome work!

function SnipeBuyout()

local buyout = xGetBuyout()

if buyout <= 0 then

xSetBuyout(10000000, true)
xSetPrimary('armor')
xSetSecondary('ring')
xSetStat(1, 'strength', 3
xSetStat(2, 'vitality', 3
xSetStat(3, 'attack speed %',
xSetStat(4, 'critical hit chance', 4)
xSetStat(5, 'critical hit damage', 2
else
while true do

xSetBuyout(10000000, true)

if xSearch() then

local item = xGetSearchItem(1)

xBuyout(1)
end
end
end

[RodeoRaider]

@Fgura: Thanks for sharing! I tried the method you suggested but it did not work for me (I added the filters to the end of the log out event). I suppose that it has to be something I did wrong or the method is script-dependent.

@Chuichu: I guess the structure of my script is pretty basic:

Main.lua:
require('Core.xxx')
haSetLogin(xxx)
require('Bots.MyBot')

MyBot.lua
Setup filters
Then do work

I do not modify anything else.

[Fgura]

V48:
Some of my bots are still stuck in the lobby

Tried yesterday, and everything worked fine. Today the result is worse: My bot(s) sometimes just stuck in the lobby screen after relog.

[CHandest]

Tried yesterday, and everything worked fine. Today the result is worse: My bot(s) sometimes just stuck in the lobby screen after relog.

It helped me a little by doing xSleep(1000) before xLocate('auction') in Events.lua as chu suggested earlier. Keeps me from being stuck most of the time.



I'm still having a problem with the bot filling in the stats. Still misses a search criteria sometimes..

EDIT: By using xSetGlobalDelay(3000) for instance the bot doesn't seem to fill in the stats slowly enough anyway. It's slow before and after entering the stat but while entering the stat it's blazing fast.

I have to use v41:-/

@Chand
xSleep(1) not 500... and if youre saying the stat is not included in search sometimes just put the sleep before the search. this sounds like a d3 bnet bug.... especially if you search again without changing those filters and you get different/correct results.

I have already tried doing xSleep(1) which didn't work. It bugs when choosing a stat - it do this too fast and xSetGlobalDelay cannot slow it down as it could in v41

[ChuiChu]

just a reminder guys... ANYTIME you are getting stuck anywhere, always place a sleep beforehand... and if your script is reset with xReset place the sleep at the beginning. i recommend around 50ms.

if this solves your problem, let me know and by how much you need to sleep by... so i can make the fix. note that from my perspective its not as easy as adding a sleep internally. i have to poll/wait on some load event to occur in d3 so i can stop the delay the instant that completes in order to max out performance. sometimes i dont wait long enough by a few millisec or an extra frame which is what causes the issue you see.


@chand... just want to confirm again the stats are always set correctly as you see them.... that the issue youre seeing is the search results dont get those stats. because theres a huge difference between the two.

@Orbiter87... does xGetGold always return 0 no matter where in gold AH? this is the second report i got about this, previous from alcor.

[CHandest]

@chand... just want to confirm again the stats are always set correctly as you see them.... that the issue youre seeing is the search results dont get those stats. because theres a huge difference

I'm sorry for not being more clear and precise. the stats are not always set correctly as I see them. If my script should search for an item with dex and vitality it sometime leave one field as 'none' so the bot only searches for items with dex which make the bot buy unwanted items.
Maybe this issue occours when the bot tries to choose a stat in the Roll-down, but it's too fast so it misclick and the field is being left as 'none' instead of 'dexterity'.

In V41 the bot could slow this proces down using haSetGlobalDelay, it cant in v48. The part where the bot clicks on the Roll-Down when doing xSetStat is going the fastest eventhough you do xSetGlobalDelay(3000) before

[alcor75]

After some test i start to believe that v48 is super cool and stable, but all the complex old script need a big retune.

I'll start mine monday and report back.

[Orbiter87]

@Orbiter87... does xGetGold always return 0 no matter where in gold AH? this is the second report i got about this, previous from alcor.

I didn't test any other pages before I downgraded back to .41, but it returned 0 on the main AH screen, breaking my script which is dependent on current gold value. If it is important for you to know if it returns 0 on other pages please tell and I will test.

[ChuiChu]

I'm sorry for not being more clear and precise. the stats are not always set correctly as I see them. If my script should search for an item with dex and vitality it sometime leave one field as 'none' so the bot only searches for items with dex which make the bot buy unwanted items.
Maybe this issue occours when the bot tries to choose a stat in the Roll-down, but it's too fast so it misclick and the field is being left as 'none' instead of 'dexterity'.

In V41 the bot could slow this proces down using haSetGlobalDelay, it cant in v48. The part where the bot clicks on the Roll-Down when doing xSetStat is going the fastest eventhough you do xSetGlobalDelay(3000) before

does this happen with vsync on?

I didn't test any other pages before I downgraded back to .41, but it returned 0 on the main AH screen, breaking my script which is dependent on current gold value. If it is important for you to know if it returns 0 on other pages please tell and I will test.

well from anywhere actually... im just curious if it fails if you launch your script FROM the (gold)AH. preferably if getgold is one of the first calls. is it still 0 then...

also which locale/region are you on?

[CHandest]

does this happen with vsync on?

Thx for your fast response, Chu!

It happens, but not as often if fps is higher.

The GlobalDelay bug is easily reproduced:

In the v41 version put haSetGlobalDelay at 3000 before a script with haFilterstat now it uses a 3 secs delay with every single thing it does.
Now in the v48 version do the same and put haSetGlobalDelay at 3000 before a script with haFilterstat (or xSetStat) now you'll see it's haSetGlobalDelay=0 when actual choosing the stat from the roll-down window, everything else is ofcourse, haSetGlobalDelay=3000