[Quick Showcase] My No Broadcasting No ATG Setup with 1 Warrior, 3 Hunters, 1 Priest

https://www.youtube.com/watch?v=2203...ature=youtu.be

I put this new setup together in about 30min. It's obviously very rough and very limited and can most likely be improved a whole lot even without any broadcasting or ATG. I went on the most dead population Classic realm that I could find (to avoid player interactions), started a fresh new ISB toolkit and a fresh new character set with "Disable capabilities to control multiple windows simulataneously, including Broadcasting and Action Target Groups (EVE Online)" checked, and I gave it a go.

My point was just to show you guys: please do not give up, this is still possible. I am using video FX with GSE2 macros to assist my warrior's target with the hunter and cast Auto Shot. And I am using EMA to auto-follow. Ebony (the EMA addon dev) said she was working on a way to integrate /assist in EMA as well. Besides, if I put this together in 30min as I said, even what Lax and the rest of the team can do.

The team comp is Prot Warrior Tank as the piloting client, 3 BM Hunters and 1 Holy Priest that I will use to heal with VFX + the Zperl addon UI and [@mouseover] GSE2 macros. The idea is to use mainly Auto Shot to have to rely on VFX as little as possible. With GSE2 macros you can use /petattack and /assist and /cast Auto Shot and even activate trinkets, all at the same time.

I know that as soon as the ISB team has a better idea of what the Blizzard Warden detects exactly, they will make the appropriate changes and do everything they can to ensure that we can still multibox the game to some extent. Do not lose hope. We may feel like criminals in hiding at the moment, but this is not the end of WoW multiboxing. In fact, the setup that I have got going on here could probably already clear five-man dungeons relatively easily with the right gear.

Blizzard hit us pretty hard but we'll be right back.

What you are doing is broadcasting one button from one window to another and using isboxer to do so.

Banhammer.

Isboxer is not going to do anything it takes for isboxer to do not be detected, they are and will never go against Blizzard ToS.

Quote:

---

Originally Posted by Braxtar

What you are doing is broadcasting one button from one window to another and using isboxer to do so.

Banhammer.

Isboxer is not going to do anything it takes for isboxer to do not be detected, they are and will never go against Blizzard ToS.

---

There is no broadcasting occuring here though, as far as I understand. It would only be broadcasting if the key I press in the vfx window was broadcasted to any other client than the one for that vfx window.

Quote:

---

Originally Posted by dustofoblivion

Quote:

---

Originally Posted by Braxtar

What you are doing is broadcasting one button from one window to another and using isboxer to do so.

Banhammer.

Isboxer is not going to do anything it takes for isboxer to do not be detected, they are and will never go against Blizzard ToS.

---

There is no broadcasting occuring here though, as far as I understand. It would only be broadcasting if the key I press in the vfx window was broadcasted to any other client than the one for that vfx window.

---

I agree that clicking/typing in a VFX isn't broadcasting to multiple game clients so not outside our new understandings of the ToS changes.

Where I have my concerns is that the software in it's current state still allows/enables broadcasting and thus it may make it to where we may have to prove we are not broadcasting (or that they may just assume we are).

The safest option would be to not use ISboxer in it's current state and instead use a different setup and I don't know the best option(s) and not sure I want to continue like that.

The next safest option may be for there to be an ISboxer version that has no broadcasting ability at all in the tool so there is no question. Alternatively ISboxer could be made to not allow broadcasting when handling WoW clients...

Otherwise we are back to "on our honor" to not use the broadcasting feature(s) and potentially having to prove a negative... If you continue using ISboxer "as is" it may be wise to record and keep all of your sessions to be able to prove/show you were not violating ToS... Not sure even that would matter as they may not be willing to take the time to review anything anyway...

In the end we may be making lots of assumptions that may or may not be valid... I think this was mainly initiated due to a scenario rampant on retail that isn't viable here so maybe we getting ahead of our skis some...

You'll get banned for this as the Isboxer is injected into Wow.
Once they detect it, automatic ban (or warning priorhand).

Quote:

---

Originally Posted by Peregrine

You'll get banned for this as the Isboxer is injected into Wow.
Once they detect it, automatic ban (or warning priorhand).

---

Source? The ISB team themselves don't know at the moment if Warden will be detecting Innerspace or something else.

Quote:

---

Originally Posted by Peregrine

You'll get banned for this as the Isboxer is injected into Wow.
Once they detect it, automatic ban (or warning priorhand).

---

We should not be making sweeping declarative statements unless we work at Blizz or have clarification from Blizz.

There is nothing definitive yet and LAX has asked for some details & clarifications.

The statement clearly said:

"We will soon begin issuing warnings to all players who are detected using input broadcasting software to mirror commands to multiple accounts at the same time (often used for multi-boxing). ... warnings will escalate to account actions, which can include suspension and, if necessary, permanent closure of the player's World of Warcraft account(s). ..."

Nothing demonstrated above involved anything to "mirror commands to multiple accounts at the same time"...