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

Got the new trinity which had a XML folder, but just getting this:

System.Exception: Element TrinityOOCToggle is not supported. Please check your XML and try again. (<TrinityOOCToggle SetTrue="false" />) Line 27
at ‚..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ‚..
(XElement , Type )
at ‚..
.
(XElement )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at ‚..
(XElement , PropertyInfo )
at ‚..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

 

Not only is my guy sometimes skipping the 2nd chest, at one point I was observing and he skipped the last 2 chests (the ones that can spawn together) entirely and just ported off. Anyone else experience this?

 

Here just check "Open Chest" in combat routines or trinity might kill your gph.

 

copy TrinityOOCToggle.cs into the XMLtags folder

 

The new trinity removes it's xml folder so in the mean time I just remade the folder and dropped the ooc by itself which makes it run but very non optimal...it doesn't even loot the items now it just walks to them so I had to recheck loot chests/corpses in trinity settings....hope this is just a temporary prob

 

does anyone know if you can get StarMetal Kukri from this ?

 

as long as it's not a cache only item, you can get it.

 

It will not open chests. It runs to them but does this weird stop motion thing then runs away. It's almost like it knows were it is but is scared.

Also for that trintiy tags folder i dont seem to have one using 1.9 version.

 

The bot gets stuck infront of the second chest, watched him stand there while a legendary dropped until i manually moved him. Any fix to this?

 

I have a fix for this profile to use the newest trinity. It requires basic knowledge about XML. Open the directory where you store your chest runner profile, right click it and hit Edit. Once inside hit CTRL+F for search. Look for TrinityOOCToggle and delete the entire line its on, work your way down the profile until they are all gone. Its a little slower, but it works at least until the OP can update it properly.

 

40 items so far...all Blue.....man if that is RNG - LOL

 

Works great, avg 50 gph and 3 legs per/hr. Great job

 

Any actual fixes for this yet?

 

Still yielding decent results.

Sadly, still screwed by the loot table....no sets except for 1 or 2 blackthornes lol.

 

I was about to start this profile but I noticed that the Folder "XmlTags" doesn't exist in my "/Demonbuddy/Plugins/Trinity/" folder.
Can I just create that Folder myself or am I just too stupid to find it.

 

they seem to have updated something, I used the exact same profile for 3-4 days, and only today this started to happend.

"You have logged in too soon after being disconnected. Please try again later(code 42002)"

now it happens all the time, I had it on 3-6 seconds, but I am still getting this shit all the time now.. Annoying as fuck.

 

Use an older trinity + quest tools for this script, works fine until you update.

 

I didn't update anything.

they seem to have updated something, I used the exact same profile for 3-4 days, and only today this started to happend.

"You have logged in too soon after being disconnected. Please try again later(code 42002)"

now it happens all the time, I had it on 3-6 seconds, but I am still getting this shit all the time now.. Annoying as fuck.

 

this has nothing to do with the profile. there are about 30 posts about this earlier in the thread.

 

I don't know if that's your problem.. But, did you change your toon?
I had a toon trying to run ghom, but I never killed ghom with that character, so this message showed.. I changed character, to a one that had killed it, and voila! It worked...

Hope it helps!