Post by PapaCharlie9 on Jul 12, 2018 15:53:30 GMT
More about how Anthem doesn't pigeonhole Javelin's to holy trinity roles, from a similar thread in Reddit's /r/anthemthegame:
old.reddit.com/r/AnthemTheGame/comments/8y2c5y/anthem_is_a_classbased_shooter_and_you_should/
OP summary: Anthem should be a holy trinity because of WoW and because Destiny was a holy trinity and because any other concept is nonsense. Literal excerpt:
"No, my point is still his (Bioware Chris Schmidt's) response, "We do not 'hard enforce' roles akin to a traditional trinity model (heal/dps/tank)," and, Chris, this is nonsense. All of us who played Destiny know that Titans were the tank class, Hunters were the hybrid DPS and Warlocks were the secondary DPS or support. Sure, all of them functioned similarly on a structural level, but they each had unique things to bring to the game that often warranted having certain classes for instances and raids. Because of this, and after seeing a gigantic, pulsating bug monster complete with egg sacks as the boss, I refuse to believe that Colossus and Rangers will bring similar results to the table."
Bioware Chris Schmidt's response. First he quoted another redditor's attempt at clarification about what 'do not hard enforce' means:
"Hey there! This is exactly what I was getting at. That the design of the game is not artificially pigeonholing you ("hard enforcing") into a particular role. Certainly players and classes will gravitate towards certain roles, and even the most effective way to conquer certain content may end up being in those roles, but philosophically we want to allow experimentation and viability in a variety of roles within the same javelin. And this in turn informs how you approach end game content design. In a hard enforced trinity design, I can always assume I have one healer, one tank, and two dps in a 4-man group. And since you design around that assumption, you reinforce that in various ways (like in matchmaking wait for one tank, one healer, and two dps to fill roles).
Using the 'trinity' example - for many years I played as a Protection Warrior in World of Warcraft. The design of the warrior class hard enforced that my role could never be as a healer, due to the design of the game. I'm not making a judgement call on whether one way is better than the other - just that our design takes an alternate approach.
Does that make sense? Let me know your thoughts!"
old.reddit.com/r/AnthemTheGame/comments/8y2c5y/anthem_is_a_classbased_shooter_and_you_should/
OP summary: Anthem should be a holy trinity because of WoW and because Destiny was a holy trinity and because any other concept is nonsense. Literal excerpt:
"No, my point is still his (Bioware Chris Schmidt's) response, "We do not 'hard enforce' roles akin to a traditional trinity model (heal/dps/tank)," and, Chris, this is nonsense. All of us who played Destiny know that Titans were the tank class, Hunters were the hybrid DPS and Warlocks were the secondary DPS or support. Sure, all of them functioned similarly on a structural level, but they each had unique things to bring to the game that often warranted having certain classes for instances and raids. Because of this, and after seeing a gigantic, pulsating bug monster complete with egg sacks as the boss, I refuse to believe that Colossus and Rangers will bring similar results to the table."
Bioware Chris Schmidt's response. First he quoted another redditor's attempt at clarification about what 'do not hard enforce' means:
I think what Chris may be trying to say here is that as a Colossus, you could build yourself to be an effective DPS without needing to be pigeonholed into a tanking role every time that you play.
"Hey there! This is exactly what I was getting at. That the design of the game is not artificially pigeonholing you ("hard enforcing") into a particular role. Certainly players and classes will gravitate towards certain roles, and even the most effective way to conquer certain content may end up being in those roles, but philosophically we want to allow experimentation and viability in a variety of roles within the same javelin. And this in turn informs how you approach end game content design. In a hard enforced trinity design, I can always assume I have one healer, one tank, and two dps in a 4-man group. And since you design around that assumption, you reinforce that in various ways (like in matchmaking wait for one tank, one healer, and two dps to fill roles).
Using the 'trinity' example - for many years I played as a Protection Warrior in World of Warcraft. The design of the warrior class hard enforced that my role could never be as a healer, due to the design of the game. I'm not making a judgement call on whether one way is better than the other - just that our design takes an alternate approach.
Does that make sense? Let me know your thoughts!"
). High risk, high reward. The storm looks fantastic for that, so I will be playing as it. But no doubt can you do something similar as ranger, if you choose to build it as such.
