Activision Blizzard: Difference between revisions

Line 37:

==Incidents==

===Starcraft 2 Not including LAN Play (2009)===

In 2009, it was announced that Star Craft 2 would not include local area network multiplayer. This came as a shock since LAN play had been a staple of Blizzard's multiplayer games. Blizzard would justify the decision by stating that using their Battle.net service would be the preferred way to play. <ref>https://www.shacknews.com/article/59340/starcraft-2s-non-existent-lan</ref> <ref>https://www.tweaktown.com/news/12681/blizzard_announces_no_lan_support_for_starcraft_ii/index.html</ref>

===Diablo III Always-On DRM (2011) and Error 37 (2012)===

In August of 2011, Blizzard confirmed that Diablo III would require an internet connection to be played even if users wanted to op-out of the multiplayer components.<ref> {{Cite web |last=Lee |first=Garnet |date=1 August 2011 |title=Diablo 3 requires always-on Internet

M |url=https://www.shacknews.com/article/69522/diablo-3-requires-always-on-internet |url-status=live |access-date=1 26 2026 |website=ShackNews}}</ref>

At launch, many players were unable to play game and received Error 37 which indicated that the servers were busy.<ref>{{Cite web |last=Kain |first=Erik |date=17 May 2012 |title='Diablo III' Fans Should Stay Angry About Always-Online DRM |url=https://www.forbes.com/sites/erikkain/2012/05/17/diablo-iii-fans-should-stay-angry-about-always-online-drm/ |url-status=live |access-date=20 Apr 2025 |website=Forbes}}</ref>

'''Removing access to MWII(2022) and MWIII(2023) through the Call of Duty HQ (2025)'''

@@ Line 37: / Line 37: @@
 ==Incidents==
+===Starcraft 2 Not including LAN Play (2009)===
+In 2009, it was announced that Star Craft 2 would not include local area network multiplayer. This came as a shock since LAN play had been a staple of Blizzard's multiplayer games. Blizzard would justify the decision by stating that using their Battle.net service would be the preferred way to play. <ref>https://www.shacknews.com/article/59340/starcraft-2s-non-existent-lan</ref> <ref>https://www.tweaktown.com/news/12681/blizzard_announces_no_lan_support_for_starcraft_ii/index.html</ref>
+===Diablo III Always-On DRM (2011) and Error 37 (2012)===
+In August of 2011, Blizzard confirmed that Diablo III would require an internet connection to be played even if users wanted to op-out of the multiplayer components.<ref> {{Cite web |last=Lee |first=Garnet |date=1 August 2011 |title=Diablo 3 requires always-on Internet
+M |url=https://www.shacknews.com/article/69522/diablo-3-requires-always-on-internet |url-status=live |access-date=1 26 2026 |website=ShackNews}}</ref>
+At launch, many players were unable to play game and received Error 37 which indicated that the servers were busy.<ref>{{Cite web |last=Kain |first=Erik |date=17 May 2012 |title='Diablo III' Fans Should Stay Angry About Always-Online DRM |url=https://www.forbes.com/sites/erikkain/2012/05/17/diablo-iii-fans-should-stay-angry-about-always-online-drm/ |url-status=live |access-date=20 Apr 2025 |website=Forbes}}</ref>
 '''Removing access to MWII(2022) and MWIII(2023) through the Call of Duty HQ (2025)'''