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

Trinity 1.8.26 Feedback

Status
Not open for further replies.
Last I tried it everything is working superbly other than not picking up legendaries, but I highly doubt in the 3 minutes between my post and yours that the issue has been fixed.
 
Last I tried it everything is working superbly other than not picking up legendaries, but I highly doubt in the 3 minutes between my post and yours that the issue has been fixed.

oh didn't notice time diff. XD
 
Does anyone have a changelog?

Im sure rrrix will post all that as he always does, when he does an official release thread and locks .25 thread. This thread was started by a user, not rrrix.
 
Im sure rrrix will post all that as he always does, when he does an official release thread and locks .25 thread. This thread was started by a user, not rrrix.

Here's the changelog. It's openly available in the other thread, but the user who started this misled people (unknowingly) by naming his thread like this. Would be a good idea to change the title...

Fixed killing corrupt growths in A4
Fixed picking up gold
TrinityExploreDungeon should be better about completing the final rift level when using RiftComplete (e.g. fixes R-Rift profile problem)
Trinity will no longer try to pickup items in Town when Vendoring
Removed CollisionSphere cache
Removed bunch of static cache variables
Refactored & Simplified how Position, Distance and Radius are calculated and used for all objects
 
Not picking up legendary s is bad. Is this a real Issue? i would think more people would be spamming this.
 
Not picking up legendary s is bad. Is this a real Issue? i would think more people would be spamming this.

I haven't seen any issues picking up legendaries, I watched it until a leg dropped and it picked it up for me. I also got a Won Khim Lau while doing keywardens. :D
 
I haven't seen any issues picking up legendaries, I watched it until a leg dropped and it picked it up for me. I also got a Won Khim Lau while doing keywardens. :D

Thank you
 
After the first one I just went back to release with .24 cause I can't watch it all day, later though I'll do a clean install and see if that resolves it for me :) glad to see maybe it's just a couple isolated events!

*Edit* Clean install of trinity fixed it for me, I should have done that to begin with :P
 
Last edited:
Awesome work on the plugin indeed. I would like to request support for Magic Missile/Wave of Force Fire build if possible.

Thanks.
 
Picking up Gold works fine now, but it still doesn't picking up legendary crafting materials...
 
My first post on forums please bear with me. DB version .394 and Trinity .25 currently being run. I changed the Legendaries option to 1+ and it picks up all these crafting mats, I have had no issues once making that change to Trinity options. Hope it helps.
 
I'm very sorry for my english.

Often encounter such exceptions, including Trinity .24/.26 and latest RiftBot profile.
Please help me, or tell me the cause of this anomaly by Trinity or RiftBot? This problem has been bothering me.:(
The following code is only part often is that once an exception occurs, a large section of abnormal continuous succession broke out.
Sometimes BOT will continue to run, and sometimes directly BOT died, stopped.

Thanks very much!

Code:
[Trinity] Error while refreshing DiaObject ActorSNO: 219613 Name: a4dun_Spire_CorruptionGeyser-32042 Type: Monster Distance: 14 
[Trinity] System.Exception: 仅完成部分的 ReadProcessMemory 或 WriteProcessMemory 请求。, at addr: 00000000, Size: 760
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.ACD.()
   at Zeta.Game.Internals.Actors.ACD.get_ACDGuid()
   at Trinity.Trinity.RefreshStepCachedObjectType(Boolean AddToCache)
   at Trinity.Trinity.CacheDiaObject(DiaObject freshObject)
   at Trinity.Trinity.RefreshCacheMainLoop()
[Trinity] Error while refreshing DiaObject ActorSNO: 219613 Name: a4dun_Spire_CorruptionGeyser-32042 Type: Monster Distance: 14 
[Trinity] System.Exception: 仅完成部分的 ReadProcessMemory 或 WriteProcessMemory 请求。, at addr: 00000000, Size: 760
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.ACD.()
   at Zeta.Game.Internals.Actors.ACD.get_ACDGuid()
   at Trinity.Trinity.RefreshStepCachedObjectType(Boolean AddToCache)
   at Trinity.Trinity.CacheDiaObject(DiaObject freshObject)
   at Trinity.Trinity.RefreshCacheMainLoop()
[Trinity] Error while refreshing DiaObject ActorSNO: 219613 Name: a4dun_Spire_CorruptionGeyser-32042 Type: Monster Distance: 19 
[Trinity] System.Exception: 仅完成部分的 ReadProcessMemory 或 WriteProcessMemory 请求。, at addr: 00000000, Size: 760
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.ACD.()
   at Zeta.Game.Internals.Actors.ACD.get_ACDGuid()
   at Trinity.Trinity.RefreshStepCachedObjectType(Boolean AddToCache)
   at Trinity.Trinity.CacheDiaObject(DiaObject freshObject)
   at Trinity.Trinity.RefreshCacheMainLoop()
 
dont know if this is DB or trinity problem.

fresh install of .393 & .26

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000198, Size: 12
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_Position()
at Zeta.Bot.InactivityDetector.(Object , EventArgs )
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Delegate.DynamicInvoke(Object[] args)
at Zeta.Bot.Pulsator.(Delegate , Object[] )
 
After the upgrade it seems that i don't have the issue of legendary picking at all.
The only thing i have noticed is that the runs are significantly slower
Profile i'm using: http://www.thebuddyforum.com/demonb...-3/155638-legendaryz-adventure-core-azmo.html

Sadly the remote tool i'm using does not allow me to extract the logs at them moment :( but i notice that the bot stops for ~30 secs to 1 min right before Azmodan and about the same amount of time after selling/salvaging when townrun is finished
 
.26 still have Legendary issues? i think i will wait for a Official Release
 
.26 still have Legendary issues? i think i will wait for a Official Release

If you delete your Trinity folder and install it fresh it picks up legendaries fine, at least that's what fixed it for me.

*edit* damn phone thought we had hungry folders!
 
Last edited:
the corruped growth is fixed but tooooooo much priority.
I have had him quit fighting an elite to go destroy one.
 
Status
Not open for further replies.
Back
Top