Mouse over syntax questions

[Grabco]

I'm currently using this macro as my frostbolt mouse over macro, how can i get it to do rank 1 frost bolts. I know it sounds stupid but i can't get it to work. If someone could please give me a workable macro for rank 1 mouse over i'd appreciate it.



#showtooltip Frostbolt

/cast [target=mouseover,harm] Frostbolt; Frostbolt



Another one I found and I don't know if it works yet:

The second bracketed harm may be important for the rank 1 frostbolt.



mouseover rank 1 frostbolt ( for peeling )



#showtooltip Frostbolt(Rank 1)

/cast [target=mouseover, harm][harm] Frostbolt(Rank 1); Frostbolt(Rank 1);



will cast rank 1 frostbolt on your moused over target whether it be focus target or just mousing over a enemies character if you're not moused over somebody it'll cast rank 1 frostbolt on your normal target

 

[lindenkron]

/cast Lesser Heal(Rank 1)



casts Rank 1 for me... problem elsewhere?

 

[Grabco]

Maybe it was a problem with the spacing idk or the bracketed "harm".

 

[Mazurati]

#showtooltip

/cast [target=mouseover,exists][] Frostbolt(rank 1)



shift click the rank spell from your book. That should remove any doubts.



if there is a target on your mouseover you'll cast rank 1 FB, if not then you'll cast it on your target

 

[Grabco]

Ok, so I'm a little new to the mouseover macro stuff previously limited myself to mouse over decurses but why aren't more people using these? I would think mouse over DoTing as a lock would be easier and more directed than aimless tab dotting, same goes for shammies with interupts? I know priests use mouse over dispells a lot If you are a caster I guess I could see a lot of benefits to having a lot of abilities on a mouseover type of set up with the default set to attacking your target especially if you are on the move. Anyone have any comments to mouse over abilities that could be beneficial for other classes. Mouse over frostbolt changed my life.



I guess the downside to this would be constant mouse turning AND mouse over spells but I think most people should be able to do both.

 

[ArthurianKnight]

Ok people have the tendencies to had brackets that shouldn't be there !



exemple...

[harm] and [] will both cause trouble.

if you have to put no options, then dont put anything at all, otherwise the engine might make mistakes.



Making a Macro

Great place to learn everything about macros.



as for your macro...

heres what you want.

/cast [target=mouseover, harm] Frostbolt(Rank 1)



in this case the frostbolt will cast only if you mouse over someone and only if you can harm that person, otherwise this macro will simply do nothing.



any [] beyond the first is useless and can only bug the macros even more.



also...

add this to your macro...

#show Frostbolt



what it does...

#Show = Icon that needs to be shown for cooldown purposes.

#showtooltip = stats of the spell on the button.



and for the #show to work you need to set the icon to the red "?"

 

[Crilicilyn]

I like hunters w/

/cast [target=mouseover] concussive shot

/lol [target=mouseover]



I used to get hit with that one a lot.

 

[Mazurati]

Ok people have the tendencies to had brackets that shouldn't be there !



exemple...

[harm] and [] will both cause trouble.

if you have to put no options, then dont put anything at all, otherwise the engine might make mistakes.



Making a Macro

Great place to learn everything about macros.



as for your macro...

heres what you want.

/cast [target=mouseover, harm] Frostbolt(Rank 1)



in this case the frostbolt will cast only if you mouse over someone and only if you can harm that person, otherwise this macro will simply do nothing.



any [] beyond the first is useless and can only bug the macros even more.



also...

add this to your macro...

#show Frostbolt



what it does...

#Show = Icon that needs to be shown for cooldown purposes.

#showtooltip = stats of the spell on the button.



and for the #show to work you need to set the icon to the red "?"

anything in [] are conditions and anything that isn't met in the 1st condition go to the 2nd one... a blank [] means cast on target.



so no.. they are not useless.



+



#showtooltip > #show because it applies to the spell you are casting. don't even bother putting in the name of the spell

 

[ArthurianKnight]

Function <--> Condition <--> Effect

thats all there is to it.



/cast [target=mouseover] Frostbolt

and

/cast [target=mouseover] [] Frostbolt



is the same, but there is one exception, the second [] forces a recheck of the states, because you actually added another conditionnal event. even if its empty you are forcing the engine to basically redo the check, hich in this case has no need for. thus not putting the condition if its empty actually help the engine by not adding unnecessary stuff.





let me put it this way...



if target = mouseover then

---- if nothing then

-------- /cast frostbolt

---- end if

---- /cast frostbolt

end if





or





if target = mouseover then

---- /cast frostbolt

end if





