Slashdot Mirror

← Back to Stories (view on slashdot.org)

"Badass" Bug Infects and Kills Borderlands 2 Characters

Posted by Unknown on from the it's-a-feature dept.

An anonymous reader writes "BBC News claims that a feature in Borderlands 2 that can only be activated in modded XBox 360s has a bug that can cause characters to be permanently deleted when they die- even if they weren't the ones who activated the feature. 'The hidden option within the game, known as "badass" or "hardcore", is turned off by default but can be enabled by those that have modified or hacked their console. [..] When a player with an unmodded console joins a Borderlands 2 multiplayer game in which there is a character running in badass mode it too gets kicked into that mode. [..] Gamers who play alongside people who have modded their console "contract" the bug which deletes their character if they die during play.'"

9 of 189 comments (clear)

  1. It's worse than that by Anonymous Coward · · Score: 5, Insightful

    It hits anyone who is in a game with anyone who has ever been exposed to it. So if player A enables it, plays with player B, and player B plays with player C, and I play with player C, I'm infected, and anyone that plays with me is also infected and a carrier.

    1. Re:It's worse than that by arth1 · · Score: 4, Insightful

      What's remarkable is that after having similar problem with "contagious" bugs in the first Borderlands, they did not safeguard against the possibility in BL2.

      In the original, two missions could be left in an unfinishable state, and everyone who played with someone with this condition would catch it too. Luckily, one of the two was a beginner's mission, and most people would already have moved the storyline past that point, and the rest get around it by recreating the character. The other one, though, was nasty.

    2. Re:It's worse than that by drinkypoo · · Score: 4, Insightful

      What's most remarkable is that a bug like this is possible at all. It reveals that the game developers did some seriously stupid shit. Nothing that another player has done to their profile should affect what happens to my profile.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:It's worse than that by mekkab · · Score: 4, Insightful

      p>Im no programmer-- but this isnt difficult. .

      You sound exactly like the manager who told the coder "just get rid of the setting but don't rip out all the other code behind it. We'll have to retest everything and we don't have budget or schedule for that. This isn't difficult. "

      --
      In the future, I would want to not be isolated from my friends in the Space Station.
  2. Re:Ah yes... Non-featured features... by Selfbain · · Score: 5, Insightful

    I'd say the ability to permanently kill an opponent in multiplayer is more than a simple bug.

    --
    Well, it has never been successfully tested.
  3. Wait... by Velorium · · Score: 4, Insightful

    Wasn't South Park's WoW episode like this?

    1. Re:Wait... by tisepti · · Score: 4, Insightful

      No. Though wow did have another similar bug.

      http://en.wikipedia.org/wiki/Corrupted_Blood_incident

    2. Re:Wait... by Geirzinho · · Score: 4, Insightful

      The corrupted blood incident is actually better described as emergent behavior in a complex system.

      The Blizzard developers didn't make a mistake, they just didn't think about all the consequences that debuff would cause in a world-like environment. And researchers had a field day studying the CB spread of the epidemic:)

  4. Why does this happen? by goombah99 · · Score: 4, Insightful

    I'm assuming that this happens because the server is trusting client stored data. That's approximately the same as not validating ones inputs in a fill-out-form. Why in this millennium would anyone ever trust data stored on a client without validating it first? Isn't this 2012? Or is there some other way this could happen?

    --
    Some drink at the fountain of knowledge. Others just gargle.