Printable View
The primary difference being I can accomplish the cast sequence I described 100% within the wow interface language and I cannot accomplish what you describe that way.Quote:
Originally Posted by Barelan
Blues have stated many times that if you can accomplish it within the native UI you are most likely safe to replicate the functionality elsewhere.
we might seem like experts on what Bliz is going to say is or isn't valid TOS but we aren't.
Go to the wow forums and ask for a blue post on what your are proposing.... then you have it from the only people who matter on the subject.
Actually you are mistaken if you think Blues matter. Policy is set high above them and handed to them. They won't have an answer to a question like this so they won't answer it any more directly than we are here.Quote:
Originally Posted by Catamer
It all boils down to the golden rule - do you FEEL it's going to get you banned. If so, don't do it.
Short version - I would think that violates the TOS.
From a philosophical point of view:
"an explicit timed delay being used to provide conditional logic". - as soon as you are supplying logic to the game using a 3rd party application, you have violated the TOS.
"The only difference is that the "clock tick" is provided by the user rather than the system. I personally feel both are automation but if other people feel differently then surely our proposal would be ok as well. " - The big difference is that the timing is provided by the user - not the system. Sure it's a fine line, and blizzard may well decide that the current /click spam isn't correct either. But as soon as you supply that timing outside the game, then I think you are in violation. I can appreciate your argument that all you are trying to do is the same thing that /click does, but you are specifially building in a pre-set timer.
From a CYA point of view:
Blizzard can (and does) occasionally ban people from using an "in-game" exploit. I'm sure you can find a few examples on the forums from people that felt that were only doing things Blizzard had already built into the game. But those cases are pretty rare. I'd guess 99.999% of the time Blizzard just fixes the "exploit" if they were the ones that caused it in the first place. Overall if you look at all the bannings that Blizzard has done since the game came out. I would guess 99.999% of them were from someone using a 3rd party application. I think if you built this logic into your product you would be subjecting your users to possible banning.
I already think that castequences used for timing crosses the line and blizzard will eventually fix it. The differences with the /castsequence method is that it is achieved 100% with the default UI so it is unlikely that you would get banned for it without warning. Using a program to do this is a big no no. Fairly sure that you can even find blue posts where they specifically forbid delays in3rd party software eg g15 software and scripting programs eg HKN and AHK
The /Click Castsequences is entirely done within the Blizzard default UI. Sure you can use Macaroon, to make a really long macro, with all the sequences in one macro, but its still the default UI which is letting you do this.
When a program will set the timing for you, and (on a keypress) decide based on its timing which spell to press, that's a very grey area, in my opinion.
I'd personally go with something like an interface within the program.
This interface allows you to choose which spells are cast, when they are first cast, and a delay until they're recast.
The program then inserts the correct number of comma's into the click castsequence, based on your spam speed.
Maybe it has a section in the "Click Castsequence Wizard" where it asks you to spam a keystroke at your pace, and then it uses that to determine the comma's required for timing.
Maybe the program can monitor your spam speed, and out of combat adjust the number of comma's so the timing is correct.
This would then be a very quick and easy way to configure a click castsequence.
But at the same time, it wouldn't provide any functionality beyond the default UI.
And the program would not be timing anything for you.
To clarify he's not talking about a delayed send.Quote:
Originally Posted by Whowantstoknow
He's talking about a key that sends F1 when you press it the first time and each successive press for X seconds sends F2.
This is still an implied delay here. You can not replicate this using the default ui but I can easily replicate this using a g15 or a script.
Just taking a small step back from this to look at it in a broader perspective without worrying about the specifics as much.
Firstly, does it violate the ToS to create a 3rd party application that duplicates the exact macro functionality available in WoW? Not an addon that extends it for longer macros but an exact copy.
Secondly, does it violate the ToS to create a 3rd party application that duplicates AND extends the macro functionality available in WoW?
Blizzard have already come down on certain third party applications and I think that making a '3rd party macro system' would get you into trouble in the long run.
Everyone has their own viewpoint but I was highly dubious about the replacement of the castequence macro at the start of the post even before I saw the timed thing.
To me a multiboxing program should stick to sending keys and mouseclicks, not venture into macro functions.
The "IF" part is the part that breaks it for me.