R-Rift - rrrix's BETA Rifts
- Thread starter rrrix
- Start date
beta 515
You have to manually update trinity (2.6.1) . Just download it from here https://www.assembla.com/code/unifiedtrinity/git/nodes
EZUpdater wasnt working for me (kept downloading 2.5.1)
You have to manually update trinity (2.6.1) . Just download it from here https://www.assembla.com/code/unifiedtrinity/git/nodes
EZUpdater wasnt working for me (kept downloading 2.5.1)
Alright installed 2.5.1, it can get in the game. but despite doing the quest tools delete to leave normal rifting only. it still tried to pull a grift key to use out of stash. fluke or is there more to it?
edit - as a matter of fact, deleting the trial and greater rift parts from the QT .xml throws up errors now on loading, cant even start bot.
edit - as a matter of fact, deleting the trial and greater rift parts from the QT .xml throws up errors now on loading, cant even start bot.
Code:
Error while starting botSystem.TypeInitializationException: The type initializer for 'QuestTools.Helpers.BotBehaviorQueue' threw an exception. ---> System.Xml.XmlException: Invalid character in the given encoding. Line 39, position 29.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.InvalidCharRecovery(Int32& bytesCount, Int32& charsCount)
at System.Xml.XmlTextReaderImpl.GetChars(Int32 maxCharsCount)
at System.Xml.XmlTextReaderImpl.ReadData()
at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
at System.Xml.XmlTextReaderImpl.FinishPartialValue()
at System.Xml.XmlTextReaderImpl.get_Value()
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.Common.Xml.XmlSettings..ctor(String path)
at QuestTools.QuestToolsSettings..ctor() in c:\Users\Ben\Desktop\Games\D3\testfor2.2.0\DemonbuddyBETA 515\Plugins\QuestTools\QuestToolsSettings.cs:line 60
at QuestTools.QuestToolsSettings.get_Instance() in c:\Users\Ben\Desktop\Games\D3\testfor2.2.0\DemonbuddyBETA 515\Plugins\QuestTools\QuestToolsSettings.cs:line 83
at QuestTools.Logger.Debug(String message) in c:\Users\Ben\Desktop\Games\D3\testfor2.2.0\DemonbuddyBETA 515\Plugins\QuestTools\Helpers\Logger.cs:line 185
at QuestTools.Helpers.BotBehaviorQueue.InsertHooks() in c:\Users\Ben\Desktop\Games\D3\testfor2.2.0\DemonbuddyBETA 515\Plugins\QuestTools\Helpers\BotBehaviorQueue.cs:line 467
at QuestTools.Helpers.BotBehaviorQueue..cctor() in c:\Users\Ben\Desktop\Games\D3\testfor2.2.0\DemonbuddyBETA 515\Plugins\QuestTools\Helpers\BotBehaviorQueue.cs:line 40
--- End of inner exception stack trace ---
at QuestTools.Helpers.BotBehaviorQueue.OnHooksClearedHandler(Object sender, EventArgs eventArgs)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Zeta.Common.TreeHooks.ClearAll()
at Zeta.Bot.Logic.OrderBot.Start()
at Zeta.Bot.BotMain.Start()
at Demonbuddy.MainWindow.HandleStartStopBot()
Last edited:
got the old riftbot rev 468 running just fine, r-rift wouldn't work with any of the changes put in here unfortunately =/ Now I just wonder if I can get kadala up and running, or if xjvz will release one with a higher cap, will be nice being able to hold onto 500-700 bshards to gamble on other chars
Try the stable build 401, quest tools 3.3.1 and trinity 2.6.1, not 2.5.1
I am using 2.6.1 my bad typo, that solved the click on start crash error. However my bot just did a town run and boop crash entirely. That was set to do RG and repeat, something to do with town rune, the error log didn't really say what caused it I watched it happen all it did was ID my items, and before it could stash them it crashed. Think I will keep my bot on rift bot full explore for now...more items, less shards though. and considering the state of bounties(not sure if they are still working, heard some moved/changed so might've broke profile?) I farmed just over 1700 fragments 3 weeks ago on raekor barb had i known shard cap was gonna be in the easy 900s i would have farmed more so my bot could farm RG rinse repeat to save up 700ish shards then i could swap chars to gamble.
my QT is 3.3.10, i assume thats same as the one you mentioned 3.3.1 or is it a diff version? right now i got normal rifts running fine, hopefully i can use this until shit is sorted and fixed in a few days so people dont have to ghetto rig and deal with constant crashes. Desperately need to run a ton of trial runs on bot, then rank up 2 gems which i alway used r-rift for but doesn't work for me atm.
my QT is 3.3.10, i assume thats same as the one you mentioned 3.3.1 or is it a diff version? right now i got normal rifts running fine, hopefully i can use this until shit is sorted and fixed in a few days so people dont have to ghetto rig and deal with constant crashes. Desperately need to run a ton of trial runs on bot, then rank up 2 gems which i alway used r-rift for but doesn't work for me atm.
rrrix
New Member
- Joined
- Jul 11, 2010
- Messages
- 3,449
- Reaction score
- 61
Trinity 2.6.1 is very experimental and is not fully supported yet. If you are using it, regularly update (like, every few hours or so) from git to get the latest fixes. There's still lots of stuff that does NOT work.
Dest226juan
New Member
- Joined
- Sep 7, 2014
- Messages
- 3
- Reaction score
- 0
Yo ive been getting this thing where i set normal rifts as higher priority but it keeps doing trials whats that about?
Dest226juan
New Member
- Joined
- Sep 7, 2014
- Messages
- 3
- Reaction score
- 0
Also is there a way you can add in a option for it to not do greater rifts its so annoying to take off all the keys and put on another character
hey thanks for all the work and help getting it up and running after a major patch. I have yet to search for it, but I was curious, if anyone knows you would be the person.
There is an error for when the bot leaves a game to create a new game, and it DB tosses out a single memory read error and bot just stops entirely until manual restart. Is this a quest tools issue or whats the cause of it? People have claimed reverting to older QT versions, or mix n matching fixed it. So thats why I ask, because if that was a fix I would have assumed that the trinity 2.6.1 and QT 3.3.10 im using would have prevented anymore new game errors.
+1 on this
the old bug/error "[Trinity] Error in HandleTarget: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 416" is also back again since we have to use latest db/trinity/qt :'(
Phantomzoner
New Member
- Joined
- May 10, 2014
- Messages
- 21
- Reaction score
- 0
thxx! so far so good. works with armory for kadala too
anyone have the kadala plugin since it works? the download is disabled
you can use the other rift bot to do that, full clears til it finds the stone back to town. ive been doing that but theres something wrong with latest version of db/trinity/qt prolly the profile too. it can run for 2 hours just fine, or the bot can stop 15 times in 30 minutes randomly because of an error if u get certain maps. rev498 of the rift bot fixed the warden jail map that pathed back n forth n eventually timed out but it never stopped the bot. I am thinking of rerolling back to 467 to see how it runs, even if the bot hangs on jailer warden map as long as it killed the RG im fine with inactivity timer kicking in. it will mean my bot keeps running nonstop and not stopping because of this error: