What's new
  • 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!

Siege Camp Chest Runner v2.1 100% Workable with DB release v1.1 r1898 Build 362.

Get this every 3rd or 4th game...

22:34:40.122 DEBUG TrinityDebug [Trinity] Error in getting LoopingAnimationEndTime Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 6361626B, Size: 12
22:34:40.386 ERROR Pulsator 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: 00000043, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.FastAttribGroupsEntry.GetAttribute[T](Int32 attribute)
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_Gold()
at Zeta.Game.Internals.Actors.ACDItem.get_ItemStackQuantity()
at Zeta.Game.Internals.Actors.DiaActivePlayer.InventoryManager.get_Coinage()
at Zeta.Bot.GameStats.(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[] )

Did you download the Trinity version I provided or get yours from somewhere else?
 
FYI everyone, if you're willing to take the risk, you can add the line:

<UsePower questId="1" powerId="00000" />

after the line:

<!-- Using TownPortal -->

near the very end, to utilize the instant leave function. It may increase your risk of being banned (as this exploit can only be accomplished by violating the terms of service for Diablo), but I think that discretion should be up to the end user and not just the devs (whom I thank for making such an excellent profile).

Cheers
 
FYI everyone, if you're willing to take the risk, you can add the line:

<UsePower questId="1" powerId="00000" />

after the line:

<!-- Using TownPortal -->

near the very end, to utilize the instant leave function. It may increase your risk of being banned (as this exploit can only be accomplished by violating the terms of service for Diablo), but I think that discretion should be up to the end user and not just the devs (whom I thank for making such an excellent profile).

Cheers

As I said before, I do not endorse this because of its' known risk as did the original Authors.
Deliberately risking unwanted attention to DB is risking DB getting shut down.
 
Last edited:
when i try get Trinity i get this : Invalid Attachment specified. If you followed a valid link, please notify the administrator.
 
from what i understand from a blue post the 100% buff doesnt apply to chests, even tho the 1st 24 hours it seemed to, i think they ninja nerfed it, so if any one is getting more then 5-6 per hour would love to see current charts

It sure did for a bit, i wonder if they did ninja nerf it, because im getting zero legs now when i was getting 5+
 
As I said before, I do not endorse this because of its' known risk as did the original Authors.
Deliberately risking unwanted attention to DB is how we end up getting shut down.

same here bossen2750!

help us Malkadore! =)
 
when i try get Trinity i get this : Invalid Attachment specified. If you followed a valid link, please notify the administrator.

I just checked all attachments and they are in working order.

You may have tried downloading Trinity as I was updating it to the page. Try downloading it again.
 
Last edited:
It sure did for a bit, i wonder if they did ninja nerf it, because im getting zero legs now when i was getting 5+

Working on a crappy laptop, I'm averaging 40 games an hour and still getting 2-3 legs and hour.
I've done my own tests concerning MF / without MF and I seem to have better drop rates with MF gear on, DESPITE what has been documented in blue on the Blizz forums. If it is true that MF doesn't affect chests, then it wouldn't hurt you any to wear some because of the small percentage of corpses and stones you hit with this profile ;)
 
Good to know its still working, RNG gods must be laughing at by barb
 
Mine keep restart the game with the following error:-

System.Exception: Injection resulted in a process exception with error code 0xc0000005
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at GreyMagic.Executor.Execute()
at ..(Executor , String )
at Zeta.Game.Internals.SNO.TagMap.GetTagMapEntryAsInteger(Int32 key)
at Zeta.Game.Internals.SNO.SNORecordActor.get_GizmoType()
at Zeta.Bot.Navigation.MainGridProvider.(DiaObject )
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at Zeta.Bot.Navigation.MainGridProvider.(BitArray )
at Zeta.Bot.Navigation.MainGridProvider.Update()
at Trinity.Trinity.GameEvents_OnGameChanged(Object sender, EventArgs e) in c:\Chest Run 362\Plugins\Trinity\Helpers\GameEvents.cs:line 117
at Zeta.Bot.GameEvents.[](EventHandler`1 , Object , )

Please uninstall DB, delete the DB folder and start over with the new Trinity 1.8.281 I've uploaded.
 
Yaahhhh, It's working again :-)


Big THANX to Malkadore for fast reponse and nice Work, I think I love you ;)
 
It sure did for a bit, i wonder if they did ninja nerf it, because im getting zero legs now when i was getting 5+

i just leave this here (keep in mind the low gph since i use the take a break plugin to take some breaks every 25-45 games):
Code:
===== Misc Statistics =====
Total tracking time: 7h 8m 6s
Total deaths: 0 [0 per hour]
Total games (approx): 342 [47,93 per hour]
Total XP gained: 0,01 million [0 million per hour]
Total Gold gained: 10205,66 Thousand [1430,35 Thousand per hour]

===== Item DROP Statistics =====
Items:
Total items dropped: 1196 [167,62 per hour]
Items dropped by ilvl: 

Items dropped by quality: 
- White: 20 [2,8 per hour] {1,67 %}
- Magic: 1023 [143,38 per hour] {85,54 %}
- Rare: 117 [16,4 per hour] {9,78 %}
- Legendary: 36 [5,05 per hour] {3,01 %}

Gem Drops:
Total gems: 116 [16,26 per hour]
- Ruby: 22 [3,08 per hour] {18,97 %}
- Topaz: 26 [3,64 per hour] {22,41 %}
- Amethyst: 29 [4,06 per hour] {25 %}
- Emerald: 18 [2,52 per hour] {15,52 %}


===== Item PICKUP Statistics =====
Items:
Total items picked up: 36 [5,05 per hour]
Item picked up by ilvl: 

Items picked up by quality: 
- Legendary: 36 [5,05 per hour] {100 %}
 
Sometimes will still stuck at the second chest, when I use Steed Charge

That's a known issue with CA's pathing when trying to retrieve an item from behind the 2nd chest. It doesn't happen often but when it does, it should correct itself within 10 attempts or restart the game. I might have a look at tweaking this tomorrow.
 
Is this supposed to be opening 2 chests, and remaking game? Just want to make sure my bot isn't missing something?

Oh oops, that game had 3 chests. Got it... will let it run for a while and post logs later!

Thank you!
 
Is this supposed to be opening 2 chests, and remaking game? Just want to make sure my bot isn't missing something?

Oh oops, that game had 3 chests. Got it... will let it run for a while and post logs later!

Thank you!

There's a possibility of 4 chests spawning on this profile with a MINIMUM of 2 chests spawning. This is all about luck I'm afraid.

Thanks for the positive feedback guys, happy hunting. :cool:
 
Seems working perfectly just like how the old one use to be. with the double loot buff i get around 5-7 lps average which is super good :)
thanks op for the remake but for settings, i wouldnt recommend turning off 'always on foreground'. foreground spoofing is needed to minimize detection by blizzard imo.
 
Back
Top