to you which one is better, the shortest one or the longer one that ends up the very same ?

the shortest one has faster processing power, thus is way better engine wise.



back then, during the first times of WOW, the conditionnal were statics, and thus the empty [] were pretty much helping the engine, but now it has been optimised and those empty brackets are just adding task to your processing unit and will simply give it more chance at bugging in.



the more you stay basic and simple, the more chances you got at making a truly optimised macro.





as for the showtooltip thing... you didn't even understood what i said.



showtooltip doesn'T show the icon. while #show does and thus also shows you the CD of the same spell.



thus...

#show

/cast frostbolt



would result in you seeing the frostbolt icon with CD, but no tooltip except the name of the macro you have given it.



while...

#showtooltip

/cast frostbolt

would only show you the icon you chose in the box and the CD won't be showing at all. while you'll be having the frostbolt tooltip instead of the macros name.



best macro type... put both of them... all info gets there.

#show

#showtooltip

/cast frostbolt

will be giving you the frostbolt icon instead of the chosen one, and it will be showing you the CD of the frostbolt.

also it will show you the tooltip of the spell instead of the macros name.

 

[Trespasser]

You can also try this macro:



#showicon

#tooltip

/cast [nomodifier:alt,target=mouseover,harm][nomodifier:alt,harm][nomodifier:alt,target=targettarget,harm][modifier:alt,target=focus,harm] Frostbolt(rank1)



What this macro does a couple of things the first is to show the tooltip and icon of frostbolt rank 1 (dûh).

Then it will cast frostbolt rank 1 in the following order:

First on your mouseover if it's a enemy.

Second your target if you don't have a mouseover target or your mouseover target is not a enemy.

Third on your target of target if your target or mouseover don't exist/are not enemy's (easyway to assist ppl to have the same target)

And Fourth by holding the alt key you will always cast it on your focus target.

 

[Muqmuq]

I roll with mouseover focus allong with [target=focus] frostbolt, sheep, fireblast and wand. It's pretty much the same idea but when you missclick you won't be sheeping of frostbollting the wrong person and I personally don't always get the right target on the first click. You can also select your focus before engaging combat, this saves time. Additionally it also allows you to observe what your target is doing and you can simply swap focus mid cpmbat. For sheeps I deff prefer this, I guess mouseover fb is a nice addition to the focus stuff though for even more more control. I don't see many others use focus macros in wsg but it's certainly helpful.

 

[builtokill]

Function <--> Condition <--> Effect

thats all there is to it.



/cast [target=mouseover] Frostbolt

and

/cast [target=mouseover] [] Frostbolt



is the same, but there is one exception, the second [] forces a recheck of the states, because you actually added another conditionnal event. even if its empty you are forcing the engine to basically redo the check, hich in this case has no need for. thus not putting the condition if its empty actually help the engine by not adding unnecessary stuff.





let me put it this way...



if target = mouseover then

---- if nothing then

-------- /cast frostbolt

---- end if

---- /cast frostbolt

end if





or





if target = mouseover then

---- /cast frostbolt

end if





to you which one is better, the shortest one or the longer one that ends up the very same ?

the shortest one has faster processing power, thus is way better engine wise.



back then, during the first times of WOW, the conditionnal were statics, and thus the empty [] were pretty much helping the engine, but now it has been optimised and those empty brackets are just adding task to your processing unit and will simply give it more chance at bugging in.



the more you stay basic and simple, the more chances you got at making a truly optimised macro.





as for the showtooltip thing... you didn't even understood what i said.



showtooltip doesn'T show the icon. while #show does and thus also shows you the CD of the same spell.



thus...

#show

/cast frostbolt



would result in you seeing the frostbolt icon with CD, but no tooltip except the name of the macro you have given it.



while...

#showtooltip

/cast frostbolt

would only show you the icon you chose in the box and the CD won't be showing at all. while you'll be having the frostbolt tooltip instead of the macros name.



best macro type... put both of them... all info gets there.

#show

#showtooltip

/cast frostbolt

will be giving you the frostbolt icon instead of the chosen one, and it will be showing you the CD of the frostbolt.

also it will show you the tooltip of the spell instead of the macros name.

your an idiot

 

[ArthurianKnight]

thank you !

 

[Ardent]

Function <--> Condition <--> Effect

thats all there is to it.



/cast [target=mouseover] Frostbolt

and

/cast [target=mouseover] [] Frostbolt



is the same, but there is one exception, the second [] forces a recheck of the states, because you actually added another conditionnal event. even if its empty you are forcing the engine to basically redo the check, hich in this case has no need for. thus not putting the condition if its empty actually help the engine by not adding unnecessary stuff.





