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

Trinity 2.8.4 & QuestTools 3.4.16

Status
Not open for further replies.
is anyone having problems with monk. He just sits in packs of mobs sometimes and doesn't use dashing strike or anything?
 
[QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 21 nodes in 5ms
System.Exception: Запрос ReadProcessMemory или WriteProcessMemory был выполнен только частично, at addr: 00000040, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
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_IsUnidentified()
at Zeta.Game.Internals.Actors.ACDItem.get_Name()
at Zeta.Bot.ItemStatistics.(Object , ItemLootedEventArgs )
at Zeta.Bot.GameEvents.[](EventHandler`1 , Object ,  )


plus appear this error:

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Запрос ReadProcessMemory или WriteProcessMemory был выполнен только частично, at addr: 00000040, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
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_IsUnidentified()
at Zeta.Bot.Logic.BrainBehavior.<HandleIdentifyAllItems>b__1b8(ACDItem i)
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
at Zeta.Bot.Logic.BrainBehavior.<HandleIdentifyAllItems>d__1be.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Zeta.Bot.ActionRunCoroutine....()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
at Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
at Buddy.Coroutines.Coroutine.Resume()
at Zeta.Bot.ActionRunCoroutine.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.Coroutines.CoroutineCompositeExtensions..()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.DbProvider.TownRun.<TownRunCoroutineWrapper>d__4.MoveNext() in c:\Users\Kusha\Documents\Demonbuddy\Plugins\Trinity\DbProvider\TownRun.cs:line 255
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Zeta.Bot.ActionRunCoroutine....()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
at Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
at Buddy.Coroutines.Coroutine.Resume()
at Zeta.Bot.ActionRunCoroutine.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.()


Very often appear this error, even after new clearn install, any solutions ??View attachment 796 2015-05-07 21.17.txt
 
Last edited:
So where are all coders? Have they been ban by the buddy team cuz everyone is dead silence since some days ago. Weird if u ask me..
 
Can someone help me with this?
My wizard only use meteor if I have both blizzard and meteor in the cast bar. Is there any way to make it cast blizzard at least for the stacks of tal rasha?
 
So where are all coders? Have they been ban by the buddy team cuz everyone is dead silence since some days ago. Weird if u ask me..

My guess is that they are working on trinity, along with some integration of the upcoming DemonBuddy Store? :)

Atleast thats what comes to mind.
 
does anyone know how to make DH completey avoid arcane the avoidance seems to be fishy
 
My guess is that they are working on trinity, along with some integration of the upcoming DemonBuddy Store? :)

Atleast thats what comes to mind.
havent thought on this, but it is very likely what you say...damn!
 
My guess is that they are working on trinity, along with some integration of the upcoming DemonBuddy Store? :)

Atleast thats what comes to mind.
Wouldnt a heads up be a perfect time then? ;) Telling ppl whats up should benefit all? Then the time for it doesnt matter. atleast for me.
 
Sorry for asking, but since I'm modifying the files in my version, I can't use EZUpdater.

I have no idea if the initialization of the dh settings has been fixed in the current available version (the problem I'm talking about in my other thread). Is it already corrected?

I'm asking because after taking a look at the posts, several of them are precisely about that : the dh is not using the potions, the dh is not trying to pick up the globe healths, the dh is not kiting...

Basically, without it, the bot can hardly be used for the dh in grifts. It can still be used for T6 and rift farming though, when it's easy.

If it's not fixed yet and if you guys want to use the dh, then it's easily fixed by adding those missing lines in the file.
 
it seems when you get above 500 blood shards it stops picking them up

yes, because the old 500 shard limit code still in the script, but now you can get more than 500, easy fix, spend your shards..
 
yes, because the old 500 shard limit code still in the script, but now you can get more than 500, easy fix, spend your shards..
not an easy fix when you want to save 1000+ to spend on an alt....
 
Occasionally, in the process of operation in normal,Sometimes DB sudden crash.
Trinity version:LazyCache changes that should not effect DB running

Code:
08:24:42.456 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9618,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.457 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9641,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.457 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9664,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.458 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9687,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.458 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9710,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.458 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9733,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.459 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9756,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.459 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9779,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.460 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9802,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.460 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9825,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.461 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9848,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.461 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9871,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.462 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9894,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。
08:24:42.462 INFO  AssemblyLoader`1 Compiler Error: f:\DemonbuddyCN\Plugins\Trinity\Reference\Legendary.cs(9917,23) : warning CS0436: “f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中的类型“Trinity.Objects.Item”与“f:\DemonbuddyCN\CompiledAssemblies\Trinity_635668407019771372.dll”中导入的类型“Trinity.Objects.Item”冲突。请使用“f:\DemonbuddyCN\Plugins\Trinity\Objects\Item.cs”中定义的类型。

Full log file:View attachment 23216 2015-05-10 07.44.zip

Thanks!
 
thx! will give it a try, do we just download and replace the files or do we have to change all the 500 to our current max?
uhhh. this part calculates whatever your max is automatically.

MaxBloodShards = 500 + ZetaDia.Me.CommonData.GetAttributeOrDefault<int>(ActorAttributeType.HighestSoloRiftLevel) * 10;
 
@xzjv,

These 2 are missing from the item list. (might be more)

[Trinity] ------ New/Unknown Items 2 ------
[Trinity] Item: Mace: Mad Monarch's Scepter (271663)
[Trinity] Item: CrusaderShield: Salvation (299418)
 
Enchanting Favor is not in the list (or maybe I cannot find it), as well as the other follower items. Would be good to include them as I am always trying to max my follower as well.
 
Status
Not open for further replies.
Back
Top