in your browser.
Pickpocket macro fizzling
Return to board index
So I ripped this default pickpocket with autoloot macro from somewhere and it's served me well. Today it suddenly started acting up.
It's supposed to put on autoloot, pickpocket the target and go back to autoloot by keypress. It gets to the 2nd part but refuses to reset my default lootsettings.
I can't find anything wrong with the macro nor have I heard about any recent changes to autolooting.
Anyone have an idea what's going wrong?
/script SetCVar("AutoLootDefault", 1)
/cast Pick Pocket
/in 1 /script SetCVar("AutoLootDefault", 0)
can the /in command run scripts?
If so, Did you remove an addon that gave you the /in command?
Try this instead:
/cast Pick Pocket
That will turn autoloot back on if you use it when you're not stealthed or in combat. You can't loot except for picking pockets and remain stealthed, and (unless you're shadowdancing) can't pick pocket when not stealthed, and if you're shadow dancing you're probably in combat, so it will work then too.
Edit: fixed the error message if you're not targetting something that's pickpocketable.
I've recently updated my Decursive and I think this might be the culprit. As soon as I tried out your new macro, I got a Lua error report indicating this.
When using the new one it does indeed pickpocket but the now there's that nasty error in my way..
Odd...why would changing a console variable cause decursive to make a lua error? Oh, wait, missing quote marks...fixing...
This one seems to be doing the trick, thanks alot!
Not that you're necessarily still here, but I always preferred the console way of setting console variables:
/console AutoLootDefault 1
A bit cleaner than the SetCVar API.
This post was from a user who has deleted their account.
You are not logged in. Please
to post a reply or
if you don't already have an account.
Connect with Wowhead
Other Fanbyte Sites
Hearthstone Top Decks
Final Fantasy XI
© 2021 Fanbyte