-
Bug in Deposit
Code:
-- Depositing
setuseroption('reopenBps', false)
init start
local CONFIG = {
LOOT_BACKPACK = getlootingdestination('lootBp'),
MAIN_DP_BACKPACK = getlootingdestination('mainDpBp'),
STACKABLE_BACKPACK = getlootingdestination('stackDpBp'),
NOT_STACKABLE_BACKPACK = getlootingdestination('lootDpBp'),
}
init end
if (not isrange(4, 11)) then
gotolabel("inDp1", "Venore")
else
closewindows() wait(500, 600)
while (windowcount(CONFIG.LOOT_BACKPACK) < 1) do
closewindows()
wait(1000, 1111)
openitem(0, "back")
wait(1000, 1111)
openitem(CONFIG.LOOT_BACKPACK)
wait(1000, 1111)
resizewindows()
end
setsetting('Cavebot/WalkThroughPlayers', 'no')
setsetting('Looting/OpenNextBP', 'no')
while windowcount("Depot box") == 0 do
opendepot()
wait(1000, 2000)
end
while windowcount(CONFIG.MAIN_DP_BACKPACK) == 0 do
openitem(CONFIG.MAIN_DP_BACKPACK, "Depot box")
wait(1234,2345)
end
clearlastonto()
while (true) do
foreach lootingitem ITEM_ENTRY do
if ITEM_ENTRY.category ~= "r" then
while (itemcount(ITEM_ENTRY.id, CONFIG.LOOT_BACKPACK) > 0) do
if (itemproperty(ITEM_ENTRY.id, ITEM_STACKABLE)) then
moveitemsonto(ITEM_ENTRY.id, CONFIG.STACKABLE_BACKPACK, 1, CONFIG.MAIN_DP_BACKPACK, CONFIG.LOOT_BACKPACK) wait(600, 1200)
else
moveitemsonto(ITEM_ENTRY.id, CONFIG.NOT_STACKABLE_BACKPACK, $lastonto, CONFIG.MAIN_DP_BACKPACK, CONFIG.LOOT_BACKPACK) wait(600, 200)
end
wait(200, 300)
end
end
end
if (itemcount(CONFIG.LOOT_BACKPACK, CONFIG.LOOT_BACKPACK) > 0) then
openitem(CONFIG.LOOT_BACKPACK, CONFIG.LOOT_BACKPACK, false) waitcontainer(CONFIG.LOOT_BACKPACK, false)
else
break
end
wait(100)
end
setsetting('Cavebot/WalkThroughPlayers', 'yes')
end
This action stopped working when i release this new version of tibia and bot. he does not open the backpack of char just to depot anymore.
i know. i can replace the code for something better plus an error in a function can destabilize a lot.
Notes: This Action has never given problems before and has not been tampered with at all. Tested on multiple scripts and chars and client 11 and 10 and continues with the problem.
Notes2: And forgive me if this is the wrong area ... i was confused if you put it in the Bug or Support section
After all the Action is the same one that i have always used so it is probably a bug in some function
-