let me put it this way...



if target = mouseover then

---- if nothing then

-------- /cast frostbolt

---- end if

---- /cast frostbolt

end if





or





if target = mouseover then

---- /cast frostbolt

end if





to you which one is better, the shortest one or the longer one that ends up the very same ?

the shortest one has faster processing power, thus is way better engine wise.



back then, during the first times of WOW, the conditionnal were statics, and thus the empty [] were pretty much helping the engine, but now it has been optimised and those empty brackets are just adding task to your processing unit and will simply give it more chance at bugging in.



the more you stay basic and simple, the more chances you got at making a truly optimised macro.





as for the showtooltip thing... you didn't even understood what i said.



showtooltip doesn'T show the icon. while #show does and thus also shows you the CD of the same spell.



thus...

#show

/cast frostbolt



would result in you seeing the frostbolt icon with CD, but no tooltip except the name of the macro you have given it.



while...

#showtooltip

/cast frostbolt

would only show you the icon you chose in the box and the CD won't be showing at all. while you'll be having the frostbolt tooltip instead of the macros name.



best macro type... put both of them... all info gets there.

#show

#showtooltip

/cast frostbolt

will be giving you the frostbolt icon instead of the chosen one, and it will be showing you the CD of the frostbolt.

also it will show you the tooltip of the spell instead of the macros name.

Your wrong on pretty much every level. The empty conditional is not worthless. Without it the macro will only cast on the mouseover target. If there is no mouseover it will do nothing. With [] in the macro if the mouseover returns false (i.e. no mouseover targets exists) the [] makes the macro behave as if it had no conditionals (i.e. cast at your target).



Secondly, #showtooltip does show the icon, as long as you use the '?' icon. Using both #show AND #showtooltip does nothing but make your macro longer with no additional funcionality.

Without any #show the macro will display the icon of whatever the first listed spell is. With #show it will display the icon of whatever spell you specify and the tooltip will display the macro name. With #showtooltip it will display the specified spell's icon AND tooltip.



Thirdly using [target=mouseover] is redundant, [@mouseover] is exactly the same with 5 less characters.

 

[Grabco]

Thirdly using [target=mouseover] is redundant, [@mouseover] is exactly the same with 5 less characters.

It's not redundant, it would be redundant if you said " target=@mousover" I think the vocabulary word you're looking for is superfluous, meaning excessive and not needed. They only just recently added @ symbol to macros but thanks for reminding me of this. Most people are using old macros but yes @ symbol makes life easier.

 

[Ardent]

Superfluous applies too but it's still redundant, as in superceded by something better and more efficient. Doesnt matter that it still works it's no longer required and thus redundant.

 

[Pizza]

Mouse overs for a mage will only slow you down.

 

[ArthurianKnight]

funny how suddently everyones knows macros, yet nobody besides me wanted to tell you what you needed to do. glad to have sprung that discussion.



if you wish to start to cast everytimes without condition, its at your leasure, but usually when you do a macro, thats because you want it to start with conditions, not just everytimes you push the macro. otherwise, why put it in macro if you want it to be the same as when you just click the ability.



yeah i had forgotten about the @ thing. its quite new, came with 3.1 or 3.2. thats the only thing i hate about blizz, changing marcos like every god damn patches. hard to follow after a while.



well glad to have helped grabco.

 

[Grabco]

Mouse overs for a mage will only slow you down.

I guess I would argue the opposite since not having to click your target seems to speed up target switching.



Please explain how it would slow you down?

 

[Ardent]

if you wish to start to cast everytimes without condition, its at your leasure, but usually when you do a macro, thats because you want it to start with conditions, not just everytimes you push the macro. otherwise, why put it in macro if you want it to be the same as when you just click the ability.

Wow, your really bad at this, i dont even know where to start.



1) the point of using macro's is that they can take different AND multiple conditions.



2) It saves so much space on your UI and saves you multiple keybinds (providing of course your not clicking your billion buttons) to have multiple spells/conditions on one key.



3) If your not using macro's properly and are just having 1 conditional per macro per ability your doing yourself a massive disservice and putting yourself at a massive handicap. Why bother even having a key that 50% of the time does nothing? when you could have a key that 50% of the time does one thing and 50% of the time does something else?



4) "why put it in macro if you want it to be the same as when you just click the ability." Your not, your ADDING OTHER CONDITIONS/ABILITIES to that original/unmodified ability, not adding the original/unmodified ability to a set of other conditions.



5) Your quite clearly doing it wrong, the reason the people who know macro;s are now here is because you are giving stupid, useless, and incorrect advice and information.