NOPE ,Coalition & Worldbosses... a story of breaking rules!

[Nikoru]

The Emerald Dragons won´t be a thing of guildalliances killing them. It more about the Hordeworldchat vs./feat. The Chinese vs. the Allianceworldchat vs./feat. The Chinese

[Aslan]

FWIW you can use the game API to perform non-action commands after a pause (supermacro has this functionality with the "/in" command, which draws on the Blizzard API). Blizzard removed the ability to use this for character actions partway through vanilla (I used a macro to automatically rebuff myself with thorns when leveling on retail). Also, there is another API command to recognize if you target a mob exactly by name, which you can use to conditionally send an "Azuregos is up" chat message, for example.

Because "/target" and chat commands aren't considered character actions, you can still use "/in" to repeatedly target a mob and send a conditional chat message with the 1.12 API (remember those annoying countdown "pulling" macros from vanilla retail?). That said, your character will still go AFK eventually if you don't move around a bit.

I guess my point here is that targeting a mob and sending a chat message don't require player input under the Warcraft API, and there's no evidence that these players are AFK botting instead of just moving once every 15 min. That said, I'm not convinced the GM staff on here actually understand what can be accomplished with in-game macros (as opposed to external programs or hardware), so it's possible they'll get banned anyways.

I guess its more of a multibox issue though, the addon/command itself.. why would it be bannable, GM's used to ban a friend of mine for a teabag macro which repeatedly toggles sit/stand without any player input, they thought it would prevent you from going afk (I guess ye.. they dont know whats possible =P), but after clearing things up he was unbanned.
In short: Is prolly a multibox issue, having a 2nd laptop next to your pc attached to some VPN to conveniently whisper your main if the WB spawns.

[dustinfll]

deleted

[Ghostly]

I applause you Keala, this is really well-gathered and thought-out evidence.
I, for one, hope that this will compel Nostalrius staff to take real action against real offenders, not just the throwaway accounts they hide behind.

[arOo]

Don't even know how I could stand thru reading the post of OP;
you described the mechanic of these spies pretty accurately now what if I tell you this is all within the limits of the WoW API and no "botting " has to be used.

The only thing you can most likely bust those players for is multiclienting(which is ulimitately a joke, but against the ToU).

[dustinfll]

Deleted

[Dreez]

there's a good reason why blizzard removed API functions in later expansions (/moved them to secure code)

[Charizard]

who needs bots when you know the spawn timer

/wink

[thargo]

I'm pretty sure I debunked this entire thread.

I would not say that yet.

Your video does not erase the OP's videos/screenshots. They still exist and raise questions.

Your video shows that the spawn timer was known. In the case of a server reset/crash however, the spawn timer is often messed up for some mobs. Which brings us back to the botting/multiboxing issue.

[Imbaslap]

Actually this is how we target, pull and notify the guild that azuregos is spawned.

http://www.twitch.tv/frz_wow/v/34695943

that nerdgasm