Please fix the selling/salvaging bug..
Bot looping on quest "clear den of the fallen". It walks to the entrance to the den but doesn't click on it to enter. TPs to town and repeats. Logs attached.
<MoveToMapMarker questId="312429" stepId="2" exitNameHash="1317387500" destinationWorldId="182976" interactRange="20" />
Are you sure you guys are using the most up to date version of both HB and Trinity? If so, then for some reasonIs working for me and none of you guys, and I don't know why.Code:<MoveToMapMarker questId="312429" stepId="2" exitNameHash="1317387500" destinationWorldId="182976" interactRange="20" />
Please fix the selling/salvaging bug..
I think the issue here is that if you stop the bot, or it has an issue and you have to reset, you have to manually reload the profile.xmlAre you sure you guys are using the most up to date version of both HB and Trinity? If so, then for some reasonIs working for me and none of you guys, and I don't know why.Code:<MoveToMapMarker questId="312429" stepId="2" exitNameHash="1317387500" destinationWorldId="182976" interactRange="20" />
<Name>Act 1 - Loader</Name>
<KillMonsters>True</KillMonsters>
<PickupLoot>true</PickupLoot>
<GameParams quest="101758" step="1" act="OpenWorld" difficulty="Normal" resumeFromSave="False" isPrivate="True" numGames="-1" />
<While condition="Me.IsInTown">
<LoadProfile profile="START.xml" nodelay="true" />
</While>
I think the issue here is that if you stop the bot, or it has an issue and you have to reset, you have to manually reload the profile.xml
What needs to be done is profile.xml needs to be put in the Act1 folder, and just rename it liked START.xml to make it stand out against the others. Then for every profile you need to add in the little code from below. This will make it so no matter which current profile is loaded, it will always create the game, then once in game revert to the main profile. From there it just goes on like normal.
Possibly keep a backup before you change them all. I have never made a script for DB or know much about it at all. I edit them here and there to get them working how I want, and what I posted is just my best assumption of whats going wrong.Yeah, I noticed problems that might be solved by that. Guess I'll go ahead and do that while I'm testing some profiles.
I'm not sure I'm sorry, I didn't think about it at the time. Maybe add a check in the Order section to see if quest still exists, if not return to town. That way if it goes to a place it doesn't belong for whatever reason it will realize it doesn't need to be there and return back to town. This would create a loop if there is a waypoint ID issue, so you would see it going to the same place over and over to narrow down what is actually messed up.@NoWayLol, could be a bad waypoint ID. If you could tell me what profile it said it loaded, that would be great.