Rift Bot - Yet Another Rifter!

As I said earlier, after trying for a couple of hours trinity .26 with QT .50, I reverted back to the package posted by Oksehode, and it runs better for me.

One problem that occurs sometimes tho, when in maps like act5 before Malthael, with all those teleporting portals, sometimes the bot won't recognize them and get stuck.
Any fix for this or I am the only one having this problem?

Thxn guys!!

 

I can't get this to run whatsoever. It keeps saying:

DemonbuddyBETA v1.1.1816.394 started
Logging in...
T: 5247025482629812527 H: 4221964419
Attached to Diablo III with pid: 4368
Flashing window
[Trinity] Initialized v1.8.26
[Rift Bot Plugin] RiftBot 0.0.8 Initialized.
[QuestTools] Plugin v1.5.50 Enabled
[Trinity] OnEnable start
Setting up Trinity Logging
[Trinity] ENABLED: Trinity v1.8.26 now in action!
[Rift Bot Plugin] RiftBot 0.0.8 Enabled.
Current bot set to Order Bot
Loaded profile Rift Bot Common
Chose Trinity as your combat routine
Loaded profile Rift Bot Common
Chose Trinity as your combat routine
[Trinity] Bot Starting
Loaded profile Rift Bot Common
GameChanged. Clearing actors
[Trinity] New Game - resetting everything
ProfileOrderManager.OnGameJoined, Reloading profile.
Loaded profile Rift Bot Common
Game joined, Resetting profile caches.
[Trinity] Starting up Generic Cache Manage thread
[Trinity] Starting up Generic Blacklist Manager thread
Stopping the bot. Reason:Failed to locate profile.
Session lasted for: 00:00:01.4832376
Chose Trinity as your combat routine
Bot Thread Ended. Was this requested?


I could not get it to work on my original DB Install, so I have just now tried an entirely Fresh Install. Still not working...

Before today it had been working fine, but I went ahead and updated to the new stuff....now it's not working.

 

That's more of and box-size / tolerance issue it seems sometimes move nodes are outside whats reachable so he keeps trying to reach that which causes the explorer to not recognize the portal.. finding the ideal box-size / tolerance for Fortress is really really tricky because sometimes one combo works then you get a different version and then again it doesn't I'm right now testing with box-size 9 and tolerance 0.48 lets see how that works out. Box-placement/path-finding looked a lot better with it but then again that does not mean anything yet.

Maps Like Pandemonium Fortress have always been 'tricky' no matter which version you use..

 

Keep getting

System.Exception: Element RiftAtStep is not supported. Please check your XML and try again. (<RiftAtStep step="1">
<WaitTimer questId="1" stepId="1" waitTime="1500" />
<MoveToMapMarker questId="312429" stepId="2" exitNameHash="1938876094" interactRange="15" destinationWorldId="288685" />
<MoveToMapMarker questId="312429" stepId="2" exitNameHash="1938876094" destinationWorldId="288685" />
<WaitTimer questId="312429" stepId="2" waitTime="1000" />
<LoadProfile file="ExploreCommon.xml" />
</RiftAtStep>) Line 41
at ..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..
(XElement , Type )
at ..
.
(XElement )
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 ..
(XElement , PropertyInfo )
at ..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

 

You are missing the riftbot plugin. You still need that even with trinity .26!

 

I keep getting:

Loaded profile Rift Bot Explore
Game joined, Resetting profile caches.
[Trinity] Starting up Generic Cache Manage thread
[Trinity] Starting up Generic Blacklist Manager thread
[Trinity] Clicking UI element Conversation Button (150523904)
Stopping the bot. Reason:Failed to locate profile.
Session lasted for: 00:00:26.3950799
Chose Trinity as your combat routine
Bot Thread Ended. Was this requested?

It talkes to Tyrael.. i dont know if thats intended?

 

Where can I download the riftbot plugin..?

 

It's on the first page. Scroll down a little. It's archived with Trinity and quest tools.

 

This seems to work with trinity 24 and act 4 thanks

 

Still can't get past the:

" Stopping the bot. Reason:Failed to locate profile."

Have tried 3 fresh installs, reboots in between installs as well.

 

Bot gets alot of stucks on Pandemonium Fortress maps. I wish i could help more in this project, unfortunately I don't know how.

 

Dont know if anyone else had this. But when I d/led the complete package, I got a trojan in my PC. so watch out. (i am 100% sure i only d/led that and nothing else on my PC).

 

LOL, a trojan from an XML/text file?
Funny guy here

 

Just made a completely fresh install, new settings, trin.26 and all and just, wow! This is better, this is good!

 

how about learn to read.... the previous download link they had was having an .exe file in it which installed everything. The installer also had some rubbish in it that you had to Agree on, that is where I got screwed. Anyways I removed the trojan with malwarebytes.

 

Thnx a lot for the explanation and all the work on this awesome profile

 

http://www.thebuddyforum.com/demonb...ial-fix-performance-problems-took-xxx-ms.html

 

error does not move the character from the beginning of the dungeon

 

DyingHymn,

there might be a way to tell the difference between the "big" and "small" version of The Cursed Hold (Warden)..

By using the coordinates and ActorExistsAt.. Both versions spawn their entrance at different coordinates.. the "big" version is <If condition="ActorExistsAt(176000, 303.0258, 1320.288, 1.596355, 10)">
Now gotta do the same for the small one then run into these maps multiple times to confirm that coordinates are always the same and then well we have a way to tell the difference


Also 4 different Pandemonium Fortress rift design runs no stuck smooth completion at [Rift Bot] Explore Pandemonium Fortress @ 9/15/0.55 settings and another thing for Pandemonium to explore properly we need to reduce combat range to a a minimum it helps a lot with stuck issues allot of the stuck comes from bot trying to fight shit he can't reach.. combat radius of around 15 or so should be good we wont need much more on that narrow map anyway not like it has tons of mobs to begin with.

 

Too much instability with EU servers atm..
I get to around 50-80% done in a rift and gets random DC's...