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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Rift Bot - Yet Another Rifter!

Status
Not open for further replies.
@Oksehode, you have error in profile included with .rar -> RiftExploreCommon.xml ->
<If condition="CurrentLevelAreaId == 275923"> <!-- Forgotten Battlefield-->
<LogMessage quest="1" step="2" output="[Rift Bot] Explore Forgotten Battlefield @ 15/30/0.5" />
<TrinityExploreRift questId="1" stepId="2" until="FullyExplored" markerDistance="45" boxSize="15" pathPrecision="30" boxTolerance="0.5"/>
<LoadProfile file="RiftFull.xml" />
Click to expand...
After this must follow </If> (Line 104-107).
 
Derrek said:
@Oksehode, you have error in profile included with .rar -> RiftExploreCommon.xml -> After this must follow </If> (Line 104-107).
Click to expand...

Yeah I just noticed and I'm correcting it and re-uploading. Thanks for the heads up though.
 
Oksehode said:
Here is a package I made to make this profile work amazing. It includes the released version of Demonbuddy and the recommended versions of the plugins needed to make it work almost flawless.
Demonbuddy-with-all-needed-profiles-and-plugins.zip

1. Unpack the zip to a folder of your choice.
2. Start Diablo and login to your account so you get to your character screen else you will get an error in Demonbuddy.
3. Start Demonbuddy.exe
4. Insert your key to login
5. Click on the "Plugins" tab and enable QuestTools, Trinity and RiftBot
6. Exit Demonbuddy
7. Delete the "CompiledAssemblies" folder inside your Demonbuddy folder
8. Start Demonbuddy.exe
9. Click on the arrow next to the "Settings" button and enable "Open Loot containers" and "Open Chests". Loot Radius 100/Kill Radius 80. Repair Durability to 25% to make it work correctly.
10. Choose your preferred difficulty under "Game Difficulty".
11. Save and Close.
12. Click on the "Plugins" tab. Click on "Trinity" then click the "Config" button.

Combat/Misc:
Trigger range for Elite Combat = 30
Trigger range for Trash Combat = 30
Minimum Trash Mob Pack Size = 1
Trash Pack Cluster Radius = 30
Disable"Force Kill Summoners"
Set Treasure Goblins to Kamikaze (Decrease this option if the bot tries to walk through walls and over cliffs to get to him)
Enable "Attempt to avoid AOE" and "Kite to Avoid Death on Low HP"
Disable "Path Around AOE", "Avoid Savage Beast Charge", Attack Mobs in AOE" and "Avoid Fire Chains"

Objects
Container Open Range = 30
Enable "Open Chests"

Advanced
"Enable Gold Inactivity" = 180

As for the rest of the settings in Trinity, set to your own preference. These settings help the bot do the rifts more smooth.

The profiles to use is inside the Profile folder.

Everything is updated for best performance with this profile.
Click to expand...

WTF is the deal w/ using a retarded downloading site requiring the installation of a download manager?
 
Hellcom said:
WTF is the deal w/ using a retarded downloading site requiring the installation of a download manager?
Click to expand...

You don't need a download manager to download it. You just use the link and click on the filename on top of the page.

Untitled.webp
 
Last edited:
I downloaded the new package of oksehode and set it up as explained but i still get this error :/

[Rift Bot] Open Rift
[Rift Bot] Enter Rift
[GameUI] Clicking UI element Conversation Button (1178034176)
[Trinity] Clicking UI element Conversation Button (1178034176)
Failed to load profile: '<' is an unexpected token. The expected token is '>'. Line 109, position 3.
System.Xml.XmlException: '<' is an unexpected token. The expected token is '>'. Line 109, position 3.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(String expectedToken1, String expectedToken2)
at System.Xml.XmlTextReaderImpl.ParseEndElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XElement.ReadElementFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)
 
h4rl3qu1n said:
I downloaded the new package of oksehode and set it up as explained but i still get this error :/

[Rift Bot] Open Rift
[Rift Bot] Enter Rift
[GameUI] Clicking UI element Conversation Button (1178034176)
[Trinity] Clicking UI element Conversation Button (1178034176)
Failed to load profile: '<' is an unexpected token. The expected token is '>'. Line 109, position 3.
System.Xml.XmlException: '<' is an unexpected token. The expected token is '>'. Line 109, position 3.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(String expectedToken1, String expectedToken2)
at System.Xml.XmlTextReaderImpl.ParseEndElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XElement.ReadElementFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)
Click to expand...

Download again. I updated the zip file.
 
Oksehode said:
Here is a package I made to make this profile work amazing. It includes the released version of Demonbuddy and the recommended versions of the plugins needed to make it work almost flawless.
Demonbuddy-with-all-needed-profiles-and-plugins.zip

1. Unpack the zip to a folder of your choice.
2. Start Diablo and login to your account so you get to your character screen else you will get an error in Demonbuddy.
3. Start Demonbuddy.exe
4. Insert your key to login
5. Click on the "Plugins" tab and enable QuestTools, Trinity and RiftBot
6. Exit Demonbuddy
7. Delete the "CompiledAssemblies" folder inside your Demonbuddy folder
8. Start Demonbuddy.exe
9. Click on the arrow next to the "Settings" button and enable "Open Loot containers" and "Open Chests". Loot Radius 100/Kill Radius 80. Repair Durability to 25% to make it work correctly.
10. Choose your preferred difficulty under "Game Difficulty".
11. Save and Close.
12. Click on the "Plugins" tab. Click on "Trinity" then click the "Config" button.

Combat/Misc:
Trigger range for Elite Combat = 30
Trigger range for Trash Combat = 30
Minimum Trash Mob Pack Size = 1
Trash Pack Cluster Radius = 30
Disable"Force Kill Summoners"
Set Treasure Goblins to Kamikaze (Decrease this option if the bot tries to walk through walls and over cliffs to get to him)
Enable "Attempt to avoid AOE" and "Kite to Avoid Death on Low HP"
Disable "Path Around AOE", "Avoid Savage Beast Charge", Attack Mobs in AOE" and "Avoid Fire Chains"

Objects
Container Open Range = 30
Enable "Open Chests"

Advanced
"Enable Gold Inactivity" = 180

As for the rest of the settings in Trinity, set to your own preference. These settings help the bot do the rifts more smooth.

The profiles to use is inside the Profile folder.

Everything is updated for best performance with this profile.
Click to expand...


I got a question with these instructions. Do you re-enable the plugins (I'm guessing) after deleting Compiled ~ or just leave them unchecked. I'm a little unclear on that. And why would you re-check or delete the Complied folder if you're just going to re-enable them again? I'm just curious why that works or w/e
 
Last edited:
Bot does not go to next map, but circles over and over in the first map of rifts until gold inactivity triggered. Is there a solution to this?

L.E.: I saw there was an upgrade. Hope that solves the problem.
 
Last edited:
Qetyip said:
I got a question with these instructions. Do you re-enable the plugins (I'm guessing) after deleting Compiled ~ or just leave them unchecked. I'm a little unclear on that. And why would you re-check or delete the Complied folder if you're just going to re-enable them again? I'm just curious why that works or w/e
Click to expand...

You don't need to re-enable the plugins after you delete the compiled folder. When you enable the plugins the first time, they're enabled until you choose to disable them for whatever reason.

You must exit DemonBuddy before deleting the compiled folder.
 
Last edited:
Ended up with a problem that kept repeating on Diablo bounty:

Exception when terminating bot thread. System.NullReferenceException: Object reference not set to an instance of an object.
at Trinity.XmlTags.TrinityExploreDungeon.<>c__DisplayClass6.<GetIgnoredAreas>b__2(IgnoreScene igns)
at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
at Trinity.XmlTags.TrinityExploreDungeon.<GetIgnoredAreas>b__1(Scene scn)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Trinity.XmlTags.TrinityExploreDungeon.GetIgnoredAreas()
at Trinity.XmlTags.TrinityExploreDungeon.<get_IgnoredAreas>b__0()
at Zeta.Common.CachedValue`1..ctor(Func`1 retriever, TimeSpan cacheFor)
at Trinity.XmlTags.TrinityExploreDungeon.get_IgnoredAreas()
at Trinity.XmlTags.TrinityExploreDungeon.IsPositionInsideIgnoredScene(Vector3 position)
at Trinity.XmlTags.TrinityExploreDungeon.<CheckIgnoredScenes>b__b5(Object ret)
at Zeta.TreeSharp.Decorator.CanRun(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.Decorator..()
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.TreeSharp.DecoratorContinue..()
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.()
Click to expand...
 
Minseok said:
Ended up with a problem that kept repeating on Diablo bounty:
Click to expand...

I don't know how well this package work with bounties as the act 4 bounty profile is taken from the community bounty project and it is updated to run with Trinity .25 and this use Trinity .24. The rift profiles should work though.

Does it break the bot or is it working normally regardless of the error?
 
Well, it broke on the Diablo bounty. It ran the others and finished them. When I remade another game, it did it again on that same bounty.
 
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2137.19ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2161.88ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2162.29ms.
[Trinity][Performance] Execution of the block TargetCheck took 2383.36ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2138.53ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2162.92ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2163.39ms.
[Trinity][Performance] Execution of the block TargetCheck took 2412.84ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2114.36ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2141.01ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2141.59ms.
[Trinity][Performance] Execution of the block TargetCheck took 2381.38ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2090.90ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2116.07ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2116.53ms.
[Trinity][Performance] Execution of the block TargetCheck took 2120.73ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2083.46ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2108.78ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2109.28ms.
[Trinity][Performance] Execution of the block TargetCheck took 2113.42ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2143.72ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2168.24ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2168.66ms.
[Trinity][Performance] Execution of the block TargetCheck took 2172.71ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2173.47ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2197.38ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2197.78ms.
[Trinity][Performance] Execution of the block TargetCheck took 2201.81ms.
[SafeMoveTo] ReachedDestination!
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2189.67ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2214.35ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2214.88ms.
[Trinity][Performance] Execution of the block TargetCheck took 2219.02ms.
[SafeMoveTo] Initialized
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2201.01ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2226.67ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2227.23ms.
[Trinity][Performance] Execution of the block TargetCheck took 2231.40ms.






This message is because the profile or the db??
 
Birasl said:
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2137.19ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2161.88ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2162.29ms.
[Trinity][Performance] Execution of the block TargetCheck took 2383.36ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2138.53ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2162.92ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2163.39ms.
[Trinity][Performance] Execution of the block TargetCheck took 2412.84ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2114.36ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2141.01ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2141.59ms.
[Trinity][Performance] Execution of the block TargetCheck took 2381.38ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2090.90ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2116.07ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2116.53ms.
[Trinity][Performance] Execution of the block TargetCheck took 2120.73ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2083.46ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2108.78ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2109.28ms.
[Trinity][Performance] Execution of the block TargetCheck took 2113.42ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2143.72ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2168.24ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2168.66ms.
[Trinity][Performance] Execution of the block TargetCheck took 2172.71ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2173.47ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2197.38ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2197.78ms.
[Trinity][Performance] Execution of the block TargetCheck took 2201.81ms.
[SafeMoveTo] ReachedDestination!
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2189.67ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2214.35ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2214.88ms.
[Trinity][Performance] Execution of the block TargetCheck took 2219.02ms.
[SafeMoveTo] Initialized
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 2201.01ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 2226.67ms.
[Trinity][Performance] Execution of the block TargetCheck.RefreshCache took 2227.23ms.
[Trinity][Performance] Execution of the block TargetCheck took 2231.40ms.






This message is because the profile or the db??
Click to expand...

DB and Trinity. A restart of DB usually takes care of it.. It tends to happen on large maps.
 
Status
Not open for further replies.
Back
Top