CheezyWhizy
New Member
- Joined
- Sep 10, 2015
- Messages
- 10
- Reaction score
- 0
EDIT: FIXED
Bot places a few unid gear (meant for ChaosRecipe) into stash according to settings but takes them back out and keeps it in the inventory for the duration of the MapBot session.
When the inventory is full of loot after the run, the bot stashes everything (including the item) but, again, takes it out right before running another map.
Bot cannot proceed to do vendor ChaosRecipe because of this.
edit: I tried selling the item and clearing out stash tab "2". Now it doesn't stash anything at all for the ChaosRecipe.
LOG:
[CurrencyRestockTask] No currency to restock.
[VendorTask] No items to vendor.
[FastMoveFromStashTab] Fail to find item at {2, 1} in "2" tab.
[SellRecipeTask] Failed to withdraw an item for the recipe, aborting
edit2: On ChaosRecipePlugin, the bot registers that there are items on the stash tab even though it is completely empty.
"amount registered and available for recipes > 2"
I figured the temp cache wasn't refreshed. It was a simple restart of the application-- but still a bug that needs to be fixed nonetheless.
Bot places a few unid gear (meant for ChaosRecipe) into stash according to settings but takes them back out and keeps it in the inventory for the duration of the MapBot session.
When the inventory is full of loot after the run, the bot stashes everything (including the item) but, again, takes it out right before running another map.
Bot cannot proceed to do vendor ChaosRecipe because of this.
edit: I tried selling the item and clearing out stash tab "2". Now it doesn't stash anything at all for the ChaosRecipe.
LOG:
[CurrencyRestockTask] No currency to restock.
[VendorTask] No items to vendor.
[FastMoveFromStashTab] Fail to find item at {2, 1} in "2" tab.
[SellRecipeTask] Failed to withdraw an item for the recipe, aborting
edit2: On ChaosRecipePlugin, the bot registers that there are items on the stash tab even though it is completely empty.
"amount registered and available for recipes > 2"
I figured the temp cache wasn't refreshed. It was a simple restart of the application-- but still a bug that needs to be fixed nonetheless.
Last edited: