Rift Bot - Yet Another Rifter!

Nothing on your side except update via svn.

All works are done behind that and I always try to stick to it. Unfortunately I broke this rule today by requesting a downgrade of Trinity.

 

flipflopping is unfortunately not solvable on my side. It is (I assume) related with DB's path generation rule/frequency.

 

Sure thing. I don't know why I haven't done that yet for the screenshots.

Unrelated to profile:
Is it just me or does Demonbuddy crash every time you shut it down? (aka. close the .exe file) Beta .394

 

I am not exp.ing similar crashes. I suspect it is related with a "not so good" version of .NET 3.5/4

 

Flipflopping w/ Trinity .24 QT .21 and Riftbot .7

ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Boss Spawned
[Trinity] Your bot got stuck! Trying to unstuck (attempt #1 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288687"
[Trinity][Performance] Execution of the block NavigateTo took 1508.85ms.

WorldId: 288687
Levelareaid: 334821
Name: X1_LR_Level_03

Position: x="1070.104" y="1322.122" z="0.1000001" (new Vector3(1070.104f,1322.122f,0.1000001f))
SceneId: 91435

QuestId: 312429
StepId: 2

Current Box Size: 20
Tolerance 0.0.1

Object Dump:

Hope this is due to the missing QT Update and if not I hope this helps if you need more informations just tell me I'll wait in here til you've got what you need

 

That's my thought as well. I am however using the ones that is posted in the beta thread and running the .exe file inside the help folder.

Are you noticing better performance using the official release of DB rather than .394?

 

There is a tldr explanation in FAQ. Here I explain more clearly.

Suppose we have a chest at location (0,0), the bot is at location (1,0), and the TrinityExploreDungeon wants to further explore the map with the next target location at (2,0), flipflop happens.

In practice this case is actually considered and well handled using a weighting scheme. However, when some complex landscapes are introduced, it seems that the thing does not work as intended.

Let's recall the cave of assassin. There are a lot of cliffs and gaps. If the bot noticed a chest at the other side of the cliff, and a simple straightline pathing (in fact more complex) cannot reach it, flipflop happens.

edit: you can see the statusbar changes between TrinityExplore and openning chest/picking up health globe/taking shrine when flipflop happens

 

No idea of performance as my PC is kind of uber ones. but in terms of errors in red color, release *seems* to be better. Only error I noticed was ReadProcessMemory which is unavoidable.

 

I meant with errors and backtracking etc of course. My PC is kinda uber also so "performance" is not an issue. Wrong use of word.

 

At least release is not worse so I decided to take it

 

Very well explained! Thank you

Will it flipflop like forever or is there a fallback?

I'm planning on leaving it alone for a couple of hours and I noticed the gold inactivity timer isn't working at the moment so I'm curious if I will find my bot was flipflopping for several hours when I'm back?

Now running with QT. 45

 

Frankly speaking I don't know the exact answer. In my experience the flipflop has a timer and that will prevent from flipflopping forever, but I have no idea how does it work.

Gold timer should work, but as rrrix has been changing its functionality (pause when bot pause), it might be unstable.

 

you can just decrease flip-flop attempts in the Weighting.cs file

 

Yup, but that's not profile related. I usually do that myself manually.

 

In middle of the second rift I'm getting massive Trinity Performance Messages, Lags ingame and I simply die due to those lags...

 

Well, so far it ran for like 3 hours or so without a problem, stopped it because I had to take laptop to work. Can I still pull any logs or whatever for you? I didn't have any logging running besides what might be enabled by default. =/

{EDIT} Forgot to say, I was using 0.6 and the QT .45 and Trinity .24 in your OP and DB 1.1.1819.357

 

Without a problem is fantastic and no log needed!

 

That is something I totally have no idea on. Anyone may give an explanation on that? It would be very interesting.

 

Ah...so many 'working old versions' and 'not working new version'... 'new version of DB with old version Trinity combination' or vice versa are such pain lol. I'm just going to take a break in botting - until everything kind of sets off... but will it ever be?

 

I don't know. But at least we have something working great right? Be optimistic on devs and rrrix