What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Trinity 1.7.2.6

Status
Not open for further replies.
I'm having the same issue of this not picking up legendaries. I see exactly how it's happening because I watched it happen. Here is the scenario:

Pack only has 1 open slot - Bot initiates town run
Large number of enemies on screen and near player
Town run has to clear out all nearby enemies to complete
Legendary (or any other item set for pickup) drops from first pack killed
Bot keeps moving to clear out all nearby
Bot finally clears scene and initiates TP far away from original drop
Bot completes town run and takes TP back to location
Bot doesn't rescan entire scene for item loot, doesn't go back to where the town-run was initiated, keeps moving forward

This is how it's happening. I can think of 3 ways to correct this (I program in c#, so I could fix this in code if I had some free time... but if I had that, I wouldn't be botting):

1.) Set in-memory waypoint when town-run is first initiated and return to that spot when TP back to dungeon (best way I can think of)
2.) Greatly increase item loot priority when town-run timer starts (this could still miss items if more than one drops, as the town run initiates when there are two open slots)
3.) Loot-scan while the town-run timer is moving and store locations in memory of drops so they can be picked up on return (Would think this could be a memory problem, but not sure).



What do you guys think?
 
Last edited:
I think I found a problem.. finishing the tower, my bot killed a pack of elites and used teleport to town. He had plenty of places in the inventory, but left the 4 items that drop on the floor. I believe, the command believed he had finished the dungeon and used the tp before catch items on the ground...

Sorry for my english, i tried my best..
 
Alright there is something seriously wrong with this new update. I left it on for an hour, came back and im had 244 deaths per hour....wtf? He just runs through the map and stops attacking, doesnt do anything besides run into packs of mobs and dies....wtf is this? It works fine for the first 15 minutes, and after that it just completely stops using ALL abilities and just runs the map, does nothing but dies.
 
Last edited:
Alright there is something seriously wrong with this new update. I left it on for an hour, came back and im had 244 deaths per hour....wtf? He just runs through the map and stops attacking, doesnt do anything besides run into packs of mobs and dies....wtf is this? It works fine for the first 15 minutes, and after that it just completely stops using ALL abilities and just runs the map, does nothing but dies.

Make a fresh install, and post a log.
 
I don't know about you guys..but my DH got only one plan for a 10hour non stop run today. 2 days ago i did a clean install of Trinity and DB..and it collected plans just fine..got more than 15 plans per day. Actually this was one of the reasons why i reinstalled everything(plans skipping). The check about plan looting is ON .. as always.
My barb did the same 10 hour run today..got more than 10 plans.
 
Random Number Generator. It's statistically possible for you to "play" for a month straight and not get a single plan.
 
I think I found a problem.. finishing the tower, my bot killed a pack of elites and used teleport to town. He had plenty of places in the inventory, but left the 4 items that drop on the floor. I believe, the command believed he had finished the dungeon and used the tp before catch items on the ground...

Sorry for my english, i tried my best..

Change "Wait for Loot Drop" in the Trinity config to 50 instead of zero.
 
i know this is a thread for 1.7.2.6 but i just wanted to give you a thumbs up for your work on tempest rush in 1.7.2.7 (Y) it works much better (small areas/destructables fuck with it but you obviously already know that)
 
How I do that? I am new I am sorry, just downloaded this version and trying to learn before it happens xD
its on the first page of the trinity settings. theres a big slider "Wait for loot drop - Delay after kill:"
 
Random Number Generator. It's statistically possible for you to "play" for a month straight and not get a single plan.
3 days ago ..before the clean install i did ... i saw it with my own eyes how my DH skips plans loot. That's why i reinstalled everything. Worked for a couple of days..now happens again(have't seen plan loot not picking..but obviously it does). Happens only with my DH so far. Barb pickup plans fine. Not a big deal..plans are cheap..but some legendary plans cost a fortune. Would be nice if rrrix could take a quick look.
 
Seems like the fresh install did the trick, everything working great! thanks
 
For some reason, my monks dont use sweeping wind.. Anyone else has this problem? I dont use innas set btw..
 
wth is this:

[14:37:38.913 N] [Trinity]Exception 1: Root element is missing.
[14:37:46.297 N] ####################################
[14:37:46.317 N] #### WP to Fields of Slaughter ####
[14:37:46.407 N] ####################################
[14:37:49.192 N] [Trinity]Exception 0: There is an error in XML document (0, 0).
[14:37:49.192 N] [Trinity]Exception 1: Root element is missing.

Bot and profile is running fine, but this keeps popping figuring in log

Full log: View attachment XML.zip
 
Last edited:
any news for ww barb?

something is wrong with barb now

he is using whirlwind when is running to pile of gold and nothing is in melee

also spamming random whirlwind for destroy items or while moving for no reason when no one is in melee.. or using it for a single gray mob he cant waste rage on this build or he cant sprint anymore

and when he meet elites he start whirwind random even if they are out of screen wasting all the rage

my settings:

trigger range no elite 0
cluster 0 (also tested to max what this setting does?)
minimum trash mob 5
fury dump always disabled
skip destructible
destructible attack range 1

also updated act 3 rixx and still have problems like walking in city and doing nothing after a disconnect
 
wth is this:

[14:37:38.913 N] [Trinity]Exception 1: Root element is missing.
[14:37:46.297 N] ####################################
[14:37:46.317 N] #### WP to Fields of Slaughter ####
[14:37:46.407 N] ####################################
[14:37:49.192 N] [Trinity]Exception 0: There is an error in XML document (0, 0).
[14:37:49.192 N] [Trinity]Exception 1: Root element is missing.

Bot and profile is running fine, but this keeps popping figuring in log

Full log: View attachment 83452

Delete Trinity Logs folder for that bot. Worked for me. It will re-create it, FYI
 
Delete Trinity Logs folder for that bot. Worked for me. It will re-create it, FYI

buce15 is correct.

Also, I believe I fixed what was causing this bug in the next version.
 
Status
Not open for further replies.
Back
Top