heisenburger

Can confirm the bot doesn't always crash in a master's area, but crashes happen probably 80% of the times. Simply start a daily mission with haku or vegan and enter master's area to reproduce the bug. (In Talisman's league. Not sure if that matters)

Just saw the crash too. Tested with default configs. Maybe it doesn't crash in every master's instance, but crashes do happen. What I did to reproduce the bug: enter a master's area in a map. start bot. crash.

You look like a noob when you paid $20 for 6 months when you could've paid $10 more for lifetime, but this makes sense if your plan is to stop botting after 6 months and save $10 over half a year. Your big posts are basically saying one thing: the bot gets stuck in act4 town. So just stay out of act4 and enjoy botting.

You look like a noob when you paid $20 for 6 months when you could've paid $10 more for lifetime, but this makes sense if your plan is to stop botting after 6 months and save $10 over half a year. Your big posts are basically saying one thing: the bot has trouble in act4 town. So just stay out of act4 and enjoy botting.

Yeah this bug happens only sometimes and I don't know if Alk can fix it without knowing how to reproduce it. A hacky solution like town-chicken can be a temporary fix.

Happened just once today. The bot was trying to take a map out of stash, and it kept clicking on an empty square in stash tab 2, but the map was in stash tab 1. I restarted the bot. No dice. So I logged out/in and the problem went away. This never happens in town, but I've seen it happen in hideout many times.

Occasionally the bot still gets stuck in hideout (still no idea how to reproduce the bug), and restarting the bot doesn't fix things, but logging out almost always solves the problem. So does it make sense to simply log out after the bot has spent more than X seconds in towns/hideout? This can also save people from looping in towns because all of us have to show up in towns after the bot chickens, so we all run the risk of exposing our bots in towns. I think it'd even better to have an additional option to fully stop the bot after it's chickened from towns/hideout too many times .

Much appreciated

Did you download a fresh copy of 0.57d? I have almost no problems with the bot so far, but the bot would break whenever I get lazy and don't make sure the configs are 100% correct. So make sure you do that and report back. But I can confirm it's dangerous to use the bot in Act4 town. It occasionally gets stuck and runs in loops. Restarting the bot solves the issue, so it's most likely a bug in the bot.

It seems the bot always identifies maps before running them. This defeats the 30% bonus on running unidentified maps. Is there a way to turn this off? (haven't been keeping up with all the changes lately...)

Glad to see this has been considered. Only alk knows if this could work: check whether the map is magic only after the augmentation orb is used. If it is magic, break the loop.

An orb of augmentation can easily boost the map to 30%-40% + quantity. It's much cheaper than rerolling with alts. Suggestion: always use an augmentation immediately after using a transmute, and I don't think it's necessary to check whether the augmentation is successfully applied. As long as the map has indeed become a magic map after both orbs are used, everything should be good.

It's a waste, but this feature will increase the values of scours a bit Maybe you should let the bot use exalts on maps too

How come I'm not getting most of these bugs... botting on stand-alone.

That does the job. Amazing speed. Thanks so much!

^ this. I used to waste fragments just like that

Sometimes the bot would go back to the same map 5 times to fight a hard boss. I tried using "always reset instance", but it's for area-farming only. Adding new options next to "set map cleared" would save some time, such as resetting the map after "exit to login because boss_name has been found!!".

Just tested it. The bug doe not exist in 0.56l+. I should stop blindly replying to these posts...

+1

Same here. If you attach spy++ to the client window, you'll see how many messages are actually sent to the client per mouse click. Try to simulate every message and see what happens...

This still doesn't explain how to reproduce the bug.

Looks like "max idle time" still doesn't have the highest chicken priority. The bot should immediately chicken after nothing's killed in 1-2 minutes.

Add this line to pickit to make the bot identify all maps: [Category] == "Map" # [Quality] >= "0"

Works fine on my pc.

ugh... it's only for testing.