logo
allyourlawarebelongtous.com
    •  
    •  
    •  
    •  
    •  
    8
    Mar

    Glider Crashes After Running Into Blizzard

    Posted by David Rodrigues | (2) Comment

    Are you procrastinating on your assignments because you spend your time playing World of Warcraft (WoW)? Are you one of the many WoW players that dedicate 21-22 hours a week playing the game? Imagine a scenario in which you can have your cake and eat it too! Envision yourself leveling up while researching an assignment or socializing! Thanks to Michael Donnelly, founder and sole member of MDY Industries LLC, you can do exactly that! If you have $15 to $25, you can have Glider, a bot, play WoW for you and you can have your life back! Once installed, Glider will do all the work for you! No need to worry about Warden, Blizzards robot that detects bots. Glider simply circumvents Warden, allowing Glider to enhance your playing experience! Unfortunately, monthly subscription fees must still be paid to play. WARNING: Consequences of using Glider include: permanent bans on your user account, contract damages and/or injunctions by Blizzard Entertainment.

    The situation above is real. Many WoW users gladly paid to enjoy the benefits provided by Glider, even though Blizzards End User License and Terms of Use explicitly state that users cannot use bots. Blizzard sued for an injunction against MDY to stop the distribution of Glider as Blizzard considered the use of bots cheating which degrades other users WoW experience, which in turn could lower the amount of monthly fees Blizzard collects from users.

    Blizzard claimed vicarious infringement of their copyright. To establish this claim Blizzard had to demonstrate copyright ownership and a violation of one of its exclusive rights by Glider users. Here, MDY may be liable for contributory infringement if it has intentionally induced or encouraged direct infringement by Glider users. However, to establish secondary infringement, Blizzard must first demonstrate direct infringement by the users.

    MDY conceded that Blizzard is the copyright owner. The circuit Court then examined whether users are licensees or owners to determine what would constitute infringement. Applying the test established in Vernor v. Autodesk, 621 F. 3d 1102 (9th Cir., September 10, 2010), the court concludes that users are licensees, and that these users may infringe a copyright if their usage is not within the scope of the license.

    However, MDY argued that Section 4 of the Terms of Use, which provides that a licensee will not “create or use cheats, bots, ‘mods’…”, is a contractual covenant and not a license condition. A breach of a covenant, or a contractual promise, is actionable only under contract law while a breach of a condition is actionable under copyright law. The circuit Court determined that Section 4 of the Terms of Use was in fact a covenant. Thus, the Court concluded that although a Glider user violates the covenants of Blizzards agreement, they do not commit copyright infringement because Glider does not infringe any of Blizzard’s exclusive rights. The Court further elaborated that to constitute copyright infringement there must be a nexus between the condition and the licensor’s exclusive rights to the copyright. Since players do not commit copyright infringement by using Glider, MDY is not liable for secondary copyright infringement.

    This is a potentially frightening conclusion for game developers. To effectively prevent widespread use of cheats, bots or mods, a developer would have to target each user utilizing or creating these mods or bots and terminate their service. This type of punishment is far less consequential than those offered by US copyright law.

    So what is a developer to do? Since many MMORPG are funded by monthly access fees and not solely by game sales, MMORPG developers need to find a balance between the cost of monitoring and the user’s experience. If user experience is highly degraded because of the excessive use of bots, cheats and mods, then the developer will have no choice but to “clean” up the service or suffer substantial user loss and revenue. It’s clear that Blizzard has a strong policy of banning users that utilize bots. Blizzard urges users to work with them to eliminate cheating by not supporting websites that promote cheating and submitting a form. These efforts may subside some of the costs of finding cheating users.

    Lastly, Blizzard claimed that MDY is liable under the Digital Millennium Copyright Act under  17 USC §1201 (a)(2) which prohibits trafficking in a technology [Glider] that is primarily designed, or has limited commercially significant use other than circumventing a technological measure [Warden] that effectively controls access to the copyrighted work. Thus, MDY does violate §1201(a)(2).

    Luckily for Blizzard, MDY was selling Glider to users and touted its ability to evade Warden. However, what would happen to a mod/bot in a similar situation that is not marketed and sold to the masses or “leaked” onto the internet is unclear. The court heavily relies on the fact that MDY sold Glider, thus satisfying the trafficking element. However, the only definition of trafficking in the copyright act (which is similar to the definition in 18 U.S.C §2320) requires consideration for anything of value or private financial gain. If the release of a new bot had no specific owner and was free, would this satisfy the prong for “traffics in a technology”? I believe it wouldn’t, rendering the DMCA powerless to a developer. Thus, the developer’s only recourse is to block the accounts that utilize the unauthorized features at their own expense.

     

    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    No TweetBacks yet. (Be the first to Tweet this post)
    Tags : Blizzard, EULA, U.S. Copyright Act, World of Warcraft
    Category : Articles

    2 comments on “Glider Crashes After Running Into Blizzard”

    1. Barely Legally » Headline of the Week said: (Sunday 13 March, 2011 )

      [...] AYLABTU has the best headline: Glider Crashes After Running Into Blizzard. Go read their post, because they deserve many [...]

    2. wow bots said: (Tuesday 15 March, 2011 )

      I really like your website. I don’t have the time at the moment to fully read your entire site but I bookmarked it and will be back around in a day or two. Thanks.

    Post a comment.

    SEARCH

    facebook

    FACEBOOK FEED

    twitter

    JOIN THE CONVERSATION

    aylabtu

    • New articles up on AYLABTU related to TM in Battlefield 3 and international rulings on your MMO time. http://t.co/STSOCLLb 10:06:43 PM April 24, 2012 from web
    • 3, count em THREE, new articles on AYLABTU. GNR? Yup. Developer battle? Oh yeah! Games+School=$? Yooouuu betcha! http://t.co/hfb3A1xs 03:04:34 AM April 11, 2012 from web
    • Zynga legal dispute? No way! See blog on copying in video games industry at AYLABTU. http://t.co/ZtxDScHR 04:23:21 PM March 23, 2012 from web
    • New AYLABTU post on SK Gov. crackdown on addiction to video games. Check it out. http://t.co/epOYZACv 04:14:08 PM March 23, 2012 from web
    • "Current Trends in the Video Game Industry" Symposium being held at NY Law School 3/28 from 6-8 PM. To RSVP, email naomi.allen@law.nyls.edu 03:50:40 PM March 18, 2012 from web
    • Current Trends in the Video Game Industry talk at NYLS on 3/28 @ 6PM. RSVP to naomi.allen@nyls.edu. Tell your mom. 06:19:41 PM March 08, 2012 from web
    • 2 new blogs dealing with prelim. injunctions after eBay and international litigation surrounding Pirate Bar @ http://t.co/4Xr50GZv. 06:17:58 PM March 08, 2012 from web
    • 2 ARTICLES IN ONE DAY?!? Ubisoft DRM article by AYLABTU Editor Lauren Flynn up. Check it out! http://t.co/JNEPd3Mj 05:38:53 PM February 24, 2012 from web
    • "Analytics in Video Games: Gamer’s Best Friend or Privacy Nightmare?" by NYLS student Joseph Gregory up on AYLABTU. http://t.co/59BgGfhz 05:11:18 PM February 24, 2012 from Tweet Button
    • New blog posting, FAA gives flight to PSN's Class Action Waiver - http://t.co/jdJm7jQO 01:20:09 PM November 30, 2011 from WordTwit Plugin

    RECENT COMMENTS

    • Coskun: Phlipups / Great editorial…
    • Ayushi: yeah you were right from the b…
    • Aleck: Yes. I posted this to the othe…
    • Marie: I agree: designers and dolevep…
    • Neide: Christopher,A couple of ciarif…
    • Rommel Hueck: That's true, but if a patent t…
    • cabinet: Fantastic blog! Great!…

    RECENT ARTICLES

  • Seven Steps to Improved Security
  • EA loses domain dispute over SSX.com
  • The Bad Gets Worse for THQ
  • Dutch High Court Recognizes the Value of Your MMO Time
  • Battlefield 3 Doubles as a Trademark Litigation Simulator
  • Licensing Video Games: A Game of Pinball
  • Revisiting the (Michael) Jordan Rules
  • Beyoncé Video Game Lawsuit Moving Forward
  • Love Sitting in Front of the TV Playing GTA All Day? Then You Belong at NYU!
  • Will Guns ‘N Roses “Reunion” in Guitar Hero III Preclude Chances of Band Reconciliation at Hall of Fame Induction?
  • SUBSCRIBE

    RSS feed

    In a Reader

    Desktop Reader Bloglines Google Live Netvibes Newsgator Yahoo! What's This?

    Via E-mail:

    'Splosion Man Apple App Store Blizzard Capcom Mobile celebrity rights Content-based restriction cyberbullying DMCA DRM EA ESA Facebook Farmville First Amendment foursquare gambling gambling device gambling machine Licensing MaXplosion Medal of Honor Michael Phelps video game Microsoft NPD OnLive privacy Property Rights right of publicity social games social media Social Networks sports video games Theme music Trademark Twisted Pixel U.S. Copyright Act Video Game Bar Association Viewpoint based restriction Virtual Goods Virtual Property win or lose money Xbox 360 Zelda Zynga

    WP Cumulus Flash tag cloud by Roy Tanck requires Flash Player 9 or better.

    LINKS

  • Case Clothesed
  • Edge Magazine
  • For The Rechord
  • Gamasutra
  • Game Politics
  • Institute For Information Law And Policy
  • Kotaku
  • Legal As She Is Spoke
  • New York Law School
  • Terra Nova
  • The Escapist
  • © 1997-2010 New York Law School | 185 West Broadway, New York, NY 10013 | 212.431.2100 | Privacy | Terms | Non-Discrimination Policy | Webmasters