Siege Camp Chest Runner V2.1 - Fast Legs & No Gear Required

i don't know why you guys run insta leave. 1, is kinda a sure method to show you using something and more important 2) the way the profile is working it will move from chest (and return only if is something to loot) so when you open last chest it will move and insta leave before you will see the leg (tried that and on 3th run with insta leave saw 1 leg and network disconnect message).

i do 60gph (picking all, gold, yellows gems) with 2.5-3.5 lph for 10+ hours (i do get some lucky days, was at 6.5lph yesterday on my barb after 7 hours, but i don't count thoose as normal runs) and 65-68gph picking only legendaries (no insta leave). works on wizzard/barb, both of them are close to 70gph only picking legs.

LE: also, after i used for 3 runs the insta leave like 1 week ago for 3-4 days i started to have the magnificent error. had to stop the bot after 2-3 hours, put a bigger number between games, was a pain. in last 3 days i run 20h+ non-stop with 2-3 seconds between games and no error. it might be just for me, or is fixed, but the error is clearly something that is up when servers are protecting from some spam/or are full and when you use insta leave i presume you kinda spam the server with some ability you don't have until you get dc.

 

How you can configure instant leave plz ?

 

Me too. Barb and Wizard are capable of doing 75-80 GPH (which gives 5-7 legs/hour most of the time) but after a couple of hours the Error occurs, so I'm back to None-Instant-Leave Version and a longer wait-timer until the Error is gone.

I never failed to loot a Legendary at the last Chest with Instant Leave btw.

 

Its all the people that whines about nerf that have the negative attitude

I can show logs that show that the L/H is just the same for the last 12 hours for me as it has been the last week

Its all about RNG..

Let it run for 12 hours + then report back

 

I use 3-7 sec

 

Ever since I started running 2 concurrent accounts, my toons sometimes run the same route they've just cleared instead of leaving the game and restarting the route. Anyone else experience this or know how to fix this?

Edit: Even with just one running, my toon doesn't always exit the game and will just port to town, open the map again and re-run the already-done map (sometimes multiple times)

Correct:
Loaded profile Siege Chest Runner v2.1 - by CaptainAmerica
GameChanged. Clearing actors
[Trinity] New Game - resetting everything
ProfileOrderManager.OnGameJoined, Reloading profile.

Incorrect:
Loaded profile Siege Chest Runner v2.1 - by CaptainAmerica
Game joined, Resetting profile caches.
[Trinity] Turned OOC off.
USING WAYPOINT
Using Waypoint. Number:8
CHEST FARM BEGIN

 

hi I cant run the profile after the last db patch and I cant see an update on the main post can someone help with this please. Thanks

 

I hope it's just rng. I love the profile but I noticed after running it a full day yesterday and 8 hrs last night I've been getting less than 1 an hr. It's said .80 hr. Last week i was getting around 2-3 sometimes 4 an hr. I'm running it again today while at work and I'll let you know what I come up with.

 

How do you make this profile pick up magic quality items? I just realized I was down under 100 Arcane Dust which is a huge hit to my crafting abilities. This run usually nets 1-2 blue per chest, so it would be very effective for farming dust too.

 

I suspected a nerf yesterday, but then i left it running over night. This morning i had both soh and th in my inventory = happy wiz

 

What was you leg per hour? Nice. Yea I can't complain even if they needed it. It gives me time to enjoy life outside of the game by not sitting there farming by hand. Grats on your find

 

i ran the bot for 10 hours yesterday and had around 5.8 LPH

 

trinity settings > pickup. set all blue to pickup

 

Nice. Hopefully it was just bad luck for me. I logged out this morning hoping it gives me better luck

 

My HC char got killed last night. Got stuck at the guard tower....

Not HC safe...

 

Thank you, that worked. I figured that section had something to do with it, but I wasn't sure how to do it properly off hand. It's going to slow me down quite a bit, but at this point.. having no arcane dust is a huge burden lol.

 

You are the one unlucky one I guess.
I've been running this profile on my barb w/ firewalkers on HC so I doubt he'd ever get stuck on a guard tower.

Been using this profile for at least 2 weeks with no issues.

 

There's a disclaimer on the front page saying this MAY happen. I've run hundreds of hours and never had it happen to me a single time, but people here have been very clear about not using gear/toon you care about dying with if you're going to do AFK HC farming. Just make a duplicate 70, load it up with high defense yellows and you'll be fine unless you get stuck, but it wont matter since you don't lose the gear you care about.

 

Bug

I start diablo, start the bot, uncheck OOC, start botting.

Some runs it works fine, some times it'll teleport to the siege camp and it is already in the process of leaving the game.

I'm running this on a monk, by the way.

Edit: And the leaving causes me to go up to 80gph and then I start getting 42002 errors.

What is going on? It seems like monks have the same bug as crusaders.


Error that happens:
Exception when terminating bot thread. System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 760
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(Int Ptr 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_Name()
at Zeta.Game.Internals.Actors.ACDItem.get_ItemType()
at Zeta.Game.Internals.Actors.ACDItem.get_ItemBaseTyp e()
at Zeta.Bot.Logic.BrainBehavior.
(ACDItem )
at System.Linq.EnumerableSorter`2.ComputeKeys(TElemen t[] elements, Int32 count)
at System.Linq.EnumerableSorter`1.Sort(TElement[] elements, Int32 count)
at System.Linq.OrderedEnumerable`1.<GetEnumerator>d__ 0.MoveNext()
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
at Zeta.Bot.Logic.BrainBehavior.(Object )
at Zeta.TreeSharp.Sequence.
.
()
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.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.TreeSharp.Sequence.
.
()
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.
()

 

There's no bug with crusaders, as Steed Charge works fine now. I've also had no problems running this profile on my monk. But for some reason, it runs like crap on my Barb which most people have no issues with. I think the profile just takes some tweaking depending on the character you're using.