[AH Bot] HappyAuction

[samuraiofu]

Hi Chiu,
I found in this version haListIterate() will move the cursor to the d3 window and give it focus . Is this a bug or else? Thank you in advance. If you need details I can ping you and send you my scripts to reproduce bug. We always want the D3 window to be backgrounded.

[Sehae]

The bid problem is there too.

[ChuiChu]

man those are wierd bugs... in areas i didnt even touch. guess bliz changed a few things lol. ill try to get another deal going soon

for that listiterate focus one make sure youre not starting the bot with d3 focused, or it will stay wanting to focus. this is a restriction im meaning to remove however... since the change to clicks from mouseovers obsoletes it.

[RodeoRaider]

nothing....

[BebbeD3]

Hello i got the problem that i cant make a script that works can anyone give me a complet scripe so i can see how it should look like

[msk380]

man those are wierd bugs... in areas i didnt even touch. guess bliz changed a few things lol. ill try to get another deal going soon

for that listiterate focus one make sure youre not starting the bot with d3 focused, or it will stay wanting to focus. this is a restriction im meaning to remove however... since the change to clicks from mouseovers obsoletes it.

It happens basically when the input limit error wouldve occurred.
Can you please fix haLogout please? It logs out and closes the window lol.
Decent leechers will find a way to tackle this search problem with it. Currently using macro to do that function

[RodeoRaider]

Hi Chuichu,

There is one proplem I would like to report: After relogging, the bot opens AH, sets all the filters like previously set, click on Search button once and then stops (the HA icon turns from red to green).

[samuraiofu]

Thank you Chiu I understand it now. But one thing I can't make sure is how you distinguish the instance number of each D3 window, from PID ?

man those are wierd bugs... in areas i didnt even touch. guess bliz changed a few things lol. ill try to get another deal going soon

for that listiterate focus one make sure youre not starting the bot with d3 focused, or it will stay wanting to focus. this is a restriction im meaning to remove however... since the change to clicks from mouseovers obsoletes it.

[ChuiChu]

ok so what ive found so far...

1. search/pagenext/pagelast returning no results
- this happens, as some already stated, when input limit error would normally happen. its clearly a new bnet thing since stopping the bot and searching/paging right after continues to have the same effect unless you wait a little. odds are i cant do anything about this... (besides hacking into bnet servers lol). it just means delays are necessary between searches.

2. because of #1 i cant reproduce an input error -> relogin sequence. so i cant comment on Rodeo's relogin issue yet. unless you mean you started the script at the login screen? using manual haLogout with the following script seemed to work fine so i need samples that cause failure. i tested with the following:

haSetLogin(...)
haAlert('logging out!')
haLogout()
-- relogs in
require('Bots.LogAuctions') -- runs a bot

as a reminder: make sure vsync is on!

3. regarding the random bid/buyout deal. i ran the default sample bot and bought out a bunch of items without fail. so i need details/samples to reproduce as well

Thank you Chiu I understand it now. But one thing I can't make sure is how you distinguish the instance number of each D3 window, from PID ?

use your login name with if haGetLogin() == '[email protected]' then ... end. if youre using the same login on multiple regions i dont have support for that yet. haGetRegion is on todo list

[msk380]

Chuichu, as i mentioned earlier,
haLogout closes the window instead of just logging out.
Maybe it's because of locale.

My code looks like

haSetLogin
My code
haLogout

[ztnko]

find another bug:
while haSellIterate() do haSellCancel() end

sometimes cancell not all items and pass over several items... in prev version it can stack on 1st item and wait 3 mins to pass item - in this version it pass over item and don't cancel it...

[RodeoRaider]

2. because of #1 i cant reproduce an input error -> relogin sequence. so i cant comment on Rodeo's relogin issue yet. unless you mean you started the script at the login screen? using manual haLogout with the following script seemed to work fine so i need samples that cause failure. i tested with the following:

haSetLogin(...)
haAlert('logging out!')
haLogout()
-- relogs in
require('Bots.LogAuctions') -- runs a bot

as a reminder: make sure vsync is on!

Hi Chuichu,

Thank you very much for replying. My script is written as followed:
Main.lua:
haSetLogin(...)
require(Bots.Mybot)
Mybot.lua:
Set all types of filters
While loop

So my bot runs for a while, get an Input limit error, logs out, sets the filters back again (I think the bot can remember the filters and automatically set it back even if I comment out the Set filters section) and I think it click on Search button once, then the HA icon turns from red to green.

I start my bot from the Auction House -> Equipment screen. And my Vsync is on.

Looking forward to your reply!

[MATRASUS]

I just bought a couple of items for my main and in active auctions tab they appeared as items i maked bid so it is blizzard auction fail not ChuiChui/HappyAuction

[DoichinMitrev]

I put decent delays and the bot works perfeclty now, I'm even buying lots of items as I don't hit the new limit. As chui said this seems to be the best solution. Also vsync has to be on, the bot is really buggy without it.

[ChuiChu]

Chuichu, as i mentioned earlier,
haLogout closes the window instead of just logging out.
Maybe it's because of locale.

My code looks like

haSetLogin
My code
haLogout

whats your locale? RU?

also anyone else having this prob?