Rifter - A Bot for Rifts!

Sometimes the bot went through, hand in the quest and then gets stuck with this error, someone got a solution?

[Trinity] Loading new profile.
Failed to load profile: Path to profile element is not valid; file not found
System.IO.FileNotFoundException: Path to profile element is not valid; file not found
Dateiname: 'Z:\Demonbuddy\Profiles\Rifter Extended.xml'
bei Zeta.Bot.Profile.Profile.Load(String path)
bei Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

 

still the problem after killing rift guardian, the bot keeps exploring till he finds the town stone and then: (i noticed that often as he kills another rare mob with the rift guardian!)

--------------------WARNING--------------------
Found town stone but still haven't killed boss.
-Leaving game in 15 seconds, stop if you want.-
--------------------WARNING--------------------

possible to add a check for boodshards and after detection use tp?

 

Im glad you and meet made up, seriously mad respect for both of you that takes maturity

Anyway been using this profile here and there tracking its progress, coming along really nicely considering I thought rifts were untouchable by DB

 

Hello, as soon as the bot opened the portal and get into the rift it just stands there and i'm getting this message from DB "[Trinity] Active bounty returned null, Assuming done. [Trinity] Bounty is done. Tag Finished." I was wondering if there is any setting that I need to turn on or off. Thanks!

 

@Changes1 delete your bounty.cs file in trinity plugin and see if that works.

 

That was the problem with trinity .19 I guess, you should update to .20

 

Is that right? But everytime I do the update using EZ updater or even downloading it manually in the Plugins tab of DB, Trinity is not there for some reason but Quest tool and EZ Updater is there and they are fully updated so I had to delete all the files and do a fresh folder for DB Beta and stuffs for it to pop out again I need some serious help damn I so wanted to use this profile.

 

There is a bug with trinity .20. Head over to the Trinity forum for the manual fix (for now).

 

SVN 63 caused this to happen, just a heads up.


System.Exception: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor questId="312429" stepId="2" x="594" y="508" z="3" actorId="364715" interactRange="11" name="x1_OpenWorld_LootRunObelisk_B-596" pathPrecision="5" pathPointLimit="250" statusText="Moving to Nephalem Obelisk" isPortal="True" />) Line 39
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)
Failed to load profile: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor questId="312429" stepId="2" x="594" y="508" z="3" actorId="364715" interactRange="11" name="x1_OpenWorld_LootRunObelisk_B-596" pathPrecision="5" pathPointLimit="250" statusText="Moving to Nephalem Obelisk" isPortal="True" />) Line 39
System.Exception: Element MoveToActor is not supported. Please check your XML and try again. (<MoveToActor questId="312429" stepId="2" x="594" y="508" z="3" actorId="364715" interactRange="11" name="x1_OpenWorld_LootRunObelisk_B-596" pathPrecision="5" pathPointLimit="250" statusText="Moving to Nephalem Obelisk" isPortal="True" />) Line 39
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)

 

as i said there is something wrong - it happen really often - that when bot kill rift boss that are on the list they still explore and end with notification about no rift boss found - i think its only connected to bosses that arent on profile list but not... something wrong witch checking even if i add bloodshard it didnt help

 

Yepp. I've wrote few pages before about it.

 

The bot gets stuck at "rubble" in many ROS maps, he doesn´t destroy it he just keeps walking back and forth towards it...Anyone have any idea how to fix it? Setting up in trinity to destroy objects makes it destroy everything, can someone tell me how to make it just destroy those items? :S

 

I'm having an issue with this not exploring levels enough. It bee lines for end level portals/stones and if the rift boss hasnt spawned by then it sits in town trying to close the rift untll it eventually goes back into the portal thinking that a new rift was opening, then it walks through the already explored areas again all the way to the end of the level once again. Gets stuck looping like this.

 

I've run into this issue as well. The failsafe for the failsafe needs another failsafe Basically when it finds the 'end of rift' stone it goes back to try and close the rift just in case the boss was killed but not detected. The problem is after this happens the game needs to be restarted because in the event that the boss WASN'T killed it tries to close it, then starts all over and runs loops through an already cleared rift. So maybe a "Found end of stone, TP to town to try and close, wait 20, restart game" type of thing at the end instead of just "TP to town, talk to end guy, restart script"

 

Is the bot suppose to open every weapon rack he comes over? Does every weapon rack have it's own actorId? If so, it would take forever to blacklist all of them.

 

I've noticed the bot has been skipping a LOT of mobs. Even when they are 4-5 in a group, it runs past them. Reason? Trinity setting?

 

<!-- Finishing Rift -->
<If condition="Me.IsInTown ">
<MoveToActor questId="312429" stepId="2" x="588" y="518" z="3" actorId="363744" interactRange="9" name="X1_LR_Nephalem-14254" pathPrecision="5" pathPointLimit="250" statusText="Completing Rift" />
<WaitTimer questId="1" stepId="1" waitTime="35000" />
<!-- Reload Profile? -->
<If condition="not ActorExistsAt(364715, ZetaDia.Me.Position.X, ZetaDia.Me.Position.Y, ZetaDia.Me.Position.Z, 100)">
<LeaveGame reason="Faild to do quest and finish rift." />
</If>
<If condition="ActorExistsAt(345935, ZetaDia.Me.Position.X, ZetaDia.Me.Position.Y, ZetaDia.Me.Position.Z, 100)">
<LeaveGame reason="Faild to do quest and finish rift." />
</If>
<TrinityLoadProfile nodelay="True" file="Put Name Here.xml" />
</If>

 

[Trinity] Active bounty returned null, Assuming done.
[Trinity] Bounty is done. Tag Finished.
[Trinity] TrinityTownPortal started - clearing area, waitTime=-1, startHealth=454322
[Trinity] Town Portal timer finished


while rift is at 96% finished :S

 

I just want to post a big thanks to NWL of course for the work to create this. I'm sure it's going to be polished and everyone will run it consistently pretty soon.

I just started working with the routine today (Core), with a fresh dB install, all up to date on quest, trinity and rift current revision.

First rift I got lucky (or perhaps unlucky) and door to next level was literally 20 meters to the right of the entrance (small act 5 graveyard map).

The bot went approx. 4 levels deep, not exploring past finding next level before proceeding deeper, and eventually hit town stone at approx. 50%, reported boss unkilled, left game.

I was going to switch to extended, but will that continue as soon as door is found? or attempt to clear entire level prior to finding door?

All of that being said, I guess as long as its afkable, spending stones, to kill in an area with 100% increased leg chance, even if its not full clearing and/or occasionally missing guardian, you are doing better than being outside of a rift.

Thanks again of course.

 

Loaded profile Rifter - A Bot for Rifts!
Game joined, Resetting profile caches.
[Trinity] Starting up Generic Cache Manage thread
[Trinity] Starting up Generic Blacklist Manager thread
ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80
[Trinity] Clicking UI element Conversation Button (768962560)
[Trinity] Active bounty returned null, Assuming done.
[Trinity] Bounty is done. Tag Finished.
[Trinity] Clicking UI element Conversation Button (768962560)

Opens rift, kills mobs it ported in on, and then it just sits and spams this.. sigh