[AH Bot] HappyAuction

[ztnko]

Found some bug - this item was bought with haItemStat('Critical Hit Chance').value1

[slained]

I guess you can write something like && !haItemStat('Increases Critical Hit Chance').value1 for now, not sure probably something like that

[ztnko]

is it intended that bot clears user.log every start?

[daxmagex]

-- get user buyout
local buyout = haFilterBuyout(2000000)

-- get user DPS using "Legendary or Set Item" input box
local dps = tonumber(haFilterUnique()) or 0

-- check input
if buyout <= 0 then
	haAlert('Set buyout!')
elseif dps <= 0 then
	haAlert('Set minimum DPS!\nuse "Legendary or Set Item" input box')
else
	-- clear unique input so search can work
	haFilterUnique('')

	while true do

		-- update buyout with randomize
		haFilterBuyout(Buyout, true)

		-- search
		if haSearch() then

			-- select first item in list
			haListSelect(1)

			-- get item dps
			local item = haItem()

			-- if item dps higher than requested dps buy!
			if item.dps >= dps then
				haBuyout()
			end
		end

		-- example of random sleep (between 0 and 3 seconds)
		haSleep(0, 3000)
	end
end

It gives me an error where I compare boolean to an number. What exactly am I doing wrong? thanks

[ChuiChu]

I checked the bot out and it's quite interesting.

My question is this: Is it possible to have random delays when using the SnipeBuyout? I saw how I can configure the delay but it's a flat 600/1000/etc. msec delay. Is it possible to configure a random delay, for example a 300-1500 msec delay

Forgive me if this is a silly question, I'm not very savvy when it comes to programming

its already included. haSleep(0, 3000) is random between 0 and 3 sec

setup snipeDPS.lua you're gonna have to learn lua though.

@chui left on last night again. I don't know if its because my computer lagged but it occasionally missed stat i was searching for, i lost 14 mill on items without stats

I'm gonna write another if statement to check on stats before it gets into the buy loop for now.

if youre using haFilterStat() it does a substring search and may grab stats like critical hit chance out of class skills like that screen shot shown above. looking into fix

Hi,

Is it possible to:
-View the current account's gold (i.e. compare player's gold to item.buyout -> don't attempt to buyout if not enough gold)
-Interact with unique item autocomplete (i.e. bot types in 'Windforce' -> select 'Windforce' from list. Currently it will select 'Windforce [Legacy]' as that is first.)

Thanks

ill add acct gold to todo list. and make it so you can specify the drop down row you select with uniques.

Found some bug - this item was bought with haItemStat('Critical Hit Chance').value1

ya it searched and found the critical hit chance in that last stat. ill look into this

is it intended that bot clears user.log every start?

yes... i may make it just increment logs in future.

-- get user buyout
local buyout = haFilterBuyout(2000000)

-- get user DPS using "Legendary or Set Item" input box
local dps = tonumber(haFilterUnique()) or 0

-- check input
if buyout <= 0 then
	haAlert('Set buyout!')
elseif dps <= 0 then
	haAlert('Set minimum DPS!\nuse "Legendary or Set Item" input box')
else
	-- clear unique input so search can work
	haFilterUnique('')

	while true do

		-- update buyout with randomize
		haFilterBuyout(Buyout, true)

		-- search
		if haSearch() then

			-- select first item in list
			haListSelect(1)

			-- get item dps
			local item = haItem()

			-- if item dps higher than requested dps buy!
			if item.dps >= dps then
				haBuyout()
			end
		end

		-- example of random sleep (between 0 and 3 seconds)
		haSleep(0, 3000)
	end
end

It gives me an error where I compare boolean to an number. What exactly am I doing wrong? thanks

haFilterBuyout(2000000) sets a buyout and returns boolean (if its successful or not)
haFilterBuyout() gets the buyout value in the buyout input box

[ztnko]

ya it searched and found the critical hit chance in that last stat. ill look into this

can you give example of code how can i get exactly critical hit chance?

[ChuiChu]

not possible with haFilterStat() at the moment, im figuring it out now....

the alternative now is with stat.text (in haItem().stats array) which contains the full stat text. but thats a bit of a hassle

[Mulambo7]

Hi, thanks for this bot and for sharing it with us. I still need to look better into it but I tried the "test1" as I assume is like the gem miner. I updated the price on the gems but I just have one question and I assume it's kind of a stupid one... on the Threshold it is the profit you make by buying and selling that item right? it was 1.3 and I assumed it was 1.3 millions.

I changed it to 0.3 since I don't have much money and need to start low and it bought me a 700k helm with a 235k gem.

What am I doing wrong? :s

[ChuiChu]

keep that over 1... the bot multiplies that value by the total gem value in an item and if thats higher than the buyout price... then it will buy that item.

anyway the gem bot is a bit crippled now due to 1.0.4 change not searching gem stats.

[ztnko]

older versions haItemStat('All Resistance').value1 works fine
new version - not working...

what else change undocumented?

[ChuiChu]

its the text found in the item tooltip now... so it would be "resistance to all elements". this was part of the filter rework in 0.9.12... thought i noted in list of changes :confused:

[slained]

Chui, running multiple clients I think sometimes a stat or number is missed, is there any haFilterSet boolean or something similar like the buy out, so I can do a check

[ChuiChu]

sure i can expose that... i already have it internally but not in script.

[ztnko]

its the text found in the item tooltip now... so it would be "resistance to all elements". this was part of the filter rework in 0.9.12... thought i noted in list of changes :confused:

Words All Resistance also can found in tooltip so i don't understand the exact rules. It must be continues phrase now? So for example Attack Speed % also doesn't work? Is it case sensitive now?

[ChuiChu]

if you mouse over the item its whatever text you see there. its case insensitive and is a substring search. so "tO all ELEment" would work too.

and with attack speed it would be "increases attack speed" if weapons search or "attack speed increased" if armor... or just use "attack speed" to handle both.