Rift Bot - Yet Another Rifter!

Oksehode · Apr 24, 2014

DB started spamming:

Code:

Exception when terminating bot thread. System.NullReferenceException: Object reference not set to an instance of an object.
   at QuestTools.MoveToMapMarker.RefreshActorInfo()
   at QuestTools.MoveToMapMarker.<CreateBehavior>b__a(Object ret)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.DecoratorContinue..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Sequence..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Bot.BotMain.()

when I entered a "The Cursed Hold (Warden)" map. Bot unresponsive and I had to stop and start it.

Any ideas?

DyingHymn · Apr 24, 2014

Add FAQ on Stopping the bot. Reason:Failed to locate profile. No more answer to that.

DyingHymn · Apr 24, 2014

Oksehode said:

DB started spamming:

Code:

Exception when terminating bot thread. System.NullReferenceException: Object reference not set to an instance of an object.
   at QuestTools.MoveToMapMarker.RefreshActorInfo()
   at QuestTools.MoveToMapMarker.<CreateBehavior>b__a(Object ret)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.DecoratorContinue..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Sequence..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Bot.BotMain.()

when I entered a "The Cursed Hold (Warden)" map. Bot unresponsive and I had to stop and start it.

Any ideas?

I've not met the map, tho it is a Trinity memory leakage problem

Oksehode · Apr 24, 2014

DyingHymn said:
I've not met the map, tho it is a Trinity memory leakage problem

Yeah I know It's not profile related, but it doesn't happen every time. Just sometimes.

mrbigsexy · Apr 24, 2014

See log. Bot was stuck and just spamming stuff - I don't even know for how long but for some reason my 3 minute gold timer didn't trigger it to leave =/.

LOG HERE: View attachment 5324 2014-04-24 15.00.txt

17:21:32.602 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 517305dd-efa9-4ec5-9ed0-7c10b94fdb40
17:21:32.758 INFO ProfileManager Loaded profile Rift Bot Common/Explore
17:21:32.766 DEBUG TrinityDebug [Trinity] Setting Window Title
17:21:32.766 DEBUG TrinityDebug [Trinity] Window Title Set
17:21:32.782 INFO ToggleTargetingTag ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
17:21:32.783 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 6a119a2a-efb0-4de6-988e-da7299870bad
17:21:32.894 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] e64fc8ef-814e-455d-99e6-4d1baa56613d
17:21:32.923 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 4d519bbc-b9f8-422d-9280-393b088bed95
17:21:33.025 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 23864dcd-c874-402b-b8ac-afeaed0842a9
17:21:34.041 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] e55edc9b-4ab2-4d2c-a3bc-6603d113feb6
17:21:34.198 INFO ProfileManager Loaded profile Rift Bot Optimized Explore
17:21:34.207 DEBUG TrinityDebug [Trinity] Setting Window Title
17:21:34.207 DEBUG TrinityDebug [Trinity] Window Title Set
17:21:34.222 INFO ToggleTargetingTag ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
17:21:34.222 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 32c0d897-8fd9-47a8-9614-75134a967b52
17:21:34.338 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 8d62eb2a-596e-4b9d-a28f-0f3f3194247c
17:21:34.338 INFO LogMessageTag [Rift Bot] Explore Boneyards @ 20/30/0.5
17:21:34.361 INFO Logger [Trinity] TrinityExploreDungeon Started
17:21:34.362 DEBUG GridSegmentation ========== Grid segmentation resetting!!! ============
17:21:34.362 DEBUG GridSegmentation ========== Grid segmentation resetting!!! ============
17:21:34.362 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 776c7ef6-a745-4184-931e-6e29f7a14774
17:21:34.365 DEBUG GridSegmentation ========== Grid segmentation resetting!!! ============
17:21:34.369 DEBUG DungeonExplorer DungeonExplorer has new areas to explore. Generating new route.
17:21:34.373 DEBUG DungeonExplorer Returning route!
17:21:34.374 INFO Logger [Trinity] Rift portal exit marker within range!
17:21:34.374 INFO Logger [Trinity] Rift is done. Tag Finished.
17:21:34.466 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 72c13785-c6d5-4ddd-bf8d-0088edacca52
17:21:34.627 INFO ProfileManager Loaded profile Rift Bot Common/Explore
17:21:34.634 DEBUG TrinityDebug [Trinity] Setting Window Title
17:21:34.635 DEBUG TrinityDebug [Trinity] Window Title Set
17:21:34.651 INFO ToggleTargetingTag ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
17:21:34.651 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 96b801e1-62da-468b-bef3-77700f2fa1a6
17:21:34.763 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 147f712f-373e-435f-b8b6-9722a977c9c2
17:21:34.791 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 3b23d17c-5962-4f02-a874-e5bd479743a0
17:21:34.892 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] 51d54b0e-463f-44a0-a257-e117c6a854e9
17:21:35.983 DEBUG TreeHooks Replaced hook [ProfileOrderBehavior_Hook] e1f95104-ba7b-4780-ab85-f4f6fbe30c26
17:21:36.136 INFO ProfileManager Loaded profile Rift Bot Optimized Explore
17:21:36.144 DEBUG TrinityDebug [Trinity] Setting Window Title
17:21:36.145 DEBUG TrinityDebug [Trinity] Window Title Set

