Logging out After Death

boat_58 · Jun 29, 2014

can anyone show me how to change it so that the bot doesn't log out each time after dying? every time it dies, it logs out and relog back in restarting the rift or the bounty all over again.

Thanks

Tony · Jun 29, 2014

check under Trinity settings about death handling value

boat_58 · Jun 29, 2014

where would that be under? i have been scanning in Trinity settings but haven't found Death Handling yet

oktogo · Jun 29, 2014

boat_58 said:
where would that be under? i have been scanning in Trinity settings but haven't found Death Handling yet

I'm not sure about a Trinity setting.... but if you go to the main DB window --> Settings --> Bot --> Misc --> Death Handling --> (Set this to ignore)

Hope that helps.

boat_58 · Jun 29, 2014

oktogo said:
I'm not sure about a Trinity setting.... but if you go to the main DB window --> Settings --> Bot --> Misc --> Death Handling --> (Set this to ignore)

Hope that helps.

ya that has always been on ignore, but it keeps logging off after each death

Jayster · Jun 29, 2014

Hey buddy I could provide more info if you'd post your log, or some SS's of it happening, it could be the profile... doing it

boat_58 · Jun 29, 2014

it won't let me attache all the log to this, maybe because it is really big but i don't know. .i have copy and pasted the last of the log on here so you can see. the bot just did a rift and died once and then initiated the log out sequence.. hopefully this is enough to help..

THanks

Code:

