you have to describe what exactly happened. but it sounds like the movetoactor/movetomapmarker bug where it goes to the objective but does not interact and thats a questtools bug. that quest worked for me every time.Great profile!
But, I have seen that the bot gets stuck on the "The True Son of the Wolf" Bounty, it dont want to stalk to the Knight. (to trigger the mobs you are suppose to kill)
there is no forcetownrun because its a waste of time if thats what you asked. otherwise townbehavior is not profile related.why does it not put gems,mats,legendaries in stash? it just keeps them in inventory
well i cant comment on that if you just say alot. most stucks are created by trinity/questtools. there are some which are profile related but i wasnt able to fix them yet because of their rarity. also i cannot watch my bot 24/7 and im not running this profile 24/7.i ran this profile for ~2 days, worked well. There are definite a lot of stuck positions. I've notice it leaving game many times. I got a few dozen helltrappers. Nothing perfect, but i can live with it. For what its worth, this profile works, its not the fastest, bit i still averaged 2.5 billion exp a hour or more when its not stuck. I get maybe 1-2 deaths a day. no gearswap or anything like that either.
Thank you for your hard work! fyi nozerg v15 that you have posted does mathiel. I've seen my bot kill mathiel quite a few times
you have to describe what exactly happened. but it sounds like the movetoactor/movetomapmarker bug where it goes to the objective but does not interact and thats a questtools bug. that quest worked for me every time.
you download gsr, enable it and set it up as you like. i dont know how to answer your question.how can v17zerg work with gearswap reload?
Did some tidying up (mostly TrinityExploreDungeon -> ExploreDungeon and some changes to path precision/box size etc.) If anyone can tell the difference from the old files I can clean up the files for the zerg users as well. I feel the exploring is working better in some places at least, but it's too early to say for sure.
Could you add versionning to your zip file, for archiving purposes please![]()
exploredungeon values are mostly untouched so you can probably get a few % speed out of those. TrinityExploreDungeon -> ExploreDungeon is just cosmetic though. i dont think anyone cares about thatDid some tidying up (mostly TrinityExploreDungeon -> ExploreDungeon and some changes to path precision/box size etc.) If anyone can tell the difference from the old files I can clean up the files for the zerg users as well. I feel the exploring is working better in some places at least, but it's too early to say for sure.
exploredungeon values are mostly untouched so you can probably get a few % speed out of those. TrinityExploreDungeon -> ExploreDungeon is just cosmetic though. i dont think anyone cares about that![]()
It had to be done!
But yeah, I found the values from one of the rift bots. I tried to the best of my knowledge to match the map layouts and I believe I got it right. The rift bot is working quite well so I figured why not use those values.
there is still <ToggleTargeting questId="368607" combat="False" looting="True" lootRadius="100" killRadius="50" /> in westmatchfire.xml in the semi zerg version. that was a small cosmetic error in v16 and you probably just replaced the qid=1 lines.mrbubbel, this is for you if you want to include the changes made to the ExploreDungeon values.
Give them a spin just to check that there are no parse errors.
there is still <ToggleTargeting questId="368607" combat="False" looting="True" lootRadius="100" killRadius="50" /> in westmatchfire.xml in the semi zerg version. that was a small cosmetic error in v16 and you probably just replaced the qid=1 lines.