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

QuestTools 3.3.2: Trial Rifts: Disable Combat At Wave not functional?

B

BitteEinBot

New Member
Joined
Mar 10, 2014
Messages
60
Reaction score
1
Hi friends,

Anyone having the same problem with the bot not stopping past a certain wave you specified? My character isn't capable of doing the rift levels it's getting in the trials :p I'm doing the trials manually at the moment so it's not a big deal, just wondering if it's just me.

It's on a clean db install, trinity 2.4.1, questtools 3.3.2, R-Rift downloaded through EZUpdater.
 
Try resetting everything. You know its not based on the actual level reached but the amount of waves completed?

Demonbuddy needs to be reset in order for that specific setting to take effect.
 
Last edited:
CaptainAmerica said:
Try resetting everything. You know its not based on the actual level reached but the amount of waves completed?

Demonbuddy needs to be reset in order for that specific setting to take effect.
Click to expand...

Yes I set it to 7 but it's completing ~10 waves. I'm reinstalling it once again. I'll report back.
 
Yes, it's not working - everyone's reported the same thing. I'll dig into it soon.

blame xzjv (he is the one who actually originally built it, and he broke it :))
 
rrrix said:
Yes, it's not working - everyone's reported the same thing. I'll dig into it soon.

blame xzjv (he is the one who actually originally built it, and he broke it :))
Click to expand...

It has been working for me but if you're fixing it is there any chance you could also add a way to limit the bot from opening rifts that are too high. So annoying when it gets one it goes into a rift it cant handle.
 
CaptainAmerica said:
It has been working for me but if you're fixing it is there any chance you could also add a way to limit the bot from opening rifts that are too high. So annoying when it gets one it goes into a rift it cant handle.
Click to expand...

It worked for me for a bit, and it's borked again randomly.
 
hydrogenman said:
It worked for me for a bit, and it's borked again randomly.
Click to expand...

I noticed that also. It runs smoothly for a long time then something errors out and it stops working. I going through the error log now to try and track it down. Rifting bot in general has trouble starting up again when you pause and skip over a step. Say you hand in the quest.
 
i put // before setcombatallow(false) in line 78, works fine for me . but it would be nice if rrrix can look into it..
 
seems to work fine if you didn't do any greater rifts before attempting trials, once a grift is done it appears to bug out for me.
 
Found the only error that happened right before it started to do max amount of waves.(Not listening to the setting)

Code: 
ERROR GameEvents System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: FF000000, Size: 12
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.FastAttribGroupsEntry..()
   at Zeta.Game.Internals.FastAttribGroupsEntry..()
   at Zeta.Game.Internals.FastAttribGroupsEntry.[](Int32 , ACD )
   at Zeta.Game.Internals.Actors.ACD.GetAttribute[T](Int32 attribute)
   at Zeta.Game.Internals.Actors.ACD.GetAttribute[T](ActorAttributeType attributeType)
   at Zeta.Game.Internals.Actors.ACDItem.get_ItemQualityLevel()
   at Trinity.Helpers.DebugUtil.<LogBuildAndItems>b__11(ACDItem i) in DBLOCATION\Db\Plugins\Trinity\Helpers\DebugUtil.cs:line 93
   at System.Linq.Enumerable.WhereListIterator`1.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Trinity.Helpers.DebugUtil.LogBuildAndItems(TrinityLogLevel level) in DBLOCATION\Db\Plugins\Trinity\Helpers\DebugUtil.cs:line 93
   at Trinity.Trinity.TrinityOnJoinGame(Object src, EventArgs mea) in DBLOCATION\Db\Plugins\Trinity\Helpers\GameEvents.cs:line 172
   at Zeta.Bot.GameEvents.[](EventHandler`1 , Object ,  )
 
all work. set wave 6, you will get 23-25 keys. disable ouesttools, enable it.
 
Last edited:
I was wondering why it wasnt working until i saw that i have limit to 6-7 waves and now its working for me thanks!
 
You must log in or register to reply here.
Back
Top