Drop that ban hammer Microsoft and drop it hard! That'll teach 'em, right? Well, that seems to be the method that the big software giant is employing for anyone playing the pre-release version of Halo 4's multiplayer via Xbox Live.
Multiple sites have picked up on Microsoft and 343 Industries' response to the game's leak, with Game Informer reporting that a spokesperson for Microsoft has stated that...
Well it's not just the reports that the team have been watching. Xbox Live users have come forward to post the messages they've been receiving from the Live Enforcement Team regarding permanent bans over trying to access and play Halo 4's multiplayer a month before the game's release. You can check out the letter below indicating that the noobs have been ban-hammered with a level 10 perma-ban.
Only virgins would try to play an unreleased game on Xbox Live.
Non-virgins were smart enough to keep the game cuddled up in offline mode on their consoles...playing the game, for free, after downloading it illegally.
For everyone else who either wants to pay Microsoft or are willing to honor the official release date, have only settled for doing the most honorable thing during the whole pre-release fiasco: watch the Legendary Ending a month before the game is due to release.
Now if you're a purchasing-puritan you'll probably want to steer clear of all this leaked, spoiler nonsense. Just take your chaste Xbox 360 far away from the mod scene as you wait out the November 6th launch of Halo 4, like a Wall-Street trader waiting for the red flags to cease before going gung-ho with the inside trading.
Oh yeah, and if you decided to dip into the devil's digital domain and grab a leaked copy of Halo 4 for your cherry-broken Xbox 360, be sure not to play the game on Xbox Live or you'll be receiving a not-so-friendly message from the Xbox Live Enforcement Team.
Staff Writer at CinemaBlend.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.