Rift Bot - Yet Another Rifter!

Ok, I finally found a solution.

Don't use beta DB. I went with the official DB and moved the files over from the original thread and it works now. Just witnessed Diablo, Izual and Cursed Chest working.

In addition, I used your settings and it's working great. Monk T1

 

My package does not include the beta. How did you end up with that?

 

So this doesnt work at all with .25 Trinity...
Enters game and then quits again over and over...
Should i just use trinity .24 and disable ezupdater for now so that it doesnt try to update .24 to .25??

 

yes

 

Just tried this. Still joins game just to exit again right away...
Damn! Even did a fresh install..
Guess im back to just doing bounty runs until this shit gets sorted
So annoying.. I have 1k rift keys now haha
Oh well......

 

Have you tried my package?

 

Just found another point where the bot got stuck....



Trinity] Your bot got stuck! Trying to unstuck (attempt #1 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288685"
[Trinity][Performance] Execution of the block NavigateTo took 1520.04ms.
[Trinity] Your bot got stuck! Trying to unstuck (attempt #2 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288685"
[Trinity][Performance] Execution of the block NavigateTo took 1523.11ms.
[Trinity][Performance] Execution of the block NavigateTo took 1540.07ms.
[Trinity][Performance] Execution of the block NavigateTo took 1690.21ms.
[Trinity] Your bot got stuck! Trying to unstuck (attempt #3 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288685"
[Trinity][Performance] Execution of the block NavigateTo took 1516.80ms.
[Trinity][Performance] Execution of the block NavigateTo took 1808.14ms.
[Trinity][Performance] Execution of the block NavigateTo took 1414.19ms.
[Trinity][Performance] Execution of the block NavigateTo took 1796.61ms.

 

Running fine on .25

Only problem is at times the bot just wanders aimlessly not exploring/looking for 2nd level and eventually it resets the game ._. I would say 70% AFKable.

 

I appreciate you reporting, but can you report like I've done here? It's much easier for us to try to fix if we have this information.

At least the LevelAreaId and the map viewer open with "Render Explore Nodes" enabled.

 

Oksehode -- The Rift upgrades you did works really good. Only issue which made it not overnight for me, is the new area with all the portals. Forgot the name of the top of my head. Starts with a C.

Map looks like the area before you reach malthael.

Hope this helps. At work so no logs, I didnt get errors, just runs back in forth between portals.

When I manually clicked the portal it would go, clear some area, then go back using the port on its own to go backwords.

Using your exact set up btw.

Cheers

 

View attachment 126487

I know why the bot got stuck now...... that area is not included in the explorable areas..... so the bot cannot respond correctly to it..... in addition the entire right hand side of that area is blacked out, which means the bot will not consider it as the possible entrance to the next level.

 

Yeah, there is nothing I can do about that. It's a Trinity/DemonBuddy issue. Waiting for Trinity .26 or some C# guru on the forum figures it out.

 

I had a problem too, it did one of the rifts perfectly, then on the same map as fistbarb refers to, completely crapped out.

I am over it, I will just do the ghom runs/Bounty runs until this works perfect with .25.

 

Why doesnt your package contain ezupdater and all that shit? :-D
Anyway, works perfectly for rifts <3

 

Can't view the attachment.

 

odd.......i can view it.....

 

Because my package depends on everything in it. Not all the latest versions of Trinity and QuestTools.

My package is for the rift profile only. I have not tried it with bounty's. I use a separate DB folder for everything else.

 

Ah..
Makes sense since bounty runs works perfect with .25 trinity version as well as newest version of DB beta.
So nice that yours works good for just rifts
Thx. Now i can hopefully get rid of my rift keys hehe

 

Now I see it. Is the bot just trying to walk through the wall up there?

I'm gonna see if I can fix it.

Another thing that might be useful is if you can check activity the bot is trying to do when It get stuck. It's at the bottom of the DB window.

 

these are jokes trying to run it 5 hours
Old profiles operated better, new getting worse shit

can anyone tell me what is wrong, bot after entrance to the rift does not move