What's new
By:
  • 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 - Fast Legs & No Gear Required

Hi, I keep getting the following text in red when I run my bot any ideas? BTW it is running and seems to work.
The following message occurs often after joining a game, but I don't see any negative side effects from it.

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: 5B4D0B0A, Size: 20
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.DiaUnit.get_Level()
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[] )

Also, Thanks for making this guys. Really easy to setup/use and I already found a upgrade in the first day.
 
Last edited:
BlAchPT said:
Finally I solved getting stuck in the second chest for good :)

In Combat/HandleTarget.cs replace:

Code: 
iInteractAttempts = HandleItemInRange();

with:

Code: 
if(Player.Position.Distance(CurrentTarget.Position) > 2f)
{
	ZetaDia.Me.Movement.MoveActor(CurrentTarget.Position);
	PlayerMover.TimeLastUsedPlayerMover = DateTime.UtcNow;
}
else
{
	iInteractAttempts = HandleItemInRange();
}

And also change 2f to 10f in the same file, a little below "private static void SetRangeRequiredForTarget()"

Code: 
case GObjectType.Item:
{
     TargetRangeRequired = 2f;

This will simply click on the ground on the other side of the chest and use Diablo's built-in navigation instead of Trinity's
Click to expand...

Every elegant solution. Utilize D3 navigation until we are within 2f of the object. I was trying to figure out a way to detect in path objects and route around but this is much simpler. Thanks for sharing.

EDIT - Just as a side note do you think it will be an issue with the sheer amount of times the bot will be clicking the item location? The refresh cycle on a loop like that has got to be really high. The default Trinity interaction is paused until item is within range, hence the 2f or 1f.
 
Last edited:
if you have some good fury regen, you can use the tornado rune in sprint + the speed bracers... the tornados will destroy some objects by themself and you dont waste time attacking them ;)

btw: @stage2 why the bot runs to chest 1, opens it, going to chest 2, opens it, then goes back to check the 1. chest, checking the second chest, then running a few meters before run ends? he runs 2x to the both chests ^^ and why he doesnt port back at last chest ? he is running a few meters^
 
Last edited:
CaptainAmerica why does my bot sometimes skip the 3. chest he runs up to it and dont open it.

And he SOMETIMES skip the second chest to, the one alone where people cant loot Legendaries sometimes.

Its the one on the last spot on the top.

And for some reason the gold inactivity timer kicks in sometimes, because my char just stands still sometimes.

This is all with the latest beta and trinity .28
 
Last edited:
creepa7 said:
if you have some good fury regen, you can use the tornado rune in sprint + the speed bracers... the tornados will destroy some objects by themself and you dont waste time attacking them ;)

btw: @stage2 why the bot runs to chest 1, opens it, going to chest 2, opens it, then goes back to check the 1. chest, checking the second chest, then running a few meters before run ends? he runs 2x to the both chests ^^ and why he doesnt port back at last chest ? he is running a few meters^
Click to expand...

You left chest opening selected in Trinity. That is why at the last location it keeps going back and forth. It should only go to each chest once and then go back if it needs to loot anything.
 
BlAchPT said:
Finally I solved getting stuck in the second chest for good :)

In Combat/HandleTarget.cs replace:

Code: 
iInteractAttempts = HandleItemInRange();

with:

Code: 
if(Player.Position.Distance(CurrentTarget.Position) > 2f)
{
	ZetaDia.Me.Movement.MoveActor(CurrentTarget.Position);
	PlayerMover.TimeLastUsedPlayerMover = DateTime.UtcNow;
}
else
{
	iInteractAttempts = HandleItemInRange();
}

And also change 2f to 10f in the same file, a little below "private static void SetRangeRequiredForTarget()"

Code: 
case GObjectType.Item:
{
     TargetRangeRequired = 2f;

This will simply click on the ground on the other side of the chest and use Diablo's built-in navigation instead of Trinity's
Click to expand...

have you found any improvements for the profile too?
 
CaptainAmerica said:
You left chest opening selected in Trinity. That is why at the last location it keeps going back and forth. It should only go to each chest once and then go back if it needs to loot anything.
Click to expand...
dude, you are a god... and im so stupid sometimes :D can you help me another time and tell me how to make it instaleave? im a noob
 
creepa7 said:
dude, you are a god... and im so stupid sometimes :D can you help me another time and tell me how to make it instaleave? im a noob
Click to expand...

Sorry I am against using that exploit and if you feel you must you need to do the research yourself. My FAQ can point you in the right direction if you insist on heading down that path.
 
if a legendary drops out of a chest bot dont run straight back to chest, it runs a little loop i think, how we can fix that?
 
sebflex said:
if a legendary drops out of a chest bot dont run straight back to chest, it runs a little loop i think, how we can fix that?
Click to expand...

Looting has nothing to do with a profile. Trinity is in charge at that point and we could probably change that behavior but it will introduce other issues/challenges. Straight line pathing does not work if their is something in the way!
 
snakkes said:
CaptainAmerica why does my bot sometimes skip the 3. chest he runs up to it and dont open it.

And he SOMETIMES skip the second chest to, the one alone where people cant loot Legendaries sometimes.

Its the one on the last spot on the top.

And for some reason the gold inactivity timer kicks in sometimes, because my char just stands still sometimes.

This is all with the latest beta and trinity .28
Click to expand...

Anyone?
 
CaptainAmerica said:
Every elegant solution. Utilize D3 navigation until we are within 2f of the object. I was trying to figure out a way to detect in path objects and route around but this is much simpler. Thanks for sharing.

EDIT - Just as a side note do you think it will be an issue with the sheer amount of times the bot will be clicking the item location? The refresh cycle on a loop like that has got to be really high. The default Trinity interaction is paused until item is within range, hence the 2f or 1f.
Click to expand...

I tested the default routine and it clicks ~10 times even with nothing changed, but you're right.

Maybe this will work better:

Code: 
if(Player.Position.Distance(CurrentTarget.Position) > 2f)
{
	if(!isMoving || DateTime.UtcNow.Subtract(PlayerMover.TimeLastUsedPlayerMover).TotalMilliseconds > 500)
	{
		ZetaDia.Me.Movement.MoveActor(CurrentTarget.Position);
		PlayerMover.TimeLastUsedPlayerMover = DateTime.UtcNow;
	}
}
else
{
	iInteractAttempts = HandleItemInRange();
}

Now it will click 2 times a second max, hopefully...

EDIT: !isMoving check is needed also
 
Last edited:
CaptainAmerica said:
Looting has nothing to do with a profile. Trinity is in charge at that point and we could probably change that behavior but it will introduce other issues/challenges. Straight line pathing does not work if their is something in the way!
Click to expand...

so we can change nothing in trinity for straight pathing to chests(or maybe to items we will loot)?
 
BlAchPT said:
I'm still modyfing the profile and the OOC file, making them customized for my Demon Hunter. Will let you know when I'm done. ;)
Click to expand...

You use Assembla? I can put you on my fork. It has the latest copy of Trinity and the profile under revision control.
 
Last edited:
You must log in or register to reply here.
Back
Top