One of the most historic studios is closing down. Unfortunately it was dead long ago. Fuck EA

Bioware is closing down
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 17 hours ago (9 children)

Are you looking at the same game? The world was vertical in the sense that you had to fly anywhere... but none of the combat or gameplay used it in any way beyond going from one place to another. That's exactly what would happen if verticality and a new map was added later in development. They just put clearings in to place the flat missions.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 1 point 16 hours ago* (8 children)

    Eh, that doesn't necessarily define where the source of pressure came from. Making unique games is an entirely different level of skill/time/commitment than what they were given.

    IMO, it's nigh equally likely that they started with the verticality design as part of it and didn't have the time to cook the idea into something neat, vs it being a later mandate after some core designs had development. The only thing that really leads me to believe that the ideas were in early is in the character designs: They were clearly meant to fly in some way, even if it might've been in a Halo jetpack sort of way early on. (which has less evidence)

    This is one of 94747252795 reasons to NEVER give these big corporations a single ounce of control over anything.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 3 points 15 hours ago (7 children)

    IMO, it’s nigh equally likely that they started with the verticality design as part of it and didn’t have the time to cook the idea into something neat, vs it being a later mandate after some core designs had development.

    Well it's a good thing that we have commentary directly related to this then, alongside basically ever major development decision... Because that's apparently what happened...

    https://kotaku.com/how-biowares-anthem-went-wrong-1833731964

    As development progressed, it became clear that some of the Anthem team’s original ideas either wouldn’t work or weren’t quite solidified enough to be implemented. Take traversal, for example. The mandate was that Anthem’s world would be massive and seamless, but how would you get around? The team played around with prototypes, exploring different ways in which your exosuit could move vertically across the world. For a long time they thought it’d be climbing up the sides of mountains and ledges, but they couldn’t get that quite right. Early iterations of flying—which, developers say, was removed from and re-added to Anthem several times—were more like gliding, and members of the Anthem team say it was tough to get the system feeling all that fun. Every time they changed the traversal, it meant changing the world design accordingly, flattening and stretching terrain to accommodate the latest movement style.

    The most common anecdote relayed to me by current and former BioWare employees was this: A group of developers are in a meeting. They’re debating some creative decision, like the mechanics of flying or the lore behind the Scar alien race. Some people disagree on the fundamentals. And then, rather than someone stepping up and making a decision about how to proceed, the meeting would end with no real verdict, leaving everything in flux. “That would just happen over and over,” said one Anthem developer. “Stuff would take a year or two to figure out because no one really wanted to make a call on it.”

    Certainly sounds like the developers had no idea how to make the game.

    One longstanding BioWare tradition is for their teams to build demos that the staff could all take home during Christmas break, and it was Anthem’s turn during Christmas of 2016. By this point, BioWare’s leadership had decided to remove flying from the game —they just couldn’t figure out how to make it feel good—so the Christmas build took place on flat terrain.

    Around the same time, Electronic Arts executive Patrick Söderlund, to whom BioWare’s leadership reported, played the Anthem Christmas demo. According to three people familiar with what happened, he told BioWare that it was unacceptable.

    Now it was time for a new build. “What began was six weeks of pretty significant crunch to do a demo specifically for Patrick Söderlund,” said one member of the team. They overhauled the art, knowing that the best way to impress Söderlund would be to make a demo that looked as pretty as possible. And, after some heated arguments, the Anthem team decided to put flying back in.

    So they removed flight entirely by Christmas of 2016, that would mean the entire map design had to lose the verticality. If you can't fly, then you have to flatten the world do accommodate for ground movement instead.

    And it was an EA executive that got them to put flying back in as a focus, flying that the team had removed entirely by that point. Even if they weren't specifically told to do so by EA. And then designed the entire game's map and movement based around that flight by the launch just over 2 years later in Feb 2019.


    They were clearly meant to fly in some way, even if it might’ve been in a Halo jetpack sort of way early on. (which has less evidence)

    I love that you try to hedge your comment and try to say that jetpack jumps and gliding are somehow even remotely in the same ballpark as flying around like Iron Man. You're honestly trying to say that Link or Aloy on a glider is similar to Anthem's flight? That's a ridiculous thing to try to compare as similar.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 1 point 15 hours ago (6 children)

    So then, that really begs the question: Why were they not allowed to take it back to the design board when the design fundamentally changed?

    Again, this is not a "developer" problem, but a fucko owner problem.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 0 points 14 hours ago* (5 children)

    Why were they not allowed to take it back to the design board when the design fundamentally changed?

    I feel like they were, effectively. There is no reason for them to not reuse assets they created from before flying was added back in after X-mas 2016, that was still 2 years before launch. 2 years is enough to develop a game, especially if the assets already exist.

    That's where the other development issues at the studio come in.

    The most common anecdote relayed to me by current and former BioWare employees was this: A group of developers are in a meeting. They’re debating some creative decision, like the mechanics of flying or the lore behind the Scar alien race. Some people disagree on the fundamentals. And then, rather than someone stepping up and making a decision about how to proceed, the meeting would end with no real verdict, leaving everything in flux. “That would just happen over and over,” said one Anthem developer. “Stuff would take a year or two to figure out because no one really wanted to make a call on it.”

    That's not a publisher/owner issue, that's a developer issue.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 14 hours ago* (4 children)

    Ohgod... that still SCREAMS interference to me... Nobody could be confident in their stance because dissent from corporate mandate meant firing, not a hearing out and debate...

    Otherwise, lead devs have many ways to force progress in a certain direction. Only fuckhead exec "direction" comes with such constant blueballing of actual progress.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 13 hours ago* (3 children)

    It's still a developer management lack of decision making. They don't get off scot free because they don't want to make a decision that EA might not like. The result of that... was a piece of shit EA didn't like. That's still on the developer.

    Unless EA is telling them to change something, decisions are still on them. Like EA saying the demo is terrible and developer management deciding to add flying back in to try and fix. That comes from an EA decision/request rather than the developer being indecisive.

    Are you trying to separate the Bioware team between developers and management, and lumping Bioware mangement into the EA side? Because that's not the discussion here. Bioware management being indecisive is still a developer issue, not an EA issue.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 13 hours ago (2 children)

    I mean... After the buyout, you BET YOUR FUCKING ASS "EA" made every dumbass inept call against them that's physically possible.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 12 hours ago (1 child)

    Bioware management doesn't get a pass for mismanagement of Anthem development just because EA is involved. EA bought Bioware in October 2007.

    In that time before Anthem they released:
    Mass Effect - 2007
    Dragon Age: Origins - 2009
    Mass Effect 2 - 2010
    Dragon Age II - 2011
    Star Wars: The Old Republic - 2011
    Mass Effect 3 - 2012
    Dragon Age: Inquisition - 2014
    Mass Effect: Andromeda - 2017

    Are you trying to claim that EA didn't interfere until we got to Anthem? Or even that it didn't interfere until the last few years before? Because that doesn't seem likely. If they were going to, they would have from the beginning.

  • source
  • parent
  • hideshow 1 child comment