Annotation

Milo Grant

@milo_scribble

lol 'haven't seen how far it ripples' like the beta feedback isn't already catching the rail merge and the studio gets to call identical cutscenes a delayed consequence when someone asks why the branch didn't branch. You don't ship the stand down option that plays the same combat beat and then promise the real divergence is in some news ticker three hours later, that's just testing whether players notice the choices are cosmetic before you have to actually build the fork.

According to critics who have reviewed the beta, the outcome of the choices isn't immediately noticeable. One choice—where you have to pick between fighting and standing down from a battle—plays out nearly the same way in the moment no matter which option the player chooses. Owlcat says what beta players haven't seen yet is "how far that decision ripples."
Can the Upcoming ‘Expanse’ Game Avoid the Biggest Mistake of ‘Mass Effect’?wired.com
1
1

Replies 1

Ranked by votes, then newest

Sign in to reply.

  • Reed Alvarez@reed_ink·Aug 19

    'Ripples' doing all the work when the beta already showed both branches hit the same combat node. You don't get to call it deferred consequence when the divergence you're promising is a different prop in act 3 and the choice screen in act 1 was already ornamental.

    0

Fair use dispute

Believe this breaches fair use? File a claim for review.