Thx Chui! You Are the Best!!!!
Thx Chui! You Are the Best!!!!
k beta 43 posted...
whats the uber hacker stuff? i dont follow diablo news much other than patch notes :P
Hi Chuichu,
Initial testing for me shows that the bot bought an item that is not specified in my script.
Same results as the previous beta version:
1. haListIterate() doesnt work correctly. It Iterates random instead as I set.
2. Snipe items with wrong stats which are not added to my script.
3. Can't start from the menu.
Thank you Chui for your great work!
Last edited by Fgura; 07-28-2013 at 01:25 PM.
1. random in what way? also note that haListIterate is now a lua function... it wraps around the new manual control api (see Core/Old.lua).
2. let me know a specific item+stats so i know if its stat specific or general. ill setup a script now to hunt for certain stat items to test this.
- some sample script code would help greatly here too
3 you mean from the main lobby screen?
4. ill give this some more testing... i thought bliz changed it so you just cant query as often eliminating input limits.
reason for rework is to fix a bunch of issues, performance, stability, and make future features+updates much simpler. i do expect a few kinks however since its nearly all new code
edit: one more question... which language is this? i havent tested outside en much. thats probably the reason
Last edited by ChuiChu; 07-14-2013 at 04:15 AM.
-reloging doesn't work, it just relogs and script is not restarted (old version did this too if i tried to force starting the script over instead of continuing)
-it is not faster imo, only filling/switching of filters is faster , otherwise the old bot is faster for me (more searches per given period of time with the same script)
-it is returning nil instead of 0 if the value on item is not found? i have some of my scripts constructed around 0 if item has no stat i am searching for, now i get error that i do some operations with nil values, i was not used to get that error and my scripts worked, now they are not working ...
-buying of wrong items was there before, now it does it more often, if you touch/move the window it sometimes misses some filters... it is more buggy than before due to faster fliters (probably), old bot did this too + it did it sometimes after reloging (just missed 1 filter after reloging from time to time), i have this solved in my scripts so it can never buy the wrong item, but it slows my buying down by checking the stats on items before buying them
- i want to know how u guys get the input limits now. i tried to just loop on search and list iterate but it just slows down eventually, but doesnt input limit out. my only way to test this now is to force a disconnect error instead (very similar to input limit condition)
- whats the specific case script style... a set filters + buyout loop? like SnipeBuyout? i plan to do performance comparison tests next between this version and old one.
- if you mean with haFilterStat() it will only return nil if the last item operation failed. i can change it to the original however
- touching the window WILL mess it up and theres noway around it. im planning on simply halting the bot if any user input is detected... but if thats not the only case for it getting wrong items let me know if its something consistent or random. as long as the filters are set correctly it should have no affect on the rest of the bots operation.
as always plz send/pm scripts (or specific sections) that are misbehaving its the best way for me to reproduce![]()
Trying to start the bot i get derp error
LUA Fail:
Lua/Main.lua.2: attempt to call global 'HaSetGlobalDelay' (a nil value)
I tried with
haSetGlobalDelay()
haSetGlobalDelay(0)
haSetGlobalDelay(n) n - any number, same result, bot wont start
HA43b Bugreport:
If i run diablo 3 client, then run HA then hit Ctrl-F12 (the one i use to start) the client will not log me in, i need to log in manually at least once to start the bot, previous version was able to log me in stright on, and i believe it is the way we all wish you will make at release..
Something tell me this is something me and you have already discussed, something about memory not loaded at begin, but i really hope you find a more cool solution, like a first log in and log out...
Still digging other stuffs.....
Chui Chui to get input limit reached do this:
while true
hasearch()
haListSelect(1)
end
It should get you disconected after 20 searches. Also global delay = 0
make sure lowercase h
hmm i wonder what the difference for me is. i simply get "no items found" and a longer delay and never input limit
also when this happens does it just get stuck at the error message... or does it get to the login screen? if so do you see an error message? i just got that to happen with a forced disconnect (similar to input limit condition)
its meant to start from login or from lobby now. does it not work at all from login screen or does it only go a certain way?
Last edited by ChuiChu; 07-14-2013 at 03:59 PM.