Hmmm, 1.4 uses the new stashing behavior tree that .180 DemonBuddy uses. Runs fine over here... I'll see if I can find out what's happening, but will need logs with diagnostic level logging!
At first thanks for the great plugin!
Unfortunately its the same problem here, I'm using AGB with the Demonbuddy townrun option.Townrun starts, some gems and tomes are stashed (but not all), It starts to judge the items and continues to do so.
Was it just an endless loop of "ItemRules" stuff? No mention of "GilesStashReplacer" in the logs anywhere? That to me looks suspiciously like the stash replacer plugin isn't "in control". Do you have a longer log available from the point the town-run started (eg when items were being identified) all the way up to the point it got stuck?
Code:
[06:44:46.515 D] [GilesStashReplacer 1.4] Stash attempt on item: 'Tome of Secrets' [Crafting_Training_Tome-19 - CraftingMaterial]. Stackable=True. TwoSlots=False
[06:44:46.750 D] Moving item args: <itemId:2023882965, ownerId:2023424064, InventorySlot:PlayerSharedStash, column:4, row:29>
[06:44:47.640 D] System.AccessViolationException: Could not read bytes from 00000000 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Actors.ACD.()
at Zeta.Internals.Actors.ACDItem.ParseItemTable()
at GilesStashReplacer.GilesStashReplacer.GilesStashAttempt(ACDItem item)
at GilesStashReplacer.GilesStashReplacer.HandleItemStashing(ACDItem item)
at GilesStashReplacer.GilesStashReplacer.DealWithKeepItemProperly(Object ctx)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..MoveNext()
at (Object )
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..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..MoveNext()
at (Object )
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.CommonBot.BotMain.()
[06:44:48.062 V] [ItemRules] Matched Glittering Hoplon of Spikes with rule: Sell leftover junk:Sell
Firstly, the other bugs you posted mean exactly what they said - you didn't have the plugin installed to the correct directory! Looks like you fixed that error though. The one above - now THAT'S an ugly looking bug that seems to be related directly to DemonBuddy. The plugin has told DemonBuddy to make sure the item stats are correct, DemonBuddy has gone to read the memory, and it's failed. This is literally just DemonBuddy being a complete spaz at reading item info
Yeah
1.4 is broken somehow ;-/
same here, using 1.4, have to manually stash the gems/mats then it starts moving again
Don't suppose you could give me (can forum PM if you don't want to post in "public view") Demonbuddy logs that cover the town-run routine could you? If you want to try and force it to happen and have a short log, a very simple way is;
1: Fill your backpack up. Doesn't matter if it's with items, craft materials or both. You can even hold shift and click some stacks to split the stacks up just to totally fill your backpack.
2: Stand a small way away from the stash (and away from the blacksmith!).
3: Start DemonBuddy up, make sure a loot-rules file and the plugin are enabled.
4: Click start and a town-run routine will instantly start you'll know it's working because it should run to the stash before anything else.
Get ready to click "Stop" again if you want to prevent a blacksmith visit (up to you), but if you can get it stuck doing this, then the full log-file from the time you opened DemonBuddy to the point of it getting stuck would be very useful, and should be a relatively small log (since you only just opened DemonBuddy).
Thanks!