15:41:55.703 DEBUG DefaultNavigationProvider Client path generated.
15:41:55.704 DEBUG DefaultNavigationProvider Generated path to <865.3141, 822.9407, 0.02894888> () with 5 hops.
15:41:56.587 DEBUG DefaultNavigationProvider Generating path to  - <880.0074, 821.8705, 0.02584447>
15:41:56.599 DEBUG DefaultNavigationProvider Successfully generated path from {X=142,Y=60} to {X=137,Y=160} in 00:00:00.0043902 with 102(4) hops
15:41:56.615 DEBUG DefaultNavigationProvider Client path generated.
15:41:56.616 DEBUG DefaultNavigationProvider Generated path to <880.0074, 821.8705, 0.02584447> () with 4 hops.
15:41:57.977 DEBUG DefaultNavigationProvider Generating path to  - <891.1981, 821.381, 0.02329614>
15:41:57.985 DEBUG DefaultNavigationProvider Successfully generated path from {X=142,Y=65} to {X=138,Y=163} in 00:00:00.0050623 with 99(9) hops
15:41:57.993 DEBUG DefaultNavigationProvider Client path generated.
15:41:57.994 DEBUG DefaultNavigationProvider Generated path to <891.1981, 821.381, 0.02329614> () with 9 hops.
15:41:59.678 DEBUG DefaultNavigationProvider Generating path to  - <902.5779, 820.3361, 0.02051089>
15:41:59.752 DEBUG DefaultNavigationProvider Successfully generated path from {X=141,Y=69} to {X=139,Y=169} in 00:00:00.0044790 with 102(3) hops
15:41:59.765 DEBUG DefaultNavigationProvider Client path generated.
15:41:59.766 DEBUG DefaultNavigationProvider Generated path to <902.5779, 820.3361, 0.02051089> () with 3 hops.
15:42:00.334 DEBUG DefaultNavigationProvider Generating path to  - <916.9027, 819.7111, 0.01671406>
15:42:00.342 DEBUG DefaultNavigationProvider Successfully generated path from {X=141,Y=75} to {X=137,Y=175} in 00:00:00.0050224 with 102(4) hops
15:42:00.356 DEBUG DefaultNavigationProvider Client path generated.
15:42:00.356 DEBUG DefaultNavigationProvider Generated path to <916.9027, 819.7111, 0.01671406> () with 4 hops.
15:42:00.957 DEBUG DefaultNavigationProvider Generating path to  - <931.6317, 819.0077, 0.01241139>
15:42:00.965 DEBUG DefaultNavigationProvider Successfully generated path from {X=141,Y=81} to {X=137,Y=180} in 00:00:00.0042684 with 100(3) hops
15:42:00.975 DEBUG DefaultNavigationProvider Client path generated.
15:42:00.976 DEBUG DefaultNavigationProvider Generated path to <931.6317, 819.0077, 0.01241139> () with 3 hops.
15:42:01.526 DEBUG DefaultNavigationProvider Generating path to  - <946.3547, 818.2328, 0.007640743>
15:42:01.538 DEBUG DefaultNavigationProvider Successfully generated path from {X=141,Y=87} to {X=135,Y=187} in 00:00:00.0086618 with 107(5) hops
15:42:01.562 DEBUG DefaultNavigationProvider Client path generated.
15:42:01.563 DEBUG DefaultNavigationProvider Generated path to <946.3547, 818.2328, 0.007640743> () with 5 hops.
15:42:02.126 DEBUG DefaultNavigationProvider Generating path to  - <961.0699, 817.3737, 0.002321574>
15:42:02.132 DEBUG DefaultNavigationProvider Successfully generated path from {X=141,Y=93} to {X=135,Y=191} in 00:00:00.0026430 with 100(4) hops
15:42:02.141 DEBUG DefaultNavigationProvider Client path generated.
15:42:02.141 DEBUG DefaultNavigationProvider Generated path to <961.0699, 817.3737, 0.002321574> () with 4 hops.
15:42:02.701 DEBUG DefaultNavigationProvider Generating path to  - <967, 817, 0>
15:42:02.709 DEBUG DefaultNavigationProvider Successfully generated path from {X=141,Y=98} to {X=135,Y=191} in 00:00:00.0054776 with 95(9) hops
15:42:02.719 DEBUG DefaultNavigationProvider Client path generated.
15:42:02.719 DEBUG DefaultNavigationProvider Generated path to <967, 817, 0> () with 9 hops.
15:42:03.380 DEBUG DefaultNavigationProvider Navigator.Clear
15:42:03.381 DEBUG DefaultNavigationProvider Generating path to Name=LacuniFemale_A Dist=29 IsElite=False LoS=True HP=1.00 Dir=NE - <719.0933, 878.8016, 0.1>
15:42:03.455 DEBUG DefaultNavigationProvider Successfully generated path from {X=146,Y=103} to {X=160,Y=96} in 00:00:00.0012898 with 17(5) hops
15:42:03.471 DEBUG DefaultNavigationProvider Client path generated.
15:42:03.473 DEBUG DefaultNavigationProvider Generated path to <719.0933, 878.8016, 0.1> (Name=LacuniFemale_A Dist=29 IsElite=False LoS=True HP=1.00 Dir=NE) with 5 hops.
15:42:05.885 DEBUG Logger [Trinity] Using Legendary Potion
15:42:07.189 DEBUG DefaultNavigationProvider Navigator.Clear
15:42:07.426 DEBUG DefaultNavigationProvider Generating path to Name=SafePoint Dist=29 IsElite=False LoS=False HP=0.00 Dir=SE - <760, 865, 0>
15:42:07.430 DEBUG DefaultNavigationProvider Successfully generated path from {X=146,Y=102} to {X=154,Y=112} in 00:00:00.0008844 with 15(5) hops
15:42:07.463 DEBUG DefaultNavigationProvider Client path generated.
15:42:07.464 DEBUG DefaultNavigationProvider Generated path to <760, 865, 0> (Name=SafePoint Dist=29 IsElite=False LoS=False HP=0.00 Dir=SE) with 5 hops.
15:42:07.869 INFO  Logger [Trinity] Attempting to avoid death!
15:42:09.307 DEBUG DefaultNavigationProvider Navigator.Clear
15:42:09.307 DEBUG DefaultNavigationProvider Generating path to Name=HealthGlobe Dist=77 IsElite=False LoS=True HP=-1.00 Dir=NW - <712.6793, 792.5048, 0.5146652>
15:42:09.396 DEBUG DefaultNavigationProvider Successfully generated path from {X=250,Y=111} to {X=221,Y=93} in 00:00:00.0021688 with 31(8) hops
15:42:09.424 DEBUG DefaultNavigationProvider Client path generated.
15:42:09.425 DEBUG DefaultNavigationProvider Generated path to <712.6793, 792.5048, 0.5146652> (Name=HealthGlobe Dist=77 IsElite=False LoS=True HP=-1.00 Dir=NW) with 8 hops.
15:42:14.155 DEBUG DefaultNavigationProvider Navigator.Clear
15:42:14.461 DEBUG DefaultNavigationProvider Generating path to Name=SafePoint Dist=13 IsElite=False LoS=False HP=0.00 Dir=SW - <767.5, 847.5, 0>
15:42:14.466 DEBUG DefaultNavigationProvider Successfully generated path from {X=247,Y=111} to {X=243,Y=115} in 00:00:00.0009560 with 7(4) hops
15:42:14.493 DEBUG DefaultNavigationProvider Client path generated.
15:42:14.494 DEBUG DefaultNavigationProvider Generated path to <767.5, 847.5, 0> (Name=SafePoint Dist=13 IsElite=False LoS=False HP=0.00 Dir=SW) with 4 hops.
15:42:18.374 DEBUG DefaultNavigationProvider Navigator.Clear
15:42:18.688 DEBUG DefaultNavigationProvider Generating path to Name=SafePoint Dist=24 IsElite=False LoS=False HP=0.00 Dir=NW - <750, 827.5, 0>
15:42:18.692 DEBUG DefaultNavigationProvider Successfully generated path from {X=243,Y=114} to {X=235,Y=108} in 00:00:00.0007314 with 9(3) hops
15:42:18.716 DEBUG DefaultNavigationProvider Client path generated.
15:42:18.717 DEBUG DefaultNavigationProvider Generated path to <750, 827.5, 0> (Name=SafePoint Dist=24 IsElite=False LoS=False HP=0.00 Dir=NW) with 3 hops.
15:42:25.242 INFO  Logger [BotEvents] Player died! Position=<765.1787, 848.1369, 0.1000001> QuestId=312429 StepId=2 WorldId=288685
15:42:25.243 INFO  Logger [BotEvents] You have died too many times. Now restarting the game.
15:42:25.610 INFO  ProfileManager Loaded profile Rift Bot Optimized Explore
15:42:31.770 DEBUG MainWindow Start/Stop Button Clicked!
15:42:31.776 INFO  BotMain Stopping the bot.
15:42:31.784 INFO  BotMain Session lasted for: 00:04:34.5493504
15:42:31.785 DEBUG BotMain CurrentBot.Stop()
15:42:33.342 DEBUG BotMain Navigator.Clear()
15:42:33.345 DEBUG DefaultNavigationProvider Navigator.Clear
15:42:33.348 DEBUG BotMain TreeHooks.Instance.ClearAll()
15:42:33.349 INFO  RoutineManager Chose Trinity as your combat routine
15:42:33.351 DEBUG TreeHooks Replaced hook [RoutineCombat] 4e93c282-dd60-4152-8770-a2b87121a096
15:42:33.353 DEBUG BotMain OnStop event
15:42:33.354 DEBUG BotMain OnStop Event Invoking
15:42:33.397 DEBUG ProfileOrderManager ProfileOrderManager.OnBotStop. Resetting caches.
15:42:33.400 DEBUG ProfileOrderManager Resetting current behavior.
15:42:37.686 INFO  BrainBehavior Clicked revive at corpse button
15:42:37.687 INFO  BotMain Bot Thread Ended. Was this requested?

