Rift Bot - Yet Another Rifter!

i think you need db beta 391

 

It will always interact with Olek and try to complete quest. If not, please post the log and I will see what's going on.

 

i meant always able to kill the boss to complete the full quest

 

Now it can detect whether a boss is killed using quest info. However if the boss spawns in a very remote distant area, Trinity won't go to kill it. That is the main and maybe the last problem now for DB or Trinity.

 

I'm not sure if anyone has this problem but the bot opens the rift and stands there...

Code:

[Trinity] Loading new profile.
Loaded profile Rifter - A Bot for Rifts!
[Trinity] TrinityExploreDungeon timer ended (0), tag finished!

I have to stop the bot and restart it.

 

It seems that the TED timer is triggered with zero seconds. Which version of Trinity, RiftBot, and profile are you with? Full log tells a story

 

ok found big problem in act 5 very hard stucks

i think problem is the portal porter

[Trinity] Your bot got stuck! Trying to unstuck (attempt #5 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288454"


i unstuck per hand more stuck act 5 not playable

 

yea thats what i mean by always able to kill the boss ... so have to wait db or rrix to update

 

Trinity .24, Rift r3. Sorry I didn't know you have updated a new rev. Will try that right away.

 

I'd say yes. What is good is that such kind of spawns are really rare (to me), 1 out of 20 or 50 sth.

 

If you mean by the map before malthael, that is a known issue with Trinity pathing. rrrix has been working on a fix for this in the last a few releases.

A temporary solution (to me) is to set the container open range to 30. Not too bad.

 

ah ok thx

 

Okay - the first two rifts went smooth.
But then I came across "Pandamonium" and it started to bug out. I just ran the same route for like 10 mins until I paused it and moved it to level 2 manually.
Then in level 2 it discovered the whole map, even the portal to next level, but forced grid reset anyways. "It was act 4, one of the first places." It wouldn't detect the portal, so I moved it to level 3 manually and killed the rift guardian.

I have noted down WorldID, LevelID and Name of level 1,2,3.

Level 1:
WorldID: 288454
LevelID: 333758
Name: X1_LR_Level_01

Level 2:
WorldID: 288685
LevelID: 346565
Name: X1_LR_Level_02

Level 3:
World ID: 288687
LevelID: 312607
X1_LR_Level_03


Btw. This is the only issue so far. I will report if more come

 

Thanks for the report. Not detecting portal should be a Trinity-issue unless there are logs saying '[RiftBot] Rifting, exit found. Tag Finished.' but not taking the portal. If grid reset is triggered, there is a problem with the parameters used for TED.

However you can try the latest r8, which increased the portal detection range. Could work better.

Pandamonium is really a bad map. What about leaving the rift and repeat once this map is encountered?

 

had a full bag, killed rift boss, ported and sold but didnt port back to grab rift boss loot, just left game. This trinity issue or rift profile?

 

Unfortunately Trinity. This problem is issued in the very early pages of this thread. Turn off looting yellows/blues.

 

Thank you. Will do. Great profile btw

 

Thanks for the reply.

This is what I have from my db logs:

Code:

2014-04-18 07:16:40,580 [Main Bot Thread] INFO  Logger (null) - [Trinity] Your bot got stuck! Trying to unstuck (attempt #1 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288454"
2014-04-18 07:16:40,580 [Main Bot Thread] DEBUG Logger (null) - [Trinity] (destination=<810, 805, 0>, which is 19.84347 distance away)
2014-04-18 07:16:40,582 [Main Bot Thread] DEBUG TrinityDebug (null) - [Trinity] Unable to generate new unstucker position! rayCast=40 navObsticle=0 - trying RANDOM point!
2014-04-18 07:16:42,084 [Main Bot Thread] ERROR PerformanceLogger (null) - [Trinity][Performance] Execution of the block NavigateTo took 1508.93ms.
2014-04-18 07:16:47,989 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:16:47,992 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:17:00,138 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:17:00,139 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:17:09,975 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:17:09,977 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:17:17,167 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:17:17,168 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:17:25,015 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:17:25,016 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:17:49,630 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:17:49,632 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:18:32,087 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:18:32,088 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:19:02,310 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:19:02,310 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:20:05,583 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:20:05,584 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:20:21,061 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:20:21,062 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:21:20,483 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:21:20,484 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:21:23,196 [Main Bot Thread] INFO  Logger (null) - [RiftBot] Rifting, exit found. Tag Finished.
2014-04-18 07:21:23,246 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] 55c033c3-3723-44cd-b216-55598ad74b0e
2014-04-18 07:21:24,806 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] 0981e9e8-4166-4d2b-a906-e5879a3fef82
2014-04-18 07:21:27,816 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 07:21:27,846 [Main Bot Thread] INFO  Logger (null) - [MoveToMapMarker] DestinationWorlId matched, finished 
2014-04-18 07:21:27,919 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] 843de306-a571-4811-b105-38d97bb205fa
2014-04-18 07:21:28,971 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] 85eebca2-ef69-46d6-bc82-d7358f35e6f4
2014-04-18 07:21:28,973 [Main Bot Thread] INFO  LogMessageTag (null) - =======EXPLORE LEVEL 2======
2014-04-18 07:21:28,989 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 07:21:29,032 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:21:29,039 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:21:29,040 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 07:21:29,040 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 07:21:29,041 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] eb22223b-cdbd-4288-8440-72ee93574b23
2014-04-18 07:21:29,043 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 07:21:29,050 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:21:29,055 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 07:21:55,500 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 07:21:55,501 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!

This was in Act 4 where it wouldn't take the portal.

I agree with Pandamonium might be a problem.
Is there a way to make seperate profiles for specific Level/World Ids?

 

It seems like a big-boxsize problem. Try r8, may resolve this issue a bit.

As to profiles for worlds, yes with RiftBot 0.0.3. Every map type can have different parameter with only two lines of code. But that is a big project and maybe need community help as it's almost impossible for me to test every possible maps with the two parameters.

 

I'm getting this error with .24 and r8:

System.Exception: Element TrinityExploreRift is not supported. Please check your XML and try again.

Any ideas?