no i call it like i see it i mean lets be honest about what is happening because as you said MBers will simply find another method as which point complaints will spring up again and Blizzard will once again move the goalposts and make that way a violation and at this point they should just save a lot of time and effort and adopt an all or nothing approach make no mistake as i said i have no issues with multi boxing however enough people obviously did so Blizz should just go ahead and completely do away with boxing in any way shape and form and put the entire issue to bed once and for all itll be a lot less painful then to rip the band aid off quickly rather than try and slowly peel it little by little
Blizzard TOS is NOT A LAW, so it isn’t ILLEGAL to multi-box.
I don’t have any experience with WOW, and don’t care about boxing in that game.
Based on my personal experience with boxing in D3 years ago, it isn’t worth the effort. If the solo/multi-player rewards weren’t so skewed, multi-boxing wouldn’t even be a thing.
I like how you indicate a change to technology in the past decade as a catalyst. The technology and the software starmap, has very little to do with running client software from a global satalite. What a game client should do is gather information from the instances running, as they examine features of the star map. A radio telescope should be a dream jub, besides the information it gathers produces the map for hardware, or new technology. The older hardware may have been slower with multiple game clients, but there is a way for the background processes, to run very quickly. I am guessing this is about the ‘Gibson’ again.
The concept of a self improving supercomputer, is not a new idea, it has different emotions, that change the function of the software design. A literal nightmare for a software designer, because each emotion alters its code, with hundreds of binary lines of code that change how it identifies, other computer systems. What made a Gibson design different, is that it is a radio based program, that calls it’s own core from one of several remote radio boxes. No telling how many there are, or just what there shape is. This is the complex part of what networking systems could be doing.
It’s a reeeeeeeeeeeeeeeeally badly done Google Translate. Either that or he went into astronomy tangent. Either/or.
The bottom line in simple terms for those reading is this: You can still have multiple account open simultaneously. Not much they could or really will (yet) do about this as each account is a separate paid entity. The difference now, as opposed to before, is that the way you control those accounts must now change. You can no longer use software to send synchronized commands to the accounts at the same time. You must either manually switch between clients or use a hardware multicasting device with multiple separate computers. No more controlling them all at the same time on a single computer.
The irony here is that this actually returns “multiboxing” to its original definition. Back in the old day, it referred to running the same game on multiple computers (boxes). Back then you had to have hardware mirroring or at the very least a KVM switch that could accomodate the number of computers you were using at the time. That is what this is change essentially forces if you want synchronized control.
You can still have your multiple accounts. What you cannot have is synchronized control over those accounts when on a single computer. That’s the change. Unfortunately, the software that allows multicasting also has botting ability, and in order to eliminate the botting ability, the multicasting portion of that software becomes collateral damage.
Blizzard isn’t the one legitimate multiboxers should blame, but instead, they should be complaining to the software developer that added botting capability into their multiboxing software. Had they not done that, this might never have happened.
So once again, having multiple accounts in and of itself? Perfectly fine. Controlling them all in sync with each other on the same computer? No longer allowed. As long as you see that section “Allow multiple instances of Battle.net” in the Battle.net app, you’ll know that you can still have multiple accounts open at once. It isn’t supported, but it isn’t regulated either. You just can’t sync them all so easily (or at all) now.
Indeed. Yet it still hasn’t sunk in. The sky is not falling, you just now have to actually take the proper precautions against the sun as the clouds have been removed.
If anyone’s wondering, this is the type of activity that Blizzard is targeting with the EULA and Warden changes. You can clearly see in that video that a single click from the player results in formation perfect alignment. That’s full-on automation there, and what Blizzard has been trying to combat for years. But with that same automation software also being what simulcasts keystrokes and mouse input, they ultimately had no choice but to put an end to it.
Legitimate multiboxers aren’t like this. They just use the simulcast feature to play their characters in sync. Unfortunately, as I noted above, they’re collateral damage in this change. This is why we can’t have nice things, as it were. And yes, just one player doing something like this can cause insane damage to a server’s economy.
It’s different here in D3, but I would err on the side of caution on the chance Blizzard decides to take the easier route out and just bake this detection into all games so they aren’t dealing with multiple variants of Warden (maintaining multiple codebases is resource intensive).
The video in the linked thread is an extreme, to say the least, and statistically their numbers are tiny, but as we’ve seen with WoW Classic, it doesn’t take much to destabilize a game’s economy and world interactions.
I provided a link to the thread and not directly to the video in order to provide context. But this is what the input mirroring detection change is meant to put a stop to. And yes, it is sad that legitimate players are caught in the dragnet, but Blizzard’s hands are kind of tied on this one since the software devs put the botting features into the software used to replicate input commands.
I think until Blizzard says something specifically about D3, D3 players that use input key mirroring are safe. If warden detects a D3 player using input mirroring, they would not be banned unless Blizzard provided an announcement that applied to D3 or more broadly to all of Blizzard’s games.
If Blizzard was planning on instituting a ban on all of its game in the near future, I think that they would have announced it at once, rather than being narrow in their focus on WoW.
I suspect this change will not be applied to D3. D4 on the other hand could be different due to world events and Blizzard letting players know before purchasing D4.
That is not a safe assumption. The EULA applies to all Blizzard games and is really vague with regard to third party software.
It is very much an “at your own risk” situation. Blizz tends to have similar rules for all their games and refused to clarify D3 restrictions when asked on the CS forums. Orly intentionally did not step in and correct the answers that were given - which tends to mean they are correct.
Does warden or whatever they use to check offending accounts look for running processes or the actions of the accounts? I use ISBoxer but only for screen arrangement. The sync function is too clunky to use so I only use the software to navigate between windows to move my other accounts around. Just wondering if they’ll check for the software process and then assume you’re using the full capability or are they checking to see if all the accounts are moving at the same time?
Battle.net’s End User License Agreement is VERY CLEAR on such matters.
License Limitations. Blizzard may suspend or terminate your license to use the Platform, or parts, components and/or single features thereof, if you violate, or assist others in violating, the license limitations set forth below. You agree that you will not, in whole or in part or under any circumstances, do the following:
Cheating: Create, use, offer, promote, advertise, make available and/or distribute the following or assist therein:
cheats; i.e. methods not expressly authorized by Blizzard, influencing and/or facilitating the gameplay, including exploits of any in-game bugs, and thereby granting you and/or any other user an advantage over other players not using such methods;
bots; i.e. any code and/or software, not expressly authorized by Blizzard, that allows the automated control of a Game, or any other feature of the Platform, e.g. the automated control of a character in a Game;
hacks; i.e. accessing or modifying the software of the Platform in any manner not expressly authorized by Blizzard; and/or
any code and/or software, not expressly authorized by Blizzard, that can be used in connection with the Platform and/or any component or feature thereof which changes and/or facilitates the gameplay or other functionality;
The initial Blizzard post was very specific to WoW. Good corporate manners would be to make a similar announcement to all Blizzard games where this change is going to be adopted.
Fair is fair.
If this change is going into effect for D3 as an example, Blizzard should post a warning on the launcher/game to warn players once before the game client opens where there is an acknowkedgment box. Many D3 players do not check the forum let alone the WoW forum.
Brilliant!