[AH Bot] HappyAuction

[ChuiChu]

oops double post ^^

[sinza]

NP Im only trying to help

[RodeoRaider]

Hi Chuichu,

Before the new version is stable, can you please incorporate the red gem dps calculation fix into the stable v41? I am still losing a lot of golds everyday due to this bug .

[ChuiChu]

that feature requires the reworked code... plus new version nearly ready.

just ignore anything with red gems for now.

[Fgura]

Beta version:

Now it logs into my account after it reaches input limit but stuck at the lobby screen instead of entering to AH.

Any solution?

[alcor75]

Beta version:

Now it logs into my account after it reaches input limit but stuck at the lobby screen instead of entering to AH.

Any solution?

Check you internet, this uppen b/c of lag usually, or ah is temporeneally down.

Chui, sometime this uppen, do you already check if the auction house button is greyed?

[momozzz]

Hi Chuichu,

Before the new version is stable, can you please incorporate the red gem dps calculation fix into the stable v41? I am still losing a lot of golds everyday due to this bug .

Simply add a line to check the gem type to each of your buyout/bid restrictions. ln the readme it says:

- item.sockets: a list of socket objects containing:
- text: gem stat text. example: 'Dexterity'
- gem: gem type. example: 'Topaz'
- rank: gem rank. example: 14 for Radiant Star

So it isn't too hard to go from there until ChuiChu implements a universal fix for it.

@ChuiChu

This is more of human error/stupidity on my part but there seems to be a small loophole with people that are using modified SnipeBuyout setups and there's an item that meets stat requirements but doesn't fall beneath the maximum buyout set. l had accidentally hovered my mouse over said item which was overpriced and since the stat requirements were met, it ended up triggering haBuyout() on the actual item that was selected in data. l managed to find a way around it, but for brand new users, something like that might cause people to lose a bit of gold every now and then.

[Fgura]

Check you internet, this uppen b/c of lag usually, or ah is temporeneally down.

Not really, the old version works perfectly with my script. With this beta version my bot doesn't start from the menu, unless I add the line haSetLogin('xxx', 'yyy') to my own SnipeBuyout.lua, but it stuck at the lobby screen. How can I force it to enter to the AH when it already logged into the lobby screen?

Thank you.

[Sehae]

Not really, the old version works perfectly with my script. With this beta version my bot doesn't start from the menu, unless I add the line haSetLogin('xxx', 'yyy') to my own SnipeBuyout.lua, but it stuck at the lobby screen. How can I force it to enter to the AH when it already logged into the lobby screen?

Thank you.

I have the same problem, it happens with multiclient, the old versions go after a relog to the AH but this one stays stuck in the menu. This does not happen with a single client on. If anyone has a solution - please share it

[ChuiChu]

Check you internet, this uppen b/c of lag usually, or ah is temporeneally down.

Chui, sometime this uppen, do you already check if the auction house button is greyed?

i just fixed this assuming the issue was only allowing 600 frames for the action to complete... or 10sec on a 60hz system. which with any lag would be not enough.

yes i poll on button status until its in the highlighted state

[ChuiChu]

Simply add a line to check the gem type to each of your buyout/bid restrictions. ln the readme it says:

- item.sockets: a list of socket objects containing:
- text: gem stat text. example: 'Dexterity'
- gem: gem type. example: 'Topaz'
- rank: gem rank. example: 14 for Radiant Star

So it isn't too hard to go from there until ChuiChu implements a universal fix for it.

@ChuiChu

This is more of human error/stupidity on my part but there seems to be a small loophole with people that are using modified SnipeBuyout setups and there's an item that meets stat requirements but doesn't fall beneath the maximum buyout set. l had accidentally hovered my mouse over said item which was overpriced and since the stat requirements were met, it ended up triggering haBuyout() on the actual item that was selected in data. l managed to find a way around it, but for brand new users, something like that might cause people to lose a bit of gold every now and then.

ya buyout just buys whatever was last selected... which can easily be whatever you manually clicked. however in the latest version i disable mouse input to d3 for duration of the script.

[KillerJohn]

Hi ChuiChu!
I'm not using your tool, because I'm noob for AH, but I looked into your AH history code, and found some "bugs".

Auction history structure is based on it's type (sell = 1, buy = 2)

your "xtime" field is
- @ +0x390 when type==buy & paid==0 (outbid)
- @ +0x2F0 when type==buy & paid>0 (purchased)
- @ +0x150 when type==sell


in case type==buy:
price @ +0x330
paid @ +0x450
if (paid > 0)
{
// purchased for "paid" amount of gold (paid = price - refund)
}
else
{
// outbid. the amount of gold you get back is "price". refund is zero
}

the number of items in an order is
- @ +0x2E8 (buy)
- @ +0xA0 (sell)

the number of actually sold commodities is @ +0x118

the "id" field you are using is something I can't recognize, but
OrderID is
- @ +0x350 (buy)
- @ +0x110 (sell)

Have a nice day!

[stalkk]

Hey, does anyone have version 42B still? My main.lua doesnt seem to work with the new 44 version (lots of stuff is nil value and it crashes) and i really want the fix to dps readings with ruby socketed weapons

[Sehae]

Does anyone have a solution for the problem, when the bot stalls in the lobby after a relog? Is there some command that would get it getting to the AH on its own and even by starting it before getting in the AH interface? I did not have this problem on the previous versions, but now it is very annoying.... :@
It is strange, because when I run the script even from the lobby the first time it enters the AH, but then upon relog - it does not. I have tried adding sleep delays at the events relog but still does nothing ...

[ChuiChu]

ill be posting another update shortly. once i know the exact relogin issue... i think i may have fixed it recently since it was only given 600 frames to fully complete (or 10sec on 60hz systems).

Hey, does anyone have version 42B still? My main.lua doesnt seem to work with the new 44 version (lots of stuff is nil value and it crashes) and i really want the fix to dps readings with ruby socketed weapons

do not replace Main.lua. or at least include the first several lines of it in your original one.