MUFFDIVER · Jun 29, 2014

[Trinity] You have died too many times. Now restarting the game.

[Trinity]You have died too many times. Now restarting the game.

Hey guys.

I had this issue as well... and man... what a run around trying to get a straight answer out of someone. I read through tons of posts on the issue... some new, some old... ALL unsolved. Either ignored all together, hadn't been followed up with, or the thread just died.

It was frustrating for me just seeing all these people getting 'generically' handled by people who didn't seem to give a $%^& ...enough to actually follow through with or follow up on with any reasonable customer service.

Anyway... I'm sorry you haven't been able to find a solution to your problem or haven't had one provided for you.

I do... have a couple 'options' that can probably help alleviate a little frustration. They may not be solutions that I would expect from a support professional and one of them (in most cases) I wouldn't particularly endorse myself but... it's something.

So here is the first one...

Work Around #1:

<TrinityMaxDeaths questId="1" max="25" />
Add the blue line that's above into the profile\xml file that your issue is occurring on.

An example is provided below:

Code:

<Profile>
  <Name>Just an Example</Name>
  <KillMonsters>Obviously</KillMonsters>
  <PickupLoot>Obviously</PickupLoot>
  <GameParams quest="1" step="-1" act="OpenWorld" resumeFromSave="False" isPrivate="True" numGames="-1" />

  <Order>
	<ToggleTargeting questId="1" stepId="1" combat="True" looting="True" lootRadius="150" killRadius="80" />
