As more runes get added the more it will be viable. More 3min cds you can weave.
polying somebody, swapping to healer runes, healing up to full, then swapping to mana runes getting full mana then swapping to frost runes and a different CD rune and popping new cds and blowing them up.
Maybe thats what blizzard wants, time will tell as people get geared and a meta gets set.
For Hunters it will be a thing even in PvE, since you can feign and swap gear in Classic.
Hunters and Rogues in PVE, just like gear swapping in fights was. Just another part of the game.
Yea, i could see it happening if hunters ever get any Cooldown around 30 seconds, POP Sniper shot, then feign death and swap sniper shot out with another Cooldown.
You are right I meant Runes not gear.
Yeah, I doubt theyâll remove macros⌠but there is some wild stuff you can do with them if you really get into the weeds. I write scripts for a living, and that would give me a huge advantage over regular players. I could make one button spammable macroâs that function like priority lists⌠kick bots⌠you name it.
Itâs basically cheating. I donât do that, cause I think itâs cheating. They definitely should remove macros and a lot of the / commands you can do â then if people complain about missing functionality they should incorporate features they want in the game to be accessible via the UI and intuitive for everyone instead of people trying to cheese the game.
You cannot do those things with normal macro functionality and the kickbot macro is a known exploit that will get you banned. letâs please not misrepresent macros or post about bannable exploits please. Macro functionality has been sanitized to such a degree that most people cannot do things over than simple macros, and the ones that work otherwise are exploiting bugs in the code.
Only if youâre using the exploits, which are bannable.
You absolutely can. Look up Gnome Sequencer. That is just one method, Gnome sequencer allows you to cycle through macros with a single key and treats each button press as if it were âclicking on a separate macro.â You can write all kinds of custom code for the addon to use as logic for how it determines which macro it âclicksâ on.
There are all kinds of things you can do. Between addons and macros, you can absolutely make single spammable button that does your rotation probably better than you can.
Thatâs an addon, not wowâs macro system.
GSE cant break the rules, but it can make them more manageable.
So no you canât. Next.
It is using WoWâs macro system in a way that it was never intended.
I see nothing in that addon that suggests what youâre saying it does, and IF it is a problematic breaking of the macro rules, then itâs a third party addon that should be removed.
He argues for the sake of arguing man
You can literally create a custom script that determines how to cycle through which macroâs to âclick.â
Each command in the macro it displays for you is itâs own Macro.
So you could sequence through abilities like:
1.) /cast ability x
2.) /cast ability y
3.) /cast ability z
You can add your own cast sequences to each individual macro if you wanted, so you can create your own conditionals.
You can add events that trigger before and after each macro.
Then you can determine the order of which those macros are activated â with the out of the box sequences, you can do basic simple things like activate in order 1,2,3 â or you can tell it to try 1,1,2,1,2,3 â you can also write your own custom code for the step functions, so it can use all kinds of scripting logic to determine how to iterate through each macro.
The whole point is to have a single button that you spam, that basically does your entire rotation. Itâs literally cheating.
Cast Sequence is already a macro. You can already make a cast sequence.
Thatâs not what a conditional is. A conditional is âIf X, do Y.â Conditionals have logic and requirements and most conditionals are disabled in the macro system. Which is why the kickbot macro is considered to be an exploit since it uses a method to bypass the restrictions that prevent using an if target is casting conditional.
You can do that with a cast sequence macro. Which is not cheating. You have no idea what youâre talking about.
No I just hate when people come to the forums and either lie about their reasoning when they canât defend their points (you) or lie about things that are pretty easy to check (him).
The difference here, is that the standard macro system does not allow you to bypass spells that can not be cast.
So you can not create priorities with standard macroâs.
Because this treats each ability as itâs own macro, and cycles through the macros â it will not get stuck on ability 2 because its on CD, it will move straight to ability 3 or whatever the step function logic dictates.
You donât need an actual if statement to create conditionals. Cast Sequence macroâs by default allow you to activate abilities via specific conditionals with limited [] inputs, such as harm, combat, dead @focus / etc. You can also dump these to null / reset on timers / status.
So you can easily do things like create conditions where something can only cast if the first ability goes off, but it skips the entire cast sequence macro if itâs already set to null via the step functions.
Yes but thatâs not doing anything outside what is possible in game. itâs not forcing through abilities that cannot be cast or breaking the GCD.
All your saying is that instead of getting stuck on the error at stack and terminating, itâs just passing the error and moving on to the next step.
Which is not cheating, conditionals, or anything else. It still canât do anything that you canât do as a normal macro function.
So weâve gone from âItâs a kickbot with conditionals!â to âWell, it just doesnât break stack at an errorâ which are two WILDLY different things.
Yes, you can do SOME conditionals. But not all. (Also Target=focus or target=GroupMember# are not conditionals) You cannot do macros that are based on whether your target is casting (requirement for a kickbot), specific buffs or debuffs on you or your target, whether a specific ability is on or of cooldown.
You can do form based macros, very important for warriors in Classic. But you canât do macros based on buff and debuff ids or other aspects.
Thereâs a very sanitized system to the current macros, unlike release wow. If this was release wow you would be 100% croeect, because original LUA was essentially the full coding with almost no restrictions.
The kick bot thing is something different, and itâs something you can incorporate into GSE.
It abuses run commands in a macro â Thankfully Blizzard is already investigating this kinda abuse:
This example is what people are using in Arenas to not cast spells if someone has the Grounding Totem buff.
/run for i=1,10 do local D = UnitBuff(âtargetâ,i); if D == âGrounding Totemâ then ClearTarget() end end;
By the same kind of logic, you can automate all kinds of other nasty things into your macros. Like what kinda debuffs they have.
I get that you really want to sound smart here, or maybe you actively use GSE and want to defend it. I dunno why youâre trying so hard to die on this hill.
The default macro usage is intended to allow simple automation â it isnât intended for you to replace your entire rotation with one button, which GSE actively allows you to do â the whole point is to bypass the limitations you run into when spamming one macro.
hunters gonna feign death and swap into what exactly? none of the runes are useful lmao
Correct. Itâs abusing a glitch where the conditional for casting was removed from most sequences, but people are able to force it through by invoking a different sequence. Itâs kind of like command injection. And itâs real dumb that Blizzard hasnât fixed it in 3 years since it was discovered. but itâs absolutely not intended.
I am smart, and no I donât use GSE. But thereâs a very big difference between claiming all macros are âcheatingâ and talking about the specific abuse of bugs in the code to bypass restricted macro conditions to create automation. You keep comparing GSE to literal issue with exploits to macro code that Blizzard hasnât fixed for whatever reason. (Iâm more mad at Blizz for being bad at fixing their content).
This is Classic. Your entire rotation IS ONE BUTTON. All a cast sequence macro in essence does is shortcut rolling your face across the keyboard. Be more mad at bad game design than cast sequences. Because cast sequences donât work for every class (shadow priests for instance) because their rotations are more complex than what normal cast sequences can do.
But I mean, we went from a macro that equips a different piece of gear to complaining that kickbots are an issue. You are LITERALLY BEING SO DISENGENUOUS IT HURTS.