DyingHymn · Apr 24, 2014

gotteshand said:
DyingHymn,

there might be a way to tell the difference between the "big" and "small" version of The Cursed Hold (Warden)..

By using the coordinates and ActorExistsAt.. Both versions spawn their entrance at different coordinates.. the "big" version is <If condition="ActorExistsAt(176000, 303.0258, 1320.288, 1.596355, 10)">
Now gotta do the same for the small one then run into these maps multiple times to confirm that coordinates are always the same and then well we have a way to tell the difference

Also 4 different Pandemonium Fortress rift design runs no stuck smooth completion at [Rift Bot] Explore Pandemonium Fortress @ 9/15/0.55 settings and another thing for Pandemonium to explore properly we need to reduce combat range to a a minimum it helps a lot with stuck issues allot of the stuck comes from bot trying to fight shit he can't reach.. combat radius of around 15 or so should be good we wont need much more on that narrow map anyway not like it has tons of mobs to begin with.

Right, one thing to note is that there are a huge number of actors for rift portals, but we can use markerid to solve this problem so that is not a big deal. If the two entrances are in the same position, we can also first walk to the end to see whether the exit for small map is there. Tho need more finding on the map. That fxxking random maps.

DyingHymn · Apr 24, 2014

btw, if we can also do similar analysis to the tower of the damned, we can get rid of riftbot plugin. One missing function it implemented is to ignore the portals right beneath the bot, which is a common case for that map(s).

Qetyip · Apr 24, 2014

DyingHymn said:
That is a main problem with DB. sometimes it cannot clear the cache when map changed.

Make a plugin for this? =D

DyingHymn · Apr 24, 2014

Qetyip said:
Make a plugin for this? =D

way toooo hard for me

Oksehode · Apr 24, 2014

That's a large prison map!

kOmiC · Apr 24, 2014

is there a way to only do the bounties and not rift?

Oksehode · Apr 24, 2014

kOmiC said:
is there a way to only do the bounties and not rift?

http://www.thebuddyforum.com/demonb...dventure-mode-bounties-community-edition.html

kOmiC · Apr 24, 2014

cool ill try it. thanks

DyingHymn · Apr 24, 2014

Oksehode said:
That's a large prison map!
View attachment 126630

Can you check on the position of the entrance? Walk near the entrance and click dump object then found the one with name "xxx_portal_xxxx"

Oksehode · Apr 24, 2014

DyingHymn said:
Can you check on the position of the entrance? Walk near the entrance and click dump object then found the one with name "xxx_portal_xxxx"

It's to late. I already closed the rift.

DyingHymn · Apr 24, 2014

Oksehode said:
It's to late. I already closed the rift.

That's fine. It will be there.

DyingHymn · Apr 24, 2014

I've searched for some images and found the big prison is always exactly the same. So we can make some pivot points and use them instead of TED.

azarielrdm · Apr 24, 2014

Endless loop in a rift set to full. Trin .26, beta .394, qt .50, riftbot 0.0.8:

Log as follows:

ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Cursed Hold (Warden) @ 35/20/0.2
[Trinity] TrinityExploreDungeon Started
[Trinity] Fully explored area! Tag Finished.
Loaded profile Rift Bot Full
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Cursed Hold (Warden) @ 35/20/0.2
[Trinity] TrinityExploreDungeon Started
[Trinity] Fully explored area! Tag Finished.
Loaded profile Rift Bot Full
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Cursed Hold (Warden) @ 35/20/0.2
[Trinity] TrinityExploreDungeon Started
[Trinity] Fully explored area! Tag Finished.
Loaded profile Rift Bot Full
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Cursed Hold (Warden) @ 35/20/0.2
[Trinity] TrinityExploreDungeon Started
[Trinity] Fully explored area! Tag Finished.
Loaded profile Rift Bot Full
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Cursed Hold (Warden) @ 35/20/0.2
[Trinity] TrinityExploreDungeon Started
[Trinity] Fully explored area! Tag Finished.
Loaded profile Rift Bot Full
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Cursed Hold (Warden) @ 35/20/0.2
[Trinity] TrinityExploreDungeon Started
[Trinity] Fully explored area! Tag Finished.
Loaded profile Rift Bot Full
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Cursed Hold (Warden) @ 35/20/0.2
[Trinity] TrinityExploreDungeon Started
[Trinity] Fully explored area! Tag Finished.
Loaded profile Rift Bot Full
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore

And so on. Since it reloads the profile over and over the inactivity timer isn't tripping.

madhat · Apr 24, 2014

Can you make it kill pinata if found ? I love pinata

mrbigsexy · Apr 24, 2014

More issues with the most recent updates.

Log attached: View attachment 804 2014-04-17 00.17.txt View attachment 2476 2014-04-24 18.53.txt

Rift Bot - Yet Another Rifter!

Active Member

New Member

New Member

Active Member

New Member

New Member

New Member

New Member

New Member

Active Member

New Member

Active Member

New Member

New Member

Active Member

New Member

New Member

Member

New Member

New Member