Depot Action

[pvzin]

Hey, guys!
Well, I'm using this code here to deposit stuff and usually everything goes fine.

--depositer

setsetting('Cavebot/WalkThroughPlayers', 'no')

closewindows()

openitem(itemname($back.id), 'back')

waitping()

openitem(lootbp, itemname($back.id))

waitping()

openitem(lootbp, lootbp)

waitping()         

resizewindows()

waitping()





if windowcount(lootbp) ~= 1 then

    gotolabel($wptid-1)

end





waitping()

setsetting('Looting/OpenNextBP', 'no')

waitping()

depotaction('maindp', 'lootbp', {'r', 'raredp', 's', 'stackdp'})

waitping()

However, once in a while it will also deposit the potions I have on my main backpack.
Is there a way to avoid that without having to use a supply backpack?

[Frox]

I dont get it.
Just simple add

openitem(0, "back", true)

[pvzin]

I dont get it.
Just simple add

openitem(0, "back", true)

I saw that..

The action works, bro. The problem is restricted to the depositing line.
Once it opens the lootbp and starts depositing, it will come back to the previous lootbps, so it can deposit everything.
But there's a point when it reaches the mainbp, and when it does so, there are some occasions on which it also deposits the potions I have there.

So mainly, I would like to know if there's a way to avoid the bot getting to the mainbp on this point, or stop depositing the potions I have there.

[Dworak]

so close your main backpack after open the LootBP or open in MainBp window

[pvzin]

so close your main backpack after open the LootBP or open in MainBp window

They do open in the same window. I think the action pretty much gives it out, doesn't it? '-'

Let's focus here:

waitping()

setsetting('Looting/OpenNextBP', 'no')

waitping()

depotaction('maindp', 'lootbp', {'r', 'raredp', 's', 'stackdp'})

waitping()

Consider I have 2 lootbps, then I'll name them for you:
- mainbp = #1
- 1st lootbp = #2
- 2nd lootbp = #3

The action will open everything until #3, then it starts depositing.
When there are no items left on #3, it goes back to #2 and deposits whatever is left there.
*Finally, it goes back to #1, so it can open the lootbp again, for an extra check.*

That's how this code works:

depotaction('maindp', 'lootbp', {'r', 'raredp', 's', 'stackdp'})

The thing is, when it comes to the last part (*), I, sometimes, have my potions deposited.
I don't want that to happen, though.

Was it clear enough now?!

[CroiX]

Well, you obviously got your potions in category 'r' or 's' then. Just remove the category and it won't deposit. =)

[pvzin]

Well, you obviously got your potions in category 'r' or 's' then. Just remove the category and it won't deposit. =)

Yep, they are categorized because they are also loot from the hunt.

[CroiX]

Yep, they are categorized because they are also loot from the hunt.

You don't need a category to loot them. Simply remove the category, or change to anything else but R and S and you'll be fine.

[pvzin]

You don't need a category to loot them. Simply remove the category, or change to anything else but R and S and you'll be fine.

True, but then I won't get to deposit the looted ones, right?! :P
You see, I want to deposit the looted potions, but not the ones I'm gonna use, that's why they are in different bps, hehe!
Thx for the time, though!

---

@thread:
If anybody else thinks of a solution, please bring me them!

[BUgWT]

Since I don't use depotaction(), maybe you can try this
A hotkey to change potion's category, for example

auto(100)

if $wptid == 123 and windowcount($back.id) == 1 then

     --category Z

else

     --category S

end

Which means when it is in main bp, it will change the category to "Z"