Does this break TOS

[Barelan]

Its not about changing the caster, it's about changing the spell.

Maybe I should clarify:

In my current setup I use druid healer. I use Rejuvinate, Regrowth, Healing Touch.

I have different keys for each heal target (F8 = tank, F9 = hunter etc)

When I press the F8 key, it cycles through the spells (just like castsequence)

If I press F8,F9,F8,F10 then I get:

1) Rejuvinate on Tank
2) Rejuvinate on Hunter
3) Regrowth on Tank
4) Rejuvinate on Shaman

I hope this makes more sense.

We don't do anything that you can't do with a basic key broadcaster and complex macros. We just make it easier. That's our philosophy.

I would argue with your point about click spamming.

When you press the button you will get different actions based on whether the cooldown has expired. You can know this by monitoring the cooldown of the spell, but if you just mash the key, then I would argue that you don't really know what to expect. Our proposal behaves in exactly the same way. I would therefore propose that if you think that /click spamming is OK, then you should consider our proposal to be OK as well.

[Iceorbz]

So all your doing is /castsequence Rejuv, Regrowth, Lifebloom ? Theres nothing wrong with that I can see, seems like a bit much when you could just put that macro into the game but hey im all for more userfriendly and easier multiboxing. That's what keeps the community growing and makes people happy.

/click does not choose what spell to cast, its coded into the macro. It's not going to rely on the game to make a decision like /castrandom did. If your program is saying, hey 30 seconds has elapsed /cast rejuv on the next keypress that would be wrong.

[Barelan]

So all your doing is /castsequence Rejuv, Regrowth, Lifebloom ? Theres nothing wrong with that I can see, seems like a bit much when you could just put that macro into the game but hey im all for more userfriendly and easier multiboxing. That's what keeps the community growing and makes people happy.

/click does not choose what spell to cast, its coded into the macro. It's not going to rely on the game to make a decision like /castrandom did. If your program is saying, hey 30 seconds has elapsed /cast rejuv on the next keypress that would be wrong.

The only difference is that the count is per key, rather than castsequence where the count is global.

No the program is not doing that. Basically the new feature is designed to emulate /click functionality, just make it easier (my brain hurts when I read the /click spamming threads!).

My concern really is whether /click spamming is an exploit. I don't really accept the argument that because the functionality is included in the UI, that blizzard sanction any possible use for it. I think that the extra commas are being used to work around the "no timers" rule.

if you mash the key at a given speed, and then cast spells based on the number of "ticks" then thats timed spell casting. The only argument is that the tick for the timer comes from the user. The fact that you can set up an entire attack (tanking, DPS sequences and healing) on one key really sounds like automation.

My problem is that if /key mashing becomes the way to multibox (and I personally hope that it doesn't) then, as a software supplier, we need to keep up with current practices.

[shaeman]

Its not about changing the caster, it's about changing the spell.

When you press the button you will get different actions based on whether the cooldown has expired. You can know this by monitoring the cooldown of the spell, but if you just mash the key, then I would argue that you don't really know what to expect. Our proposal behaves in exactly the same way. I would therefore propose that if you think that /click spamming is OK, then you should consider our proposal to be OK as well.

It doesn't matter whether folks here think /click spamming is okay or not - it's blizzard's opinion of what is against their terms of service that is important.

Given their stated position on macros performing the conditional logic for the user (castrandom change) I think we will see a change to either castsequence or /click that will stop the /click spamming method (but that's just my opinion).

At that point this functionality would definitely be against their terms of service (in my opinion) up until that time it would probably be okay....... (probably).

But who knows - maybe blizzard won't like the idea of an explicit timed delay being used to provide conditional logic.

Personally I won't even /click spam so feel free to write me of as a paranoid nut