This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.7
PTR
10.2.6
Beta
Macro not functioning as expected.
Post Reply
Return to board index
Post by
pelf
It defaults to true even for characters existing before its implementation. Is yours false?
Post by
RedwoodElf
I dunno...I created my Druid about 2 years ago, shortly after the release of BC...yours predates that?
EDIT: Mine's True Pelf...his is apparently false.
I don't see any checkboxes in the interface to turn it on and off...maybe it's linked to another one, like "auto self cast?"
So the following should turn it on for him?
/run SetCVar("autoUnshift",true)
Post by
Wanderingfox
There used to be one, way the hell back when they put the option in... It appears that they've overlooked it when they redid the interface UI however.
I may have manually set mine way back then and completely forgotten about it, but yes /run print(GetCVar("autoUnshift")) returns false and that's how I want it :P The last thing I need is to pop out of bear because I fat fingered rejuv.
Post by
pelf
I have it set to true so I don't have to have a powershift macro. My form macros are all
/cast !<form_name>
so if I'm in cat and I want to break a snare, I just press my cat button and I shift from cat to cat. I also don't want to have to cancel a form to cast a heal. With autoUnshift true, it's only one physical action for me to start healing.
/run SetCVar("autoUnshift",true)
Another way to do that is:
/console autoUnshift 1
A bit easier to remember, IMO :).
Post by
RedwoodElf
There used to be one, way the hell back when they put the option in... It appears that they've overlooked it when they redid the interface UI however.
I may have manually set mine way back then and completely forgotten about it, but yes /run print(GetCVar("autoUnshift")) returns false and that's how I want it :P The last thing I need is to pop out of bear because I fat fingered rejuv.
Thats why I don't put Rejuv on my bear bar unless it has a on it...heh
Post by
Wanderingfox
Right, hypothetical situation was hypothetical...
With that said, some of us run with more actionbars on the screen than just our main one. For example, I have several actionbars along the bottom of my screen and only one of which changes based on the stance that I'm in (oh @#$% heals being on another so that I can reach them when I'm not healing without having eat keybindings or switch pages). Granted this is a left over from back when it was advantageous to have multiple ranks of a spell on your bar (especially druids... who the hell ever casts max rank healing touch? >_<), but it's still an ease of use thing.
Some of the spells on that other pages would trigger me to switch stances when I don't want to, as well as a few keybinds that I have, and I'm already pushing the limit of macros on the toon for various other things, so forcing a onto my heals rather than just making them not break forms unless I tell them to explicitly is really the better option.
Post by
112926
This post was from a user who has deleted their account.
Post by
Wanderingfox
(Assuming you are still having macro issues)
Double check all your ' ; and : are correct. More then one of my macros has broke (or reacted in bizarre ways) all for using : where I should have had ;
If breaking the lines up fixes it, I'll bet it's something like that.
Double, triple, and quadruple checked. It's actually the first thing I looked at. I know my syntax is right (as I've proven by the separated macro), the question is why it doesn't function when put back together. Not that it matters since the expanded macro fits within the size limitations.
Post by
112926
This post was from a user who has deleted their account.
Post by
RedwoodElf
(Assuming you are still having macro issues)
Double check all your ' ; and : are correct. More then one of my macros has broke (or reacted in bizarre ways) all for using : where I should have had ;
If breaking the lines up fixes it, I'll bet it's something like that.
Double, triple, and quadruple checked. It's actually the first thing I looked at. I know my syntax is right (as I've proven by the separated macro), the question is why it doesn't function when put back together. Not that it matters since the expanded macro fits within the size limitations.
Hum... what happens if you put Flight Form before Travel? Anything?
(I'm a programmer at heart, and I can't leave a broken script alone. <_< )
Then it would try to cast flight form in combat in a flyable area, and that won't work.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.