[bug] Infinite Stash Loop

[Gorm]

My bot got stuck in a stashing loop, swapping the same item in the stash.

[23:07:16.528 N] Loaded profile Sarkoth farm profile by Nesox
[23:07:16.528 N] Number of games completed:10
[23:07:16.897 N] Last run acquired 3878 gold.
[23:07:16.899 N] Current Gold per Hour: 152930
[23:07:35.929 N] [w3eZle's Sarkoth Kill Wait v0.5] Enabeling KillMonsters & PickupLoot
[23:07:56.695 N] [w3eZle's Sarkoth Kill Wait v0.5] Disabeling KillMonsters & PickupLoot
[23:09:30.650 N] Stashed item [Shadow Apex]
[23:09:59.183 N] Stashed item [Shadow Apex]
[23:10:17.711 N] Stashed item [Stout Gate]
[23:10:22.719 N] Stashed item [Shadow Apex]
[23:13:29.058 N] Stashed item [Shadow Apex]
[23:14:36.188 N] Stashed item [Stout Gate]
[23:15:33.263 N] Stashed item [Shadow Apex]
[23:16:08.323 N] Stashed item [Shadow Apex]
[23:16:37.861 N] Stashed item [Stout Gate]
[23:18:36.587 N] Stashed item [Shadow Apex]
[23:20:41.228 N] Stashed item [Stout Gate]

Enabled Diagnostic Logging Here

[23:23:10.937 D] Moving item args: <itemId:1, ownerId:5, InventorySlotlayerSharedStash, column:1, row:0>
[23:23:10.945 N] Stashed item [Stout Gate]
[23:23:12.562 D] Moving item args: <itemId:2, ownerId:5, InventorySlotlayerSharedStash, column:1, row:1>
[23:23:12.571 N] Stashed item [Shadow Apex]
[23:23:14.177 D] Moving item args: <itemId:1, ownerId:5, InventorySlotlayerSharedStash, column:1, row:0>
[23:23:14.202 N] Stashed item [Stout Gate]
etc...

I replaced itemId and ownerId because it would obviously identify me.

 

[marko001]

I have exactly same problem.
I read trough forum and tried to manage the .xml so that it can't generate errors.
I read about Blacksmithing lvl10 before using salvaging so I removed from Priorities in .xml
I checked 1st stash as protected and Ignore when inventory full.

Whenever inventory is full it returns to town, go near stack and starts looping (sometimes it also does it near TP in town) until I manually move a yellow in stack. Then it goes selling, reparing (if needed) and redo TP.

Where is the error? Is this a DB errror or what?

Thanks,

M.