additem #itemid//#shift-click-item-link #itemcountĪdds the specified number of items of id #itemid (or exact (!) name $itemname in brackets, or link created by shift-click at item in inventory or recipe) to your or selected character inventory. help achievement $subcommand to see info on subcommands
achievement to see the list of possible subcommands or. $achievement: can be either achievement id or achievement linkĬheck all achievement criteria of the selected player. help account set $subcommand to see info on subcommandsĭisplay the access level of your account.Īdd an achievement to the targeted player. account set to see the list of possible subcommands or.
#Wow setting spell queue password#
account set password $account $password $password Set the security level for targeted player (can't be used at self) or for account $name to a level of #level on the realm #realmID. Addon values: 0 - normal, 1 - tbc, 2 - wotlk. Set user (possible targeted) expansion addon level allowed. account password $old_password $new_password $new_password account 2fa setup PIN to confirm setup.Īllow login from account only from current used Country or remove this requirement.Īllow login from account only from current used IP or remove this requirement. Apply token to authenticator app (case sensitive). These commands can not be used in the world console. Note: Some commands are working only by selecting a player or a creature. There, all commands must start with a leading dot, f.ex. The other way is using the gm command ingame in the chat console of the wow client.
In the world console window the leading dot (.) is not mandantory, but you can use it. Either by typing it directly into the world console window. GM commands can be entered mainly in 2 ways.
#Wow setting spell queue code#
It is not known at this time if other pets are affected by this bug, but it’s easy enough to code around it if it is. If you run with multiple pets (say for PvP), you may want to make your attack macros pet-sensitive. Pretty simple, right? Do this for every one of your offensive spells, replacing Immolate with the appropriate spell name. You may want to include Curse of Doom in this list, too. This is a relatively simple fix if you are comfortable with macros, so it’s a good time to try them out if you’ve never done so before.Īt a bare minimum, your 4 primary offensive spells (Immolate, Conflagrate, Incinerate, Chaos Bolt) need to be supplemented with a macro that queues your Imp’s Firebolt for casting. If you’re not comfortable with macros, you may want to look at my Introduction to Macros and Warlock Macros posts. You’re going to have to solve this with macros. And you can’t micromanage your pets’ firing rate.
Obviously, considering how many of your buffs are tied into the Imp, this can’t stand. If you don’t, they autocast every 2.14 seconds or so. If you spam the spell on the pet bar, the Firebolts fire every 2.0 seconds.
#Wow setting spell queue manual#
See, the bug only affects autocasted Firebolts, not manual ones. While small, this delay adds up over the course of a fight. So there’s a pause between each Firebolt as the WoW client communicates with the server. Seems if you leave your Imp on autocast, its Firebolt is affected by an old client-server casting bug that used to bedevil warlocks, especially with Immolate. So, here’s an interesting warlock bug that I didn’t know about.
0 kommentar(er)
