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

Rift Bot - Yet Another Rifting Profile!

Thanks sounds good, where did you get the newest Trinity, and Quest tools. Im still using 1.9.5.. Didn't upgrade to .6 because everything but the Goblins is perfect.
Getting over 5 LPH w/your profile.
 
@DyingHymn
You don't accept donation? I can't find any info about donation.
(I donated to Oksehode, he has a "donate" button.)
 
ran the past few hrs, works well, came back to 500 blood shards and some other good stuff.
 
In order to do an SVN Checkout - i use the repo link? sorry for being a newb :/
 
Big difference with the update. Nice job big papa! I will donate once i get my check.
 
Profile - "Rift Bot Full with Bounties" is failing big time, used 8 hours on 1 game with 1 leg...

It clicked my "gold inactivity" to -OFF and i first this morning.


But then i have to say that i loooooove "Rift Bot Common" -it works perfectly <3 <3
 
I see that the recommended version of DB is now 410 while it was 408 yesterday, did 410 get updated? I'm still on 408 because it worked great but the problem with quickjoin is a serious problem for me (friends/clanmembers joining my game when I bot).

Will update to 410 and see how it goes.
 
Lol. There is 1.9.7 now AS oksehode posted


1.9.7 just came out either today or yesterday, ive running mine for about a week now. i've been using rift bot full with bounties and no issues apart from trinity pathing problems
 
Exception during bot tick.System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Generic.List`1.set_Capacity(Int32 value)
at System.Collections.Generic.List`1.EnsureCapacity(Int32 min)
at System.Collections.Generic.List`1.Add(T item)
at Zeta.Bot.Pathfinding.PathFinder.FindPath(Point startPoint, Point endPoint, Boolean includeDiagonals, Int32 maxMilliseconds, Boolean allowPartialPaths)
at Zeta.Bot.Navigation.DefaultNavigationProvider.(Vector3 , Boolean )
at Zeta.Bot.Navigation.DefaultNavigationProvider.GeneratePath(Vector3 destination, String destinationName, Boolean useRaycast)
at Zeta.Bot.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at Zeta.Bot.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast)
at QuestTools.Helpers.MiniMapMarker.<VisitMiniMapMarkers>b__42(Object ret)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.()

getting stuck issues and its only on Act 3 map levels. Running DB beta 410, latest trinity 1.9.7 and quest tools. Rift common profile.
 
I see that the recommended version of DB is now 410 while it was 408 yesterday, did 410 get updated? I'm still on 408 because it worked great but the problem with quickjoin is a serious problem for me (friends/clanmembers joining my game when I bot).

Will update to 410 and see how it goes.

In option (d3 options that is) you can click a box that does that only requests or invites can join your game. quick join is disabled
 
[Trinity] Socketed Ascended Armor of Glory [chestArmor_norm_base_flippy-3212] [Chest] = (trashing blues)
[Trinity] Forbidden Plates [shoulderPads_norm_base_flippy-7391] [Shoulder] = (force salvage rare)
Opening stash
Opening stash
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
[Trinity] Your bot got stuck! Trying to unstuck (attempt #1 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="172909"
[Trinity] Your bot got stuck! Trying to unstuck (attempt #2 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="172909"
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items
Opening salvage window
Attempting to repair all items

anyone knows a fix for this ?

Anyone knows this?

I've run the bot for about 2 hours and this comes.
 
In option (d3 options that is) you can click a box that does that only requests or invites can join your game. quick join is disabled
only problem was that 408 enabled quickjoin REGARDLESS of what you chose in d3 options. (SERIOUS BUG)
 
i've read that you should be using 1.95 trinity as the newer ones have this sort of issue.
Thanks, should wait for newer version released through EZU

It seems only happened after your reach the % durability. Once occured, never get back..
 
Can someone please tell me the differences between common, explore and full versions?

Also, for some reason the bot is repetitively trying to repair gear despite them not being repaired. Anyone know how to fix this?
 
Last edited:
Back
Top