Rift Bot - Yet Another Rifter!

btw this levelareaid is really meaningful to me. I will test my guess on this variable tmr. Wish a good result.

 

nice profile thanks a lot.

 

DB Log: Leaving level 2, entering level 3:

Code:

2014-04-18 16:38:55,671 [Main Bot Thread] INFO  Logger (null) - [Trinity] Found exitNameHash 1938876095!
2014-04-18 16:38:55,769 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] e52b4ea8-b15f-4374-9371-a708ab25f513
2014-04-18 16:39:02,668 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] 095f8ced-09ee-4aa3-87db-2f6de7acc4aa
2014-04-18 16:39:04,763 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 16:39:05,764 [Main Bot Thread] INFO  Logger (null) - [MoveToMapMarker] DestinationWorlId matched, finished 
2014-04-18 16:39:05,829 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] 85eb1954-5dca-49de-81c1-ace39273e031
2014-04-18 16:39:05,830 [Main Bot Thread] INFO  Logger (null) - [MoveToMapMarker] DestinationWorlId matched, finished 
2014-04-18 16:39:05,873 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] d0067770-f820-493d-a2d3-be38bf147725
2014-04-18 16:39:06,902 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] d1a7d64d-6e08-4241-a5e9-cdb2b6f2db1e
2014-04-18 16:39:06,902 [Main Bot Thread] INFO  LogMessageTag (null) - =======EXPLORE LEVEL 3======
2014-04-18 16:39:06,947 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 16:39:06,983 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 16:39:06,987 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 16:39:06,988 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 16:39:06,988 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 16:39:06,989 [Main Bot Thread] DEBUG TreeHooks (null) - Replaced hook [ProfileOrderBehavior_Hook] 0958f615-0c67-4cb1-9cae-d0632ad0b0eb
2014-04-18 16:39:06,992 [Main Bot Thread] DEBUG GridSegmentation (null) - ========== Grid segmentation resetting!!! ============
2014-04-18 16:39:06,997 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 16:39:07,002 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 16:39:09,602 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 16:39:09,604 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!
2014-04-18 16:39:41,941 [Main Bot Thread] INFO  Logger (null) - [Trinity] Clicking UI element Conversation Button (150110208)
2014-04-18 16:39:42,048 [Main Bot Thread] INFO  Logger (null) - [Trinity] Clicking UI element Conversation Button (150110208)
2014-04-18 16:39:57,858 [Main Bot Thread] DEBUG Logger (null) - [Trinity] Using Legendary Potion
2014-04-18 16:40:29,520 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 16:40:29,521 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!

I was using R11 - Full clear

 

You need to blacklist the broken chests.

Also, why does it leave game and create a new one every time? Just reload the profile instead..?

 

Full clear will ignore boss kill. Read the first post.

edit: I see you are mainly concerning the backtrack problem but not continue-after-boss-kill. There is almost nothing we can do. I will test my thought tmr on this issue though.

 

Thank you for this info.
leave and create is in fact faster than reload. And more failsafe.

edit: can you give me a link or thread on those broken chests? A general search shows nothing. Thanks.

 

If I delete the below portion of the xml code, will the bot not stop the rift if it finds the townstone? I would rather drop my gold inactivity timer as a failsafe than to have my guy get to lvl 2 of a big map and have it explore a small portion until finding the stone and try to leave. I don't want my guy to leave the rift after finding a townstone, I'd rather him leave due to gold inactivity if he gets stuck in a small lvl that is fully cleared with no additional levels (if that makes sense).

<While condition="not Me.IsInTown ">
<LogMessage quest="1" step="2" output="====>TOWNSTONE FOUND" />
<LogMessage quest="1" step="2" output="====>FORCE RESET" />
<If condition="CurrentWorldId == 288454">
<LogMessage quest="1" step="2" output="====>FULL EXPLORE LEVEL 1" />
<TrinityExploreRift questId="312429" stepId="2" until="RiftComplete" markerDistance="80" boxTolerance="0.1" boxSize="25" ignoreMarkers="False" />
<WaitTimer questId="1" stepId="1" waitTime="1500"/>
<LogMessage quest="1" step="2" output="====>RIFT BOSS DOWN" />
</If>
<WaitTimer questId="1" stepId="1" waitTime="500"/>
<WaitTimer questId="1" stepId="1" waitTime="500"/>
<WaitTimer questId="1" stepId="1" waitTime="500"/>
<WaitTimer questId="1" stepId="1" waitTime="500"/>
<TrinityTownPortal questId="1" stepId="1" />
<WaitTimer questId="1" stepId="1" waitTime="3000"/>
</While>

 

I know it does.

But backtracking to start, go back Right before where the rift Guardian was spawned and killed, backtracking again without doing the rest of the map is not Right. It did it for 10-15 min until i left game.

 

No, delete this part will let the bot stuck near the stone and loop infinitely.

I will not make a profile that depends on gold inactivity timer as it is both inefficient and "problematic" (I mean people will ask a lot of questions like WHY MY BOT EXPLORED THE SAME LEVEL FOR 10 HOURS?)

 

As I myself don't run the full version, I can only check the xml for you to see whether there are bugs.

 

See the log. There are a lot of

2014-04-18 16:40:29,520 [Main Bot Thread] DEBUG DungeonExplorer (null) - DungeonExplorer has new areas to explore. Generating new route.
2014-04-18 16:40:29,521 [Main Bot Thread] DEBUG DungeonExplorer (null) - Returning route!

Each one causes one backtrack. It is caused by the DungeonExplorer in Trinity. Though I will try find method to fix, I'm not sure whether it can work. It is mainly a Trinity issue.

 

I just encountered the same problem on the same WorldID, LevelAreaID and Name. While I am sitting here on this map, is there any other info you need me to get?

 

Is RiftBot plugin updated to .3 ?

 

Yes. Trinity .24, RiftBot Plugin .3, Quest Tools .45 and most recent DB Beta

 

Okay. I Will test the other version and see how that goes.

 

A screenshot of the map is excellent. But the info is already enough. Ty guy!

 

the plugin wont show in demonbuddy when i have placed it in the pugin file?

 

All current profiles for bounty/rift utilize the DungeonExplore feature of Trinity. *I think* all will suffer from the map.

 

First post USE section

if still missing, post a full log. make sure everything is up to date.

 

So far this is working great!

I am curious if anyone has any recommended builds for crusader botting?

Also my only complaint:

I wish it would ignore this and just keep clearing, its always so close to spawning the boss when this happens.

This would reduce the number of failed games if this was ignored, and you just let the gold inactivity timer do the reset for you if it continues exploring and finds nothing.