What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Rift Bot - Yet Another Rifter!

Status
Not open for further replies.
erxxlu said:
Currently running a rift with .7 of your Riftbot unfortunately I forgot to update QT but it's running very smooth at the moment!

Is "Add PriorityScenes to default exploration" something we need to do or something you changed in the plugin?
Click to expand...

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. :(
 
triccuz said:
Testing it right now. (also with SimpleFollow)

Flipflopping at the entrance of Soullbound Realm 2 on the stairs
Click to expand...

flipflopping is unfortunately not solvable on my side. It is (I assume) related with DB's path generation rule/frequency.
 
DyingHymn said:
One more thing, could you tick the "Render Explore Nodes" option when taking screenshot? That is in fact the key of making a good parameter. :) ty!
Click to expand...

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
 
Oksehode said:
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
Click to expand...

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:
[262335FC] Type: Player Name: Monk_Female-91 ActorSNO: 4717, Distance: 0
[26237670] Type: Monster Name: Hireling_Templar-100 ActorSNO: 52693, Distance: 12.89899
[26255BFC] Type: Item Name: CraftingMaterials_Flippy_Global-20234 ActorSNO: 137958
[26263FB8] GizmoType: DestroySelfWhenNear Name: RatSwarm_lineA-20181 ActorSNO: 87172 Distance: 61.97889 Position: <1009.401, 1309.612, -7.629395E-06> Barracade: False Radius: 6.232893
[26233A48] GizmoType: BreakableDoor Name: a1dun_Leor_Jail_Door_Breakable_A-20209 ActorSNO: 95481 Distance: 64.12377 Position: <1042.5, 1380, -3.051758E-05> Barracade: True Radius: 13.62475 Health0.00100000004749745/1
[26236DD8] Type: Monster Name: x1_SkeletonArcher_Westmarch_Ghost_A-20208 ActorSNO: 310888, Distance: 103.7729
[26241120] GizmoType: Chest Name: a1dun_Leor_Tool_Rack_A_01-20207 ActorSNO: 58317 Distance: 120.2585 Position: <951.2206, 1340.253, 0> Barracade: False Radius: 7.240044
[2625ADA0] GizmoType: DestroySelfWhenNear Name: RatSwarm_lineA-20197 ActorSNO: 87172 Distance: 132.884 Position: <1073.031, 1189.271, -1.525879E-05> Barracade: False Radius: 6.232893
[26235410] GizmoType: DestroySelfWhenNear Name: RatSwarm_lineA-20194 ActorSNO: 87172 Distance: 135.3819 Position: <1079.615, 1187.075, 0> Barracade: False Radius: 6.232893
[262632D4] GizmoType: BreakableDoor Name: a1dun_Leor_Jail_Door_Breakable_A-20292 ActorSNO: 95481 Distance: 138.017 Position: <939.5, 1277.5, 0> Barracade: True Radius: 13.62475 Health0.00100000004749745/1
[26243C18] Type: Environment Name: Dungeon_Stone_Invis-18183 ActorSNO: 179951, Distance: 268.2924
[26245194] Type: Environment Name: Dungeon_Stone_Invis-18114 ActorSNO: 179951, Distance: 268.2924
[26239038] Type: Environment Name: Dungeon_Stone_Invis-16893 ActorSNO: 179951, Distance: 268.2924
[26262A3C] Type: Environment Name: Dungeon_Stone_Invis-16694 ActorSNO: 179951, Distance: 268.2924
Click to expand...

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 ;)
 
DyingHymn said:
I am not exp.ing similar crashes. I suspect it is related with a "not so good" version of .NET 3.5/4
Click to expand...

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?
 
Last edited:
erxxlu said:
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 ;)
Click to expand...

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
 
Last edited:
Oksehode said:
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?
Click to expand...

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.
 
DyingHymn said:
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.
Click to expand...

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. :)
 
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
 
erxxlu said:
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
Click to expand...

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.
 
In middle of the second rift I'm getting massive Trinity Performance Messages, Lags ingame and I simply die due to those lags...


Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Rift Bot] Explore Arreat Crater @ 15/0.3
[Trinity] TrinityExploreDungeon Started
[Trinity] Unable to navigate to target! Blacklisting x1_Ghost_Dark_A SNO=309114 RAGuid=1169358875 dist=13 canFullyPath=False
[Trinity] Unable to navigate to target! Blacklisting x1_Ghost_Dark_A SNO=309114 RAGuid=1211236390 dist=18 canFullyPath=False
[Trinity] Your bot got stuck! Trying to unstuck (attempt #1 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288454"
[Trinity][Performance] Execution of the block NavigateTo took 1508.97ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1530.58ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1548.23ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1548.46ms.
[Trinity][Performance] Execution of the block HandleTarget took 1597.67ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1463.20ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1481.66ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1481.89ms.
[Trinity][Performance] Execution of the block HandleTarget took 1836.86ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1302.84ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1321.66ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1321.92ms.
[Trinity][Performance] Execution of the block HandleTarget took 1483.28ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1389.37ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1411.61ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1411.86ms.
[Trinity][Performance] Execution of the block HandleTarget took 1626.22ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1489.13ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1538.40ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 1538.60ms.
[Trinity][Performance] Execution of the block TargetCheck took 1538.81ms.
[Trinity] Player is dead
[QuestTools] Player died! Position=<1611.5, 732.4796, 0.1000015> QuestId=312429 StepId=2 WorldId=288454
Click to expand...
 
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
 
Last edited:
frstimr said:
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. =/
Click to expand...

Without a problem is fantastic and no log needed! :)
 
erxxlu said:
In middle of the second rift I'm getting massive Trinity Performance Messages, Lags ingame and I simply die due to those lags...
Click to expand...

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?
 
hpark62 said:
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?
Click to expand...

I don't know. But at least we have something working great right? Be optimistic on devs and rrrix :)
 
Status
Not open for further replies.
Back
Top