Hi,
I’m a multiboxer who hasn’t posted anything on the AH in years, frequently just levels up characters for fun when there is a lull in content, and is willing to (just as every other Multiboxer here is) take any question you might have and form constructive dialogue around it.
Edit for clarification: also haven’t raw gold farmed at any point and I don’t have millions of gold sitting around somewhere.
Yes but they could have stopped it before it became a big deal. I mean, i would want to stop something before it began to become a bigger problem. I mean, I would. It was useful back then, but now more and more players are abusing it. I would of stopped it at the source before it became really bad. That is just me though.
Really? I’ve been killed by multiboxers or blocked from spawns maybe 4 or 5 times total? I’ve had one truly “bad” experience with a 40 man MB bg team that just sat in the throne of isle of conquest. Once, ever.
Never been corpse camped by a multiboxer*. Never had a multiboxer* wipe out a low level quest hub over and over and force me to forgo enjoying WoW with my free time for the day. Never been blocked by a multiboxer* camping a WQ all day. Yet a small number of single-box players seem to love passing the time like this.
Turn warmode off? Yup, been griefed by my own faction too—plenty of exploits and non exploits to accomplish this—never by a multiboxer* though.
I’m perfectly happy to concede that my data is one point just as any other individual posting here, but there is a big distinction between bot/automated multiboxing and us nerds sitting at a keyboard figuring out how to optimize our team and trying to help out people when we see them doing the same quest as us. (Yeah, believe it or not a lot of multiboxers are well aware of how multiboxing affects things like mob tagging and node mining for other players and actually play around letting other players get tags or node clicks before they go in.)
*I actually play single-box with the majority of my time, so no, the reason I don’t get griefed by multiboxers isn’t because I have my own team to defend me.
That said it isn’t that they are banning the use of third party input broadcast software in their game that concerns me.
What concerns me is their method of “detecting” input broadcast software in use and whether or not that detection process involves reading in memory processes on the client computer.
But the aspect that bothers me the most is that any true software process detection (as opposed to something like server side examination of map geography and client density per IP connection which would be perfectly legitimate means to determine a multiboxer) would need to access memory on the client. We have been down this road before and Terms of Service are void where such Terms of Service might impinge upon criminal or civil statute. Just because it is in the Terms of Service does not make it okay for Blizzard to violate the law nor does it absolve Blizzard Entertainment of responsibility in those cases. Also since such input broadcast software is not unique to Blizzard Entertainment and can have other purposes to which it is being used legitimately, and companies being who and what they are (prone to mistakes) false positives are more likely to occur. If they do occur then the account(s) holder is harmed and would have grievance that would need to have a remedy so that the account(s) holder can be made whole (yeah yeah appeals process blah blah not good enough sorry there is a good reason these laws exist and a really good reason why Warden was found to be overly intrusive).
So either the Blizzard Entertainment policy would be intermittently enforced (what was that about arbitrary and capricious?) Would potentially violate several federal statutes regarding electronic communications, or would be unprovable in any legal forum including arbitration (any evidence admitted by Blizzard other than testimony from credible witness would not be admissible and the credible witness would have no way of testifying that the software being used was not being used for other legitimate purpose) or all three. It also could have the unintended consequence (again depending on the manner in which the software detection was done) of causing destruction of legitimate in process software use and could if incorrectly programmed or programmed in bad faith end up acting like Extended Copy Protection (XCP) or MediaMax CD-3.
I don’t know about anyone else but I really do not want Blizzard Entertainment mucking about beyond the boundaries of the WoW.exe on my computer. If the only way to prevent that is not agreeing to the terms of service (when it gets updated) and to stop playing WoW altogether then I would be sad but I would rather be sad and not have my hardware or software compromised than to be happy and have a brick for a pc. World of Warcraft is far down on the list of things I do with my computer and does not (in my universe) rate the privilege necessary to scan volatile RAM or inspect files or any other sort of intrusion into my private domain.
Now I could be totally misinformed about how they plan on implementing such detection and if I am good! Good Riddance to Multiboxing! But if I am not misinformed and this detection process does cause harm what then?
They have been but the manner in which they did it originally was forced to be changed by the outcome of several trials, and a couple of national newsmaking scandals:
…" The Warden’s reliability in correctly discerning legitimate versus illegitimate actions was called into question when a large scale incident happened. This incident banned many Linux users after an update to Warden caused it to incorrectly detect Cedega as a cheat program. Blizzard issued a statement claiming they had correctly identified and restored all accounts and credited them with 20 days play. Warden scans all processes running on a computer, not just the game, and could possibly run across what would be considered private information and other personally identifiable information It is because of these peripheral scans that Warden has been accused of being spyware and has run afoul of controversy among privacy advocates." -Wikipedia entry on Blizzard Entertainment Subheading Warden Client
I feel while i agree with this overall post. The truth of the matter is that with multiboxing, it is a very useful thing for those players and forcing all of them to just give it all up, I mean, the multiboxers are not going to give up on this easily. Blizzard is in for something else later on, especially considering how long multiboxing has been optimal and useful for these players, and how controversial warden has been over the years. It would be like telling everyone in america to give up their cars because the components of cars that have been around for a while cause cancer or something like that. Not exactly the same as multiboxing, but imagine how difficult this would be to do.
Same thing with twinking, but twinking isn’t useful, people just enjoy it. Granted you can still enjoy it, but in a different more contained way. It has a similar stigma of explosive annoyances from both sides of the community. So instead of enjoying it the way they were and continuing to enjoy it this way, they were told they had to enjoy it in a different way, and no one really wanted to.
So for blizzard, if anything, it is only going to stymy the issue. Guaranteed folks will find ways around this that won’t be detected by warden or other players. It is pretty difficult to let anything like this go on for so long and then all of a sudden just make it more difficult. In this case, a ton of responses mention other ways of multiboxing. If not system, what about hardware? This won’t go over well for blizzard, that much i can assure.
I feel the official stance is fine, but it should have been added as a stance before it became a huge problem. Like in 2006 or somethin. Same thing with twinks. Should have had that added in like 2006. Only the .5 percent of vanilla naxx players would even remember multiboxing or twinking being a thing. Blizzard waits way to long to enact anything like this.
“The developers are actually pretty impressed with what multiboxers are able to accomplish. There is nothing wrong with it, so long as you don’t automate anything.” - me chatting with Blue, in game, ~2016
Build a better mousetrap and nature builds a better mouse. I’d say that concept is pretty well universal. Even now the ability to multibox without detection by a software program exists Especially if you have at your disposal a virtualized environment. One keyboard, One button, One action, across 2/4/8/16/32/64 vm’s (with a slight input delay of a few ms (5 to 10ms) and the software has to stay within the guest OS so it cannot even see the other processes. Now what? Blizzards going to ban virtualization? Umm…
From my perspective, that quote is from a gm in 2016. It is likely the meaning of the quote wouldn’t reflect the new multibotting stance blizzard has now. It would require the actual definition of automation, and anything found to be within that definition would be illegal now. I am sure there are ways that aren’t automating, but blizzard will probably say it does fall under that category. That is the other problem with the new stance is that it is to broad.