Search results

I've only had this issue once or twice and it was always corrected by the profile restarting once it hit inactivity timer. However I remember this also happening occasionally in Da oasis before I switched over from exploredungeon tag to moveto tags for pathing. Tonight after I get homework done...

v2.1 - The bug with running to the gate in townruns in a1 has been narrowed down to the bot thinknig the blacksmith is near the gate when trying to salvage, townruns will still be called at the start of act1 profile but if the bot is in act1 it will port to act2 then do townrun then start act1...

Thanks for the quick response man, I have narrowed this issue down now and it appears to be an issue with salvaging. If you have any items that need to be salvaged when the townrun is called in act 1 it will run to the gate searching for the blacksmith to salvage the items. I will submit a bug...

The fix is up, v2.0 just released.

Tweak your combat settings in Trinity.

Version 2.0 is now up with these changes: v2.0 - Bug fix for a1 townrun, this issue did not seem to be caused by the profile itself but by adding a forcetownrun to the start of a1 this problem should occur far less often if at all. - Rewrote pathing for a2 so if it spawns at 1 of the 9...

Good to hear =). Running my newest version over night and seeing how it goes. It seems to work great so far, much smoother than my current version.

Also, new version will have a forcetownrun tag at the start of act 1 profile to avoid the stuck on the gate. New version is all done and just being tested right now. I will also be uploading a version designed to run just 1 zone over and over to farm a specific key.

Replace your "Last" profile with that one, make sure to remove the old one from the folder. Restart DB and load that profile.

Just trying to get my current profiles working flawlessly, mainly just this one since the others work fine and then starting my work on bounties.

Yep, just open the profile called "Last" and edit the load profile line to just load Da.Oasis rather than fields.

Update: I am almost done writing the profile that uses moveto tags for Da. Oasis, this will hopefully help to prevent backtracking. I will have 4 different routes for this zone based on the 9 locations the waypoints spawn. I will also include a method for it to use exploredungeon tag in the...

If you want it to skip certain acts lets say Da. Oasis for example, you would open the To_Oasis profile in notepad, towards the end there should be this line <LoadProfile profile="Da_Oasis.xml" /> . You would change the profile name, in this case, Da_Oasis.xml to whatever profile you want...

I have found 7 waypoints that spawn in act 2 Da. Oasis, I will be writing pathing for arriving at any 7 of them to avoid having to use the exploredungeon tag, this should decrease backtracking and chance of timing out due to inactivity. Currently I have pathing done for 2/7 of the waypoints...

I will also be updating pathing in act 2 to use moveto tags and not exploredungeon tag as that seems to cause a lot of backtracking in big areas in it current state.

I will be adding a forcetownrun at the start of the act 1 profile in my next release so that the bot will have an empty inventory before actually starting the run, that way it should never need to tow run during the act 1 profile unless you have it set to loot everything. Other than that there's...

Please upload logs if you find bugs, also the Act 1 townrun bug is a DB problem not an issue with the profile. Townruns work fine in every other act just not act 1 for some reason.

Honestly man I have botted CoTA, Core of Arreat, Sarkoth runs back in the day and never been banned once, IMO its all just luck of the draw,err bad luck I suppose in this case, that gets you banned. I bot 24/7 and always have and I have been botting since DB release. Personally I have been...

That is an error with death handling in DB or Trinity it is not intended.

Not sure what that error is from but that might be the issue.