Is this allowed?
I've started to get to know ISBoxer over the last week or so, and I'm having a lot of fun with all the features for my wow boxing teams. It's really a powerful piece of software, and I've probably only tried out about 10% of it, or at least that's how it seems right now.
I have one question though; Are all the functions of ISBoxer that you can implement, especially for a wow boxing team, 100% allowed? I'm thinking about two things in particular, the steps feature and the part where you can delay between two steps.
I remember we used to be able to make pretty powerful macros in wow using castsequence. The castsequence command used to function so that if a skill couldn't be executed in turn, for example if it was on cooldown or the right conditions weren't met, the macro would just go on to the next skill in the sequence.
Blizzard changed it to the state we have now, which is so that a castsequence macro gets stuck on whatever skill is next until it can be cast. Until then, it just sits there doing nothing until reset and/or the right conditions are met so the skill can be cast. The line '/castsequence Arcane Blast, Arcane Missiles' would never go any further if the AM proc didn't happen on that first AB.
However, it seems that with ISBoxer we can circumvent this change, using steps. With steps and calls between dps key maps, you can construct a one key click that executes whatever skill is available when it becomes available, a behavior that seems to me Blizzard wanted to avoid.
The other thing, the delay between the steps executing is something we used to accomplish by inserting commas in a castsequence. You used to be able to insert enough commas in a macro so that each click you did to step through the commas would time the macro to other macros for example. '/castsequence skill1, , , , , , , , , , , , , , skill2', where skill2 would execute after a delay determined by the click speed of the macro user.
This was also changed by Blizzard, as all macros now ignore whichever number of commas we put in them. Also something that ISB allows through the delay between step executions.
Is this something to be concerned about?
I have one question though; Are all the functions of ISBoxer that you can implement, especially for a wow boxing team, 100% allowed? I'm thinking about two things in particular, the steps feature and the part where you can delay between two steps.
I remember we used to be able to make pretty powerful macros in wow using castsequence. The castsequence command used to function so that if a skill couldn't be executed in turn, for example if it was on cooldown or the right conditions weren't met, the macro would just go on to the next skill in the sequence.
Blizzard changed it to the state we have now, which is so that a castsequence macro gets stuck on whatever skill is next until it can be cast. Until then, it just sits there doing nothing until reset and/or the right conditions are met so the skill can be cast. The line '/castsequence Arcane Blast, Arcane Missiles' would never go any further if the AM proc didn't happen on that first AB.
However, it seems that with ISBoxer we can circumvent this change, using steps. With steps and calls between dps key maps, you can construct a one key click that executes whatever skill is available when it becomes available, a behavior that seems to me Blizzard wanted to avoid.
The other thing, the delay between the steps executing is something we used to accomplish by inserting commas in a castsequence. You used to be able to insert enough commas in a macro so that each click you did to step through the commas would time the macro to other macros for example. '/castsequence skill1, , , , , , , , , , , , , , skill2', where skill2 would execute after a delay determined by the click speed of the macro user.
This was also changed by Blizzard, as all macros now ignore whichever number of commas we put in them. Also something that ISB allows through the delay between step executions.
Is this something to be concerned about?