"Dhuriya24;c-1817156" wrote:
You're delusional if your really going to try and blame me/the playerbase for Finn getting nerfed. Unless you started playing this game 4 months ago, you should have basic knowledge of how this team works and has worked in the past. This team has always worked by generating a TM train that prevents opponents from attacking and the developers never saw a problem with Finn's leadership until people started using Han to outspeed Revan with c3po.
zFinn's interaction with c3po in the raid and PVP is not an exploit, its a mechanic that the developers dont enjoy existing in the game because of an actually badly designed raid and zFinn's ability to compete with high tier teams.
If you really read my post, you would see that I was asking for a non-Revan team that can reliably compete in the meta, but one cant be listed because it doesnt exist.
If zFinn got ousted out of the meta due to teams that just happen to counter him, whatever thats normal. CG coming out of the woodwork to nerf an old leadership just because they dont think it's fair to people who own Revan is once again, just as petty as you stalking me for weeks.
1) I ain't stalking you. I'll take your word for it that I replied to a few of your posts on a public forum in a couple of the larger threads of the moment. You have a generic internet number name and no real avatar; I do not remember who the heck you are.
2) I never blamed the playerbase for zFinn getting reworked. The interaction itself is a problem. It had to be changed for the health of the game. But you should not be upset that the game is being fixed.
3) Exploit loops are still mechanics. That does not make them stop being exploit loops. They're unhealthy for the game, and need to be fixed. Up to 175% TM gain for popping a bubble is an inherently broken mechanic in an ATB system that just begs to become a loop. The 3PO/Han/Chewie lineup takes it to extremes, with the potential to dovetail you into an infinite turn meter loop at tick zero of combat unless they have a specific ability to prevent it without action (and sometimes even if they do) is not healthy for the game, needs to be fixed, and you are not entitled to additional compensation because the exploit loop you were profiting from gets fixed.
4) zFinn did not suddenly become a problem because of P3 Sith or 3PO or interactions with Revan. P3 Sith was the specific inciting incident, but it's been an issue for a lot longer. Most problems in a game exist for some period of time, then there is a specific event where it goes too far, and then it is fixed. But that doesn't make the prior problematic elements cease to exist.
Finn is a massive design space problem. When Finn got his zeta, it firmly proclaimed Resistance to be an Expose faction. His expose sources in-faction at the time were himself, Poe, Trooper, and Pilot. Five new Resistance units and over a year later, his in-faction expose sources were... himself, Poe, Trooper, and Pilot. (BB-8 doesn't count because 70 turn cooldown.) Because Finn's lead must not be fed. Because it's a broken mechanic. They even found a clever workaround in JTR's lead to keep saying Resistance is the expose faction, but nest it under her lead so that it won't feed Finn. Then, they fed Finn a good expose source and it broke.
hSith was just the impetus to finally fix a standing problem. Because no matter how hard you deny it, going right into an infinite TM loop at tick zero unless your opponent has some sort of out-of-turn counter is a profoundly broken mechanic that creates serious design problems.
5) Changing mechanics the developers don't enjoy is literally part of their job. Where mechanics the developers don't enjoy are defined as mechanics that they deem must change for the long term health of the game. This is not a Galaxy of Heroes thing. This is a thing in most continuously supported games. Sometimes long-established mechanics have to change. Extreme TM leads like Finn and HK-47 are some of those mechanics that have to change.
6) Bringing up Revan is pure whataboutism. And phrasing it as "Revan" is disingenuous since there are two completely different Revans right now.
Jedi Knight Revan is a meta. We've had a lot of metas in the past. People have complained about every single one of them. Yes, Jedi Knight Revan has been an extreme meta. Now, Darth Revan is carving out a spot in the meta, and will continue to do so, whether it's practical or not. There are currently multiple viable meta teams. That you dislike their leads having similar fashion sense does not invalidate that fact.
But regardless, Revan is a meta. Metas come and go. Upcoming releases will shake Revan's hold. It's a temporary problem. Finn is a persistent problem that's been impacting the game and its development for years. Ousting a Revan meta with the Jar Jar meta will not fix the Finn problem. Only fixing the Finn problem will fix the Finn problem, and it's been let set for long enough.
"SmurfLAX28;c-1817177" wrote:
C'mon man, you know anything not named Revan in this game is an overpromise and a massive disappointment.... How many times have people been disappointed by CG trolling us by underdelivering
How many times has the playerbase drummed up unreasonably extreme hype and been disappointed based on things that were never promised?
How many times has Revan
been the disappointment when pretty much everything since the release of Nihilus was, "Darth Revan confirmed?"
