This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Classic Theme
Thottbot Theme
Maybe Bliz needs to revisit some of their booleans...
Post Reply
Return to board index
Post by
RedwoodElf
So how is
/cast <spell that will fail if the target is a non-mana-user>
/cast <other spell>
any different than your example, if you had available?
And I doubt very much you really WOULD put a /use Parachute cloak (or /cast Slow Fall for that matter) on all your macros, due to the (as I mentioned before) "locks out all other functions of the macro" factor, not to mention the "I really want to waste 30 characters on every single macro in my list" factor, considering how many of my macros are already 250+ characters.
Falling, of course, would evaluate to true even if you had Slow Fall or Parachute cloak active, since booleans don't check for buffs. would be the equivalent of in macrospeak.
As a computer programmer, I am quite aware of what "automation" is...you're just using a non-standard, non-dictionary definition,which is imprecise and inaccurate. Like calling an Apple an orange, because you use the word "orange" to refer to all fruit. (a somewhat extreme example, but it is to demonstrate WHY I don't trust the word "automation" in this context)
I like to be precise, particularly when discussing computer issues like programming macros.
Post by
Wanderingfox
because the logic is different in each case.
You can still cast a mana drain on a hostile unit, it just might not work
if the target has mana
. You can't cast a heal on a hostile target
at all
. The difference is that the first one is going "can I cast this spell on this target? Yes. Ok, does that target have mana?" while the second one is just saying "can I cast this spell on this target? No.". Does that make more sense? Is it a minor difference? Yes, but it's where the so-called line is in regards to what can and what can not be done with macros, or at least that is where the line has been drawn in the past.
is not like , it's like . It's true if you're in a certain state of movement (flying, swiming, running), and false if you're not. The difference is that swimming doesn't really have a possible exploit that would allow someone to prevent a death simply by hitting a macro.
1. I'm a comp-sci major. I know how to program, and I have been programming, both as a hobby and as a job, for almost 12 years now.
2. I copied the definition of the word from google's define: operator. Just to be absolutely positive I'll give you another quote from a reputable dictionary along with a link.
Automatic:
2: having a self-acting or self-regulating mechanism <an automatic transmission>
source:
http://www.merriam-webster.com/dictionary/automatic
3. WoW macros aren't exactly programming. If you want to be technical, they're scripting at most. XD
4. You knew exactly what I had meant the first time I had said it, you're arguing the point for absolutely no reason :P
Post by
RedwoodElf
because the logic is different in each case.
You can still cast a mana drain on a hostile unit, it just might not work
if the target has mana
. You can't cast a heal on a hostile target
at all
. The difference is that the first one is going "can I cast this spell on this target? Yes. Ok, does that target have mana?" while the second one is just saying "can I cast this spell on this target? No.". Does that make more sense? Is it a minor difference? Yes, but it's where the so-called line is in regards to what can and what can not be done with macros, or at least that is where the line has been drawn in the past.
Acutally, I think you meant "if the target DOESN'T have mana." - however, last time I used mana Drain on a target that wasn't a mana-user, I got an "invalid target" error, at least I think I did.
is not like , it's like . It's true if you're in a certain state of movement (flying, swiming, running), and false if you're not. The difference is that swimming doesn't really have a possible exploit that would allow someone to prevent a death simply by hitting a macro.
Gee, so there are no water breathing spells in the game that could be triggered by the boolean? I'm pretty sure that
/cast Unending Breath
could most CERTAINLY prevent a death "by simply hitting a macro" if you're underwater.
Post by
Wanderingfox
The error message is the same, where it fails is different.
If CanCastOnTarget Then
If TargetHasMana Then
SpellCast
Else
Invalid Target
End If
Else
Invalid Target
End If
The innermost invalid target is triggered by drain mana on a unit without mana, the outermost one is triggered by a healing spell on a hostile target. Doesn't seem like a big distinction, but keep in mind this is incredibly simplified. The similar bit of code inside of WoW is infinitely more complex. The difference between where it errors is the difference between something not even being tried, and something being tried and failing. I'm not sure if there's a better way to explain it than that.
Anyway, there is a rather distinct difference between something like /cast Unending Breath and /cast Slow Fall. The UI gives you 4 minutes to cast unending breath, and then another 60 seconds on top of that. You KNOW when you're going to start drowning. The UI tells it to you. There isn't any advantage to simply making a macro so you can cast it faster. You DON'T know when you're going to be falling (yes you know in some cases, but not all of them, and that's an important distinction). That means there is a distinct advantage to using the macro conditional, and that is the kind of thing blizzard has been trying to avoid.
Like I mentioned in my previous post, it's right on the line, and I could easily see Blizzard changing their policy to include it, but under their current thinking, it's a step too far towards the game client running the game for you.
Regardless, this whole discussion is moot. The conditional doesn't actually exist, so there's no sense in arguing over its use. Perhaps you'd have better luck seeing them implemented by posting in their suggestion forum :P
Oh, and I think you meant this: /cast Unending Breath
Swimming only checks your status, your macro basically says "If I'm swimming and my target is friendly cast unending breath, otherwise cast unending breath on myself (regardless of if I'm swimming or not)"
Post by
RedwoodElf
Oh, and I think you meant this: /cast Unending Breath
Swimming only checks your status, your macro basically says "If I'm swimming and my target is friendly cast unending breath, otherwise cast unending breath on myself (regardless of if I'm swimming or not)"
Actually, that was as I intended...it's for use when I and a teammate are both swimming for a prolonged period, for use from my main actionbar. If he's jumping in the water without me, I probably won't be in range to cast UEB on him when he runs out of breath anyway. If I need to cast it before we jump in, I just manually trigger it from my sidebar.
Post by
Wanderingfox
Oh, and I think you meant this: /cast Unending Breath
Swimming only checks your status, your macro basically says "If I'm swimming and my target is friendly cast unending breath, otherwise cast unending breath on myself (regardless of if I'm swimming or not)"
Actually, that was as I intended...it's for use when I and a teammate are both swimming for a prolonged period, for use from my main actionbar. If he's jumping in the water without me, I probably won't be in range to cast UEB on him when he runs out of breath anyway. If I need to cast it before we jump in, I just manually trigger it from my sidebar.
Then why put it there at all? Why not just do /cast Unending Breath
Post by
RedwoodElf
Actually I noticed some typos in there. And it's just the first line of the macro (was typing in a hurry)
/cast Unending Breath
/stopmacro
/use Dreadsteed Of course, I'll have to edit it now that mounts can swim. My Warlock isn't high enough for a flying mount yet, so this macro will eventually change a lot.
Post by
Wanderingfox
Ah OK, that makes a ton more sense XD
Post by
RedwoodElf
So here's my current Parachute Cloak macro:
/equip Parachute Cloak
/stopmacro
/use parachute Cloak
prevents the macro from accidentally dismounting in midair. Parachute Cloak only lasts 10 seconds and has a 30 second cooldown, it is quite easy to be too far above the ground for a safe landing. (Another reason why wouldn't be a cure-all as you seem to think...you still have to hit the macro at the right time)
Post by
Wanderingfox
Because it's not just the parachute cloak that you could use it with. Levitate and Safe Fall both have much longer durations and no need to equip things. You could very easily roll them into macros that have nothing to do with falling so that you don't have to even think about it.
Post by
RedwoodElf
Isn't safe fall a passive ability? Pretty sure you don't have to put that one in a macro. :P
Maybe you meant Slow Fall?
Post by
Wanderingfox
Ya sorry, I was buying my second set of rogue minor glyphs when I was writing that. Freudian slip >_<
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.
