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

Stuck in town; having to restart DB

D

DaBraddah

New Member
Joined
Sep 25, 2015
Messages
24
Reaction score
0
I have realized that my DB would get stuck in town after running Nephalim Rifts.
Only solution I have had so far is to restart DB (Stop, Start). This would resolve it, but I'm not always able to be next to my PC.

Any solutions?

Also, my Log file is 8MB, and this forum won't let me upload it.
 
zip and/or split your log file or grab a shorter one for us
 
update Trinity and let me know plz
 
Really? It says that it is when I log into it. It doesn't give me a prompt to update it O.o and I just downloaded it this morning from this site.

Let me look in forums for a step by step way to update it, maybe.
 
Oh nevermind. Now I feel like an asshole. I looked through log and see that it is at 35 and latest is 59. Not sure why 59 isn't in the exe installation. Will update it now along with the latest installation package

^_^ I hope this fixes it. thanks!

Edit: Wow I love what you did with the Trinity plugin . excellent work!
 
Last edited:
View attachment 8644 2015-10-14 22.19.zipThe log is 48 MB....


I woke up to this

06:10:41.139 DEBUG Logger [Trinity 2.13.59] Using Legendary Potion
06:10:41.140 DEBUG TrinityDebug [Trinity 2.13.59] Unable to find skill for power DrinkHealthPotion
06:10:42.688 DEBUG TrinityDebug [Trinity 2.13.59] Kite movement failed, cancelling for 1500ms
06:10:42.721 DEBUG TrinityDebug [Trinity 2.13.59] Kite movement cancelled for -1467ms
06:10:43.887 DEBUG TrinityDebug [Trinity 2.13.59] Kite movement cancelled for -301ms
06:10:43.929 DEBUG TrinityDebug [Trinity 2.13.59] Kite movement cancelled for -259ms
06:10:45.559 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=57 IsBossOrEliteRareUnique
06:10:49.391 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 144315 // Ghoul_E (Unit) Adding ShouldIgnore=False nearbyCount=1 radiusDistance=26 hotspot=False elitesInRange=True hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False CloseRange
06:10:49.683 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=57 IsBossOrEliteRareUnique
06:10:50.472 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 144315 // Ghoul_E (Unit) Adding ShouldIgnore=False nearbyCount=1 radiusDistance=26 hotspot=False elitesInRange=True hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False CloseRange
06:10:50.805 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=57 IsBossOrEliteRareUnique
06:10:51.181 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 144315 // Ghoul_E (Unit) Adding ShouldIgnore=False nearbyCount=1 radiusDistance=26 hotspot=False elitesInRange=True hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False CloseRange
06:10:51.227 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=57 IsBossOrEliteRareUnique
06:10:53.190 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=66 IsBossOrEliteRareUnique
06:10:53.215 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=25 IsBossOrEliteRareUnique LowHPElite
06:10:58.388 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 144315 // Ghoul_E (Unit) Adding ShouldIgnore=False nearbyCount=1 radiusDistance=23 hotspot=False elitesInRange=True hitPointsPc=1.0 summoner=False quest=False minimap=False bounty=False CloseRange
06:10:58.680 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=25 IsBossOrEliteRareUnique LowHPElite
06:10:59.804 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=25 CloseRange
06:11:00.370 DEBUG TrinityDebug [Trinity 2.13.59] Target changed to 106714 // TerrorDemon_A (Unit) Adding shouldIgnore=False hitPointsPct=25 IsBossOrEliteRareUnique LowHPElite
06:11:08.824 ERROR Logger [Trinity 2.13.59] Player is dead
06:11:08.866 DEBUG InactivityDetector [GameEvents.OnPlayerDied] Resetting inactivity detector
06:11:08.867 INFO Logger [QuestTools][BotEvents] Player died! Position=<624.997, 632.4905, 10.1> QuestId=312429 StepId=2 WorldId=288685
 
Last edited:
make a new installation from scratch including Trinity and Adventurer plz
 
I did, but will need to make another WD to test it. I'll stick with my monk for now. It seems to be working flawlessly, with the occasional "stuck".

Thank you again. It is amazing how you can tend to our issues so promptly. This program is getting better and better every update.
 
One great update would be something to react specifically off of the Proc (near death experience, etc), forcing the bot to escape to a safe area (or entrance) and wait in town until cooldown for proc is over.
 
thats something Trinity should handle
 
report it under Trinity's section plz
 
You must log in or register to reply here.
Back
Top