[COLOR="#000080"]          <TrinityMaxDeaths questId="1" max="50" />[/COLOR]

                .........more example code...... more code....
          .........more code...... more code....
                .........more example code...... more code....

  </Order>
</Profile>

I seen people recommending looking for and removing the <TrinityMaxDeaths questId="1" max="1" /> from any profiles they used... but most people could not find the entry at all. So with a little reverse psychology... I figured why not ADD the line, increase the number, and see if it overrides the DemonBuddy feature... and it did.

Work Around #2:

A more aggressive approach but again... all the same... it stops the problem and doesn't seem to create any new ones in the process.

You can modify, move, or delete... I normally wouldn't recommend this... but it works.

..DemonBuddy\Plugins\QuestTools\ProfileTags\MaxDeaths.cs
..DemonBuddy\Plugins\QuestTools\Helpers\Death.cs

Please... backup any files before editing or deleting!

I personally just zipped up 'MaxDeaths.cs', left the zipped file in the same folder as the original and then deleted MaxDeaths.cs.

Yes, maybe a unorthodox approach but... it's not my job to fix it and well I just had enough of dealing with it

If someone wants to provide a better\technical solution or an actual proper fix... I'm sure you'd be popular

All the best and take care!

boat_58 · Jun 30, 2014

thank you, i will give that a try when i get home.. thanks for your reply, i know what you mean, i am sure someone out there knows how to fix it but no one cares to help. i mean we pay for the product, the least they can do is take a look for the us.

tomer132246 · Jun 30, 2014

same problem here, you should really adress it.

spaceitout · Jun 30, 2014

Death Handling General Setup & Information

Good Post Muff !

Trinity Info ,

, pretty much cover that.

now with only those settings and nothing more ,
a profile would and/or could let you die forever ... repair cost , death ... forever.
*that is the only real reason i see used and/or used myself is the
<TrinityMaxDeaths questId="1" max="25" /> code

^ but you cant always find it in the profile ?
- you should only be searching for the word " maxdeaths " with notepad++ ,
you should clearly see it then.
* some profiles are linked and it may not show up where you think it does ...
- note : it can be changed on the fly , so you need to change them all if there is multiple xml files.

Best of Luck , its really simple - just don't let it overwhelm you ... it happens !

oktogo · Jul 2, 2014

Ironically enough I just started getting this error out of the blue... Been using the same profile for ages without issues. Gunna try fix actions posted by muff.

oktogo · Jul 2, 2014

MUFFDIVER said:
[Trinity]You have died too many times. Now restarting the game.
I personally just zipped up 'MaxDeaths.cs', left the zipped file in the same folder as the original and then deleted MaxDeaths.cs.

Worked perfect for me! Modifying ..DemonBuddy\Plugins\QuestTools\Helpers\Death.cs made the bot inoperable though.

Thanks again Muff.

MonsterHunter · Jul 3, 2014

Thank you Muffdiver! Took me a while to nail down where to add the extra line.

Moving Death/Maxdeath cs kills the bot from operating.

Basically you add the line into the profile you load into DB if it doesn't have the TrinityMaxDeath line.

Zachary · Jul 17, 2014

MUFFDIVER said:
[Trinity]You have died too many times. Now restarting the game.

Hey guys.

I had this issue as well... and man... what a run around trying to get a straight answer out of someone. I read through tons of posts on the issue... some new, some old... ALL unsolved. Either ignored all together, hadn't been followed up with, or the thread just died.

It was frustrating for me just seeing all these people getting 'generically' handled by people who didn't seem to give a $%^& ...enough to actually follow through with or follow up on with any reasonable customer service.

Anyway... I'm sorry you haven't been able to find a solution to your problem or haven't had one provided for you.

I do... have a couple 'options' that can probably help alleviate a little frustration. They may not be solutions that I would expect from a support professional and one of them (in most cases) I wouldn't particularly endorse myself but... it's something.

So here is the first one...

Work Around #1:

<TrinityMaxDeaths questId="1" max="25" />
Add the blue line that's above into the profile\xml file that your issue is occurring on.

An example is provided below:

Code:

<Profile> <Name>Just an Example</Name> <KillMonsters>Obviously</KillMonsters> <PickupLoot>Obviously</PickupLoot> <GameParams quest="1" step="-1" act="OpenWorld" resumeFromSave="False" isPrivate="True" numGames="-1" /> <Order> <ToggleTargeting questId="1" stepId="1" combat="True" looting="True" lootRadius="150" killRadius="80" /> [COLOR="#000080"] <TrinityMaxDeaths questId="1" max="50" />[/COLOR] .........more example code...... more code.... .........more code...... more code.... .........more example code...... more code.... </Order> </Profile>

I seen people recommending looking for and removing the <TrinityMaxDeaths questId="1" max="1" /> from any profiles they used... but most people could not find the entry at all. So with a little reverse psychology... I figured why not ADD the line, increase the number, and see if it overrides the DemonBuddy feature... and it did.

Work Around #2:

A more aggressive approach but again... all the same... it stops the problem and doesn't seem to create any new ones in the process.

You can modify, move, or delete... I normally wouldn't recommend this... but it works.

..DemonBuddy\Plugins\QuestTools\ProfileTags\MaxDeaths.cs
..DemonBuddy\Plugins\QuestTools\Helpers\Death.cs

Please... backup any files before editing or deleting!

I personally just zipped up 'MaxDeaths.cs', left the zipped file in the same folder as the original and then deleted MaxDeaths.cs.

Yes, maybe a unorthodox approach but... it's not my job to fix it and well I just had enough of dealing with it If someone wants to provide a better\technical solution or an actual proper fix... I'm sure you'd be popular

All the best and take care!

Second method did it for me, thanks muff!

Clowfor · Aug 7, 2014

Issue here is that if maxdeath is not set in the profile the max death is actually handled by Questhelper and the file botevents.cs and not by trinity nor DB. In this file you have the following piece of code.

