![]() I think it's funny that even within the wowlazymacro post telling people that may be over the line, there's other users talking about what timing they're running at, what is optimal, and justifying why they think it should be OK. Having any sort of tool that repeatedly spams a command (whether it does that by you pressing and holding a button, or by using a toggle on/off fundamentally breaks Blizzard's 1 keypress = 1 action mantra. 200MS (poor notation BTW - millisecond is most commonly abbreviated as "ms") is just another way of writing 0.2 seconds. Yeah, MS in is the millisecond delay that they've programmed - i.e. (Basically MS is the speed at which people are “pressing” the button that the macro is bound to) "unlock" functionality), then it's perfectly fine. So, the consensus is going to be that if you can download an add-on from one of the standard add-on sites, and it doesn't require an additional, external program to run (i.e. If Blizzard didn't approve of it, then they'd break some functionality that it relies on, like they've done to other add-ons in the past. It isn't against the rules of the game to use an add-on that functions entirely within Blizzard's Lua sandbox for World of Warcraft, and GSE has been around, in some form, since, at least, Legion. I'm thinking back to how Blizz broke their own /castsequence behavior back in BC or WOLK - it used to be possible to optimally program your complete rotation in /castsequence, so Blizz changed that to halt when it encountered something on cool down. Specifically, including timing into macros has long been verboten and it looks like GSE alters the default /castsequence behavior also. But it seems like a few of their options are against ToS - they add functionality into your macro's that does not exist in game. ![]() I was looking to improve my macro setup and someone suggested GSE and. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |