[AH Bot] HappyAuction

[msk380]

i would like to summarize all i know about "Bugged Mode" bug as i named it. When bot enters this mode - it only "simulates" work - 1st time i write about this mode here - http://www.ownedcore.com/forums/diab...ml#post2592241 ([AH Bot] HappyAuction). Now i can add more info about it. for example we can take this simple script that i post here before:

function zResell()
	local zp=0.85
	local ii=0
	zitems3={
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0}
	}
	while haSellIterate() do
	ii=ii+1
		local item = haItem()
		zitems3[ii][1]=item.hash
		zitems3[ii][2]=item.buyout
		haSellCancel()
	end
	haSleep(1100)
	while haSendToStash() do end
	while haSendToStash() do end
	haSetGlobalDelay(100)
	local zf = true
	for zrow = 1,10 do
	if zf == false then break end
	for zcol = 1,7 do
	if zf == false then break end
		haStashSelect(zcol, zrow, 1)
		local item = haItem()
		for j=1,10 do
			if item.hash == zitems3[j][1] then
				price = math.floor((zitems3[j][2])*zp)
				zf = haSell (price, price)
				break
			end

		end
	end
	end
end

zResell()

it cancell all auctions and then resell it... now what happens when bot enters this "bug mode" - there are variants
1. the bot stops on 1st haSellCancel() and freze there forever on "auctions" tab.
2. the bot cancell all items good but fully ignore while haSendToStash() do end line (i even write it 2 times in script) - so it cancell all items and not send them to stash and of couse it find nothing then in stash
3. it cancell all ok, it send to shash ok but then it reads wrong tooltips - so it can't recognize items and ignore them
4. all 3 previous is ok but when he click an item and try zf = haSell (price, price) - zf == false don't know why. (i don't speek here about bugged auction house as previous 2 weeks when sometimes we can see "zero error" when trying to sell item)

it's most annoying bug ever. it happens regulary. it happens for all my friends whom i contact. with this script i can surely see that bot enters "bug mode" and take on or off vsync, take on and off fullscreen mode or even restart diablo client. after that manipulations - bot enters normal mode and all working as intended. but the most problem that you only see bugged mode when bod doing such manipulations. we can't see it when bot in "buying items mode" because there is no manipulations at all. i am 100% sure that when bot in bug mode it can't buy items. there are statistically impossible incidences such as bot working in "finding and buying items" mode for 12 hours and don't find even 1 item (it logs every item that it find). then i saw it and restart diablo clinet and bot starting to find 10+ items for hour as always for this script etc... there are tonn of such statistically impossible cases. i am sure i can understand when bot working and don't find items because there are no items and this bugged case. it's very big and annoying problem! i try every day to find that magic video settings that don't enter bug mode and i can't find - i set vsync on and off, i set fps to 20,30,40... i resize window different ways... nothing helps - one day it enters this mode and it's luck if i quickly understand it.

as for statistic - i bot on EU (20 ping), US (150 ping), Asia (500+ ping) - proportions of bug happens 1x(EU)-3x(US)-10x(Asia) - so i think it correlated with ping or delays of interface etc... may be all this info helps ChuiChu to understand the roots of the problem... if there is not enough info about problem - i need to know what info i need to gather?

p.s. if somebody knows that magic combination of video settings - help please! (don't offer full screen mode - it must be only window mode)

a quick fix to this problem: insert a while true do loop after the global delay.

[strohhaar]

where is the banwave? do they need time to ban our mules? thats not normal! what are they waiting?

[ztnko]

blizzard see than ah botting takes more time to be profitable now - so they give us that time...

[strohhaar]

and here is one funny example:

for more than one week i sniped always the same yellow high end item (my script is looking for ~ 30 itemtypes/legendarys). in one week ~ 100 pieces of that type. with always nearly the same great stats for str, int or dex... and always nearly the same price! ( from 5-11 millions each)

and now? nothing! its over.. no items of this type anymore.

is it for us or for ah general?

no matter but thx blizz for the items!!

[Trotz]

bloody beginner question:

i have set the bot to wait between 5 and 30 seconds between searches and to take 25 minute breaks every 2 hours.

How long does an ah bot live on average, and what can be describes as rather safe delays? can i push it and search every 5-8 seconds and expect the bot to still live 2 weeks plus?

[ntn3333]

i can't use hasetlogin...help me plz

[dungle]

I'm newbie and have a question: Is it possible to make a script that will do instant buyout of current selected item in the list when I hit a hotkey?
Example:start the bot, active it, open AH, search for item, select it then hit ALT+1, the script will then do haBuyout() if item has buyout price.

[xblackday]

How do i make the bot stop for random amount of time after MAXSEARCH.

Im using:

local AFTERSLEEPMIN = 1 -- minimum amount of time after searching all the items to wait in minutes (will avoid being kicked with this) set to 0 to disable
local AFTERSLEEPMAX = 3 -- maximum amount of time after searching all the items to wait in minutes (will avoid being kicked with this) set to 0 to disable

But it is not working as intended.

[Trotz]

can nobody give me a hint what kind of delay range i should choose between searches? the account does not have to live forever but 2weeks+ would be nice

[ChuiChu]

i would like to summarize all i know about "Bugged Mode" bug as i named it. When bot enters this mode - it only "simulates" work - 1st time i write about this mode here - http://www.ownedcore.com/forums/diab...ml#post2592241 ([AH Bot] HappyAuction). Now i can add more info about it. for example we can take this simple script that i post here before:

function zResell()
	local zp=0.85
	local ii=0
	zitems3={
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0},
	{0,0}
	}
	while haSellIterate() do
	ii=ii+1
		local item = haItem()
		zitems3[ii][1]=item.hash
		zitems3[ii][2]=item.buyout
		haSellCancel()
	end
	haSleep(1100)
	while haSendToStash() do end
	while haSendToStash() do end
	haSetGlobalDelay(100)
	local zf = true
	for zrow = 1,10 do
	if zf == false then break end
	for zcol = 1,7 do
	if zf == false then break end
		haStashSelect(zcol, zrow, 1)
		local item = haItem()
		for j=1,10 do
			if item.hash == zitems3[j][1] then
				price = math.floor((zitems3[j][2])*zp)
				zf = haSell (price, price)
				break
			end

		end
	end
	end
end

zResell()

it cancell all auctions and then resell it... now what happens when bot enters this "bug mode" - there are variants
1. the bot stops on 1st haSellCancel() and freze there forever on "auctions" tab.
2. the bot cancell all items good but fully ignore while haSendToStash() do end line (i even write it 2 times in script) - so it cancell all items and not send them to stash and of couse it find nothing then in stash
3. it cancell all ok, it send to shash ok but then it reads wrong tooltips - so it can't recognize items and ignore them
4. all 3 previous is ok but when he click an item and try zf = haSell (price, price) - zf == false don't know why. (i don't speek here about bugged auction house as previous 2 weeks when sometimes we can see "zero error" when trying to sell item)

it's most annoying bug ever. it happens regulary. it happens for all my friends whom i contact. with this script i can surely see that bot enters "bug mode" and take on or off vsync, take on and off fullscreen mode or even restart diablo client. after that manipulations - bot enters normal mode and all working as intended. but the most problem that you only see bugged mode when bod doing such manipulations. we can't see it when bot in "buying items mode" because there is no manipulations at all. i am 100% sure that when bot in bug mode it can't buy items. there are statistically impossible incidences such as bot working in "finding and buying items" mode for 12 hours and don't find even 1 item (it logs every item that it find). then i saw it and restart diablo clinet and bot starting to find 10+ items for hour as always for this script etc... there are tonn of such statistically impossible cases. i am sure i can understand when bot working and don't find items because there are no items and this bugged case. it's very big and annoying problem! i try every day to find that magic video settings that don't enter bug mode and i can't find - i set vsync on and off, i set fps to 20,30,40... i resize window different ways... nothing helps - one day it enters this mode and it's luck if i quickly understand it.

as for statistic - i bot on EU (20 ping), US (150 ping), Asia (500+ ping) - proportions of bug happens 1x(EU)-3x(US)-10x(Asia) - so i think it correlated with ping or delays of interface etc... may be all this info helps ChuiChu to understand the roots of the problem... if there is not enough info about problem - i need to know what info i need to gather?

p.s. if somebody knows that magic combination of video settings - help please! (don't offer full screen mode - it must be only window mode)

always use vsync on. ignore my old readme suggestion to use it

for high ping servers see if setting to lower fps like 40 helps for at least your first case. I have several functions that wait only a certain amount of time before giving up which may be less than some high latency.

1. this includes haSellCancel (it shouldnt wait forever though). what does screen look like when this happens? is the item still there? note this also returns status. its probably failing in your case. if so you can use that to break out of loop.
2. see if adding a small delay before this helps. if so then it will immediately tell me what the problem is.
3. do you mean the stash items? the stash items have been tricky for me, somehow different from rest of AH. still looking into ways to improve it. does this only happen after cancel/sendstash?
4. it may be related to #3 not reading an item.

[ChuiChu]

bloody beginner question:

i have set the bot to wait between 5 and 30 seconds between searches and to take 25 minute breaks every 2 hours.

How long does an ah bot live on average, and what can be describes as rather safe delays? can i push it and search every 5-8 seconds and expect the bot to still live 2 weeks plus?

i dont know the bnet detection rules but i would suggest something that follows a human like schedule. with short delay (0 to 50ms globaly delay) session bursts with some lunch/dinner/sleep length delay (haSleep in hours) at those particular times.

this is just a suggestion out of my ass though. but ive yet to be banned for simple using the bot or even hitting several input limits... so im quite sure its related to extended use and frequency.

I'm newbie and have a question: Is it possible to make a script that will do instant buyout of current selected item in the list when I hit a hotkey?
Example:start the bot, active it, open AH, search for item, select it then hit ALT+1, the script will then do haBuyout() if item has buyout price.

hotkeys for specific functions/scripts are not supported (yet). just the one hotkey for running the main bot. closest thing u can do now isuse haAlert() to create popup and hit "ok" button for the last case of your script.

i can't use hasetlogin...help me plz

whats the problem?

How do i make the bot stop for random amount of time after MAXSEARCH.

Im using:



But it is not working as intended.

haSleep is in milliseconds, not minutes. the following will random delay between 1 and 3 ms. note that the randomness is not linear and will tend to choose the lower more than the higher.
haSleep(1*60*1000, 3*60*1000)

[ChuiChu]

k updated after long break.... mostly fixes. when work winds down ill get back to features

some fixes are still pending until i can reproduce (and therefore fix)

[ztnko]

can't understand how to work with haItem().heading. this example of code:

haConsole()
haListIterate()
item=haItem()
print(item.type)
print(item.heading)
print(item.rarity)

gives me this:

[ztnko]

1. this includes haSellCancel (it shouldnt wait forever though). what does screen look like when this happens? is the item still there? note this also returns status. its probably failing in your case. if so you can use that to break out of loop.

screen look like switching to 'auctions' tab and freeze there on cancelling 1st item. item is still there - it doesn't cancell even 1 item. yes now i understand that this freeze screen don't longs forever because i never see it when i swith to bot after some time. but it lasts long enough - minimum several minutes - when i start bot with this resell script and see that script stops on cancelling items i stop it manually and need to take some manipulation with restarting diablo client or with video settings to get it to work. if i simply restart script - it also fails. As i say - once bot enters this "bugged mode" only manipulations with wideo settings can help... so if i insert status check in this script to break out of loop - it only reduse freeze time i think but not solve any problem.

2. see if adding a small delay before this helps. if so then it will immediately tell me what the problem is.

before what? as you can see there already big delay and double sendtostash rows:
haSleep(1100)
while haSendToStash() do end
while haSendToStash() do end

may be you mean smth like this while haSendToStash() do haSleep(100) end but it can't help because it affects only 2nd item and all other. it doen't affect 1st item. but haSleep(1100) affects particular 1st item and it's already here. this small delay in cycle can help if it sent to stash 1st item and then ignore all other. but it's ignore ALL items. there was no case that is sent 1st item and ignore others. it ignores all items or sent all.

3. do you mean the stash items? the stash items have been tricky for me, somehow different from rest of AH. still looking into ways to improve it. does this only happen after cancel/sendstash?

yes i say about stash. no it's not only after cancel/sendstash. when my main script starts - it's trying to sell items in stash and if bot in "bugged mode" cursor simpy pass over this item because i think it haItem() reads wrong stats or doesn't read at all. I don't test what exact return haItem() in that situation.

4. it may be related to #3 not reading an item.

reading is already complete on this stage - if reaing is wrong then it's n.3 case and it's simpy pass over item not trying to sell it. case.4 is when it try to sell it but return error status. you can see in this script that zf== false only if trying to sell item.

[ChuiChu]

oops... i accidentally undo the final line for heading before i zip everything up. those that downloaded v36 and care about haItem().heading dl again (same version, updated zip)

heading is only important if haItem().type doesnt work for you. which would be certain locales that dont follow the format <rarity><space><type>.

ill review your last reply tomorrow ztnko... zzz now