private static void GameEvents_OnPlayerDied(object sender, EventArgs e)
{
Death.DeathCount++;
Death.LastDeathTime = DateTime.UtcNow;

Logger.Log("Player died! Position={0} QuestId={1} StepId={2} WorldId={3}",
ZetaDia.Me.Position, ZetaDia.CurrentQuest.QuestSNO, ZetaDia.CurrentQuest.StepId, ZetaDia.CurrentWorldId);

Death.MaxDeathsAllowed = 10;

if (Death.MaxDeathsAllowed <= 0)
return;

if (Death.DeathCount < Death.MaxDeathsAllowed)
return;

Logger.Log("You have died too many times. Now restarting the game.");
ProfileManager.Load(ProfileManager.CurrentProfile.Path);
ZetaDia.Service.Party.LeaveGame(true);

// This is bad, we shouldn't do this

Thread.Sleep(12000);
}

Adding the line with bold and red, should give you 10 deaths before a new game is created incase it havent been added in the profile.

Whatsmacroing · Aug 7, 2014

Thanks

turkeyslayer · May 29, 2015

MUFFDIVER said:
[Trinity]You have died too many times. Now restarting the game.

Hey guys.

I had this issue as well... and man... what a run around trying to get a straight answer out of someone. I read through tons of posts on the issue... some new, some old... ALL unsolved. Either ignored all together, hadn't been followed up with, or the thread just died.

It was frustrating for me just seeing all these people getting 'generically' handled by people who didn't seem to give a $%^& ...enough to actually follow through with or follow up on with any reasonable customer service.

Anyway... I'm sorry you haven't been able to find a solution to your problem or haven't had one provided for you.

I do... have a couple 'options' that can probably help alleviate a little frustration. They may not be solutions that I would expect from a support professional and one of them (in most cases) I wouldn't particularly endorse myself but... it's something.

So here is the first one...

Work Around #1:

<TrinityMaxDeaths questId="1" max="25" />
Add the blue line that's above into the profile\xml file that your issue is occurring on.

An example is provided below:

Code:

<Profile> <Name>Just an Example</Name> <KillMonsters>Obviously</KillMonsters> <PickupLoot>Obviously</PickupLoot> <GameParams quest="1" step="-1" act="OpenWorld" resumeFromSave="False" isPrivate="True" numGames="-1" /> <Order> <ToggleTargeting questId="1" stepId="1" combat="True" looting="True" lootRadius="150" killRadius="80" /> [COLOR="#000080"] <TrinityMaxDeaths questId="1" max="50" />[/COLOR] .........more example code...... more code.... .........more code...... more code.... .........more example code...... more code.... </Order> </Profile>

I seen people recommending looking for and removing the <TrinityMaxDeaths questId="1" max="1" /> from any profiles they used... but most people could not find the entry at all. So with a little reverse psychology... I figured why not ADD the line, increase the number, and see if it overrides the DemonBuddy feature... and it did.

Work Around #2:

A more aggressive approach but again... all the same... it stops the problem and doesn't seem to create any new ones in the process.

You can modify, move, or delete... I normally wouldn't recommend this... but it works.

..DemonBuddy\Plugins\QuestTools\ProfileTags\MaxDeaths.cs
..DemonBuddy\Plugins\QuestTools\Helpers\Death.cs

Please... backup any files before editing or deleting!

I personally just zipped up 'MaxDeaths.cs', left the zipped file in the same folder as the original and then deleted MaxDeaths.cs.

Yes, maybe a unorthodox approach but... it's not my job to fix it and well I just had enough of dealing with it If someone wants to provide a better\technical solution or an actual proper fix... I'm sure you'd be popular

All the best and take care!

thank u muffdiver, 1st option did it for me whereas the 2nd one stopped trinity from operating.
glad i was able to find this page. cheers

Search

Search

Logging out After Death

boat_58

Member

Tony

"The Bee"

boat_58

Member

oktogo

New Member

boat_58

Member

Jayster

New Member

boat_58

Member

MUFFDIVER

Member

boat_58

Member

tomer132246

New Member

spaceitout

New Member

oktogo

New Member

oktogo

New Member

MonsterHunter

New Member

Zachary

New Member

Clowfor

New Member

Whatsmacroing

New Member

turkeyslayer

Member