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.
Still struggles with "The Cursed Hold" type rifts. Gets stuck around the edges, can't find portal if center and doesn't backtrack right.
 
Hellcom said:
Still struggles with "The Cursed Hold" type rifts. Gets stuck around the edges, can't find portal if center and doesn't backtrack right.
Click to expand...

We are working on that problem is there are 2 version of that map a "big" one and a "small" one both have the same LevelId and SceneId.. so figuring out which is which and then running a fix point script to "explore" the map is going to take a while.. takes a lot of testing to get it right got an idea how to tell the difference but it'll take a while to confirm that this method works and once that is done still gotta write the map specific scripts..
 
Another update:

CurrentLevelId: 353527
Map Name: X1_LR_Tileset_Aqueducts

Box-size: 12
Tolerance: 0.45

BPywtWN.png
 
Oksehode said:
Added.
Click to expand...

Code: 
<!-- Aquaducts--><LogMessage quest="1" step="2" output="[Rift Bot] Explore Crypts @ 12/30/0.45"/><TrinityExploreRift questId="337492" stepId="1" until="RiftComplete" markerDistance="45" boxSize="12" pathPrecision="30" boxTolerance="0.45"/><LoadProfile file="RiftCommon.xml"/>

please change the output to Aquaducts as well in both files to keep information display in demonbuddy as accurate as possible:)
 
Last edited:
Oksehode said:
Added.
Click to expand...

Latest rev with Trinity .26 is working pretty well for me. I know a lot of the issues with this project right now have to do with Trinity, but is there anything that we can do/any information we can pass along that would help you guys make the profile better/more efficient?
 
Bot just open rift go in and got this error :

Failed to load profile: '<' est un jeton inattendu. Le jeton attendu est '>'. Ligne 109, position 3.
System.Xml.XmlException: '<' est un jeton inattendu. Le jeton attendu est '>'. Ligne 109, position 3.
à System.Xml.XmlTextReaderImpl.Throw(Exception e)
à System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
à System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(String expectedToken1, String expectedToken2)
à System.Xml.XmlTextReaderImpl.ParseEndElement()
à System.Xml.XmlTextReaderImpl.ParseElementContent()
à System.Xml.XmlTextReaderImpl.Read()
à System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
à System.Xml.Linq.XElement.ReadElementFrom(XmlReader r, LoadOptions o)
à System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
à System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
à Zeta.Bot.Profile.Profile.Load(String path)
à Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)


bot just stay afk, i tried to fresh instal like 5-6 times always this shit.
 
Nask said:
Bot just open rift go in and got this error :

Failed to load profile: '<' est un jeton inattendu. Le jeton attendu est '>'. Ligne 109, position 3.
System.Xml.XmlException: '<' est un jeton inattendu. Le jeton attendu est '>'. Ligne 109, position 3.
à System.Xml.XmlTextReaderImpl.Throw(Exception e)
à System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
à System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(String expectedToken1, String expectedToken2)
à System.Xml.XmlTextReaderImpl.ParseEndElement()
à System.Xml.XmlTextReaderImpl.ParseElementContent()
à System.Xml.XmlTextReaderImpl.Read()
à System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
à System.Xml.Linq.XElement.ReadElementFrom(XmlReader r, LoadOptions o)
à System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
à System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
à Zeta.Bot.Profile.Profile.Load(String path)
à Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)


bot just stay afk, i tried to fresh instal like 5-6 times always this shit.
Click to expand...

Update to the latest revision of the profile. That's an old issue.
 
gotteshand said:
Code: 
<!-- Aquaducts--><LogMessage quest="1" step="2" output="[Rift Bot] Explore Crypts @ 12/30/0.45"/><TrinityExploreRift questId="337492" stepId="1" until="RiftComplete" markerDistance="45" boxSize="12" pathPrecision="30" boxTolerance="0.45"/><LoadProfile file="RiftCommon.xml"/>

please change the output to Aquaducts as well in both files to keep information display in demonbuddy as accurate as possible:)

There seems to be an issue were trinity and riftbot plugin fight over access to objects causing path-finding to completely kill itself when entering a rift. Not entirely sure if I'm getting it right but object already owned by another thread seems to be an access issue.. adding delays does not solve it.

Code: 
System.InvalidOperationException: Der aufrufende Thread kann nicht auf dieses Objekt zugreifen, da sich das Objekt im Besitz eines anderen Threads befindet.
   bei System.Windows.Threading.Dispatcher.VerifyAccess()
   bei System.Windows.Threading.DispatcherObject.VerifyAccess()
   bei System.Windows.Media.Visual.VerifyAPIReadWrite()
   bei System.Windows.Media.VisualCollection.Clear()
   bei Demonbuddy.TerrainVisualHost.ResetBackground()
   bei Demonbuddy.TerrainVisualHost.<.ctor>b__0(Object s, EventArgs e)
   bei Zeta.Bot.GameEvents.[](EventHandler`1 , Object ,  )
Click to expand...

Fixed the log message. :)
As for the other issue, I have to let DyingHymn take a look at that.
 
Oksehode said:
Fixed the log message. :)
As for the other issue, I have to let DyingHymn take a look at that.
Click to expand...

Thats with DB stable build I'll test now if that persists with DB beta build.. I'll let you guys know.

edit..

was caused by having had DB crash to many times:) ram got fucked up by that leaving old worker thread in there.. causing db to cash by entering box-size 1 into the mapviewer is not a good idea bad things can happen:)
But it seems that lateast DB beta runs a-lot better with .26 compared to the latest stable build.
 
Last edited:
_Steve_ said:
Latest rev with Trinity .26 is working pretty well for me. I know a lot of the issues with this project right now have to do with Trinity, but is there anything that we can do/any information we can pass along that would help you guys make the profile better/more efficient?
Click to expand...

Glad It's working for you and thank you for the support. You should PM DyingHymn and ask him what would help make this profile better. He's kinda the project guru, I'm just doing the small pathing tweaks (for now).

I don't know if anything other than a better exploration system would help this profile be perfect. The logic of the profile is pretty solid with the limitations of DB and its current features.
 
Oksehode said:
I changed the link to another provider. Shouldn't be any trojans in my package?
Click to expand...

Nope :) Nothing wrong with your package, it's very good. But anyone that fell for the speedyshare trap and installed downloader would be pretty fucked by now. Googled it beforehand it while the types of malware it installs varies it's between 4 and 7 programmes.
 
brilliant soo glad this is working once again ( scared to ever update now ) thanks u guys :D

@Oksehode kudos man ur back tracker is lookin sick does this currently only work on non beta ?
 
Hellcom said:
Nope :) Nothing wrong with your package, it's very good. But anyone that fell for the speedyshare trap and installed downloader would be pretty fucked by now. Googled it beforehand it while the types of malware it installs varies it's between 4 and 7 programmes.
Click to expand...

I did actually check beforehand if I could download the file without any fuzz and extra crap and I could. When people started to mention download managers and such things, I just changed the site which to upload to. I have however found a even better site to upload now, but I can't update post #2.
 
pajapo said:
brilliant soo glad this is working once again ( scared to ever update now ) thanks u guys :D

@Oksehode kudos man ur back tracker is lookin sick does this currently only work on non beta ?
Click to expand...

Thank you for the kind words. :)
I haven't tested it with the beta after Trinity .26 released, but It's working great on the non beta release except for some pathing issues here and there. Pandemonium Fortress (the one with the death gates) is a really troublesome map to tweak. Should be working relative ok with the other maps. Some backtracking is to be expected.
 
Still no response about my problem, anyone able to help me?

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.
 
Status
Not open for further replies.
Back
Top