This is a lot of hot air about an non issue.
This is a lot of hot air about an non issue.
Personally I like the 'no dupes' stuff for parties. Means when a weapon drops in Byakko/other things that people can get their weapon without having to outroll someone else. I've lost things multiple times due to that.
Plus I like not having a second paladin in groups I'm in, that way buffs don't overlap, same with scholars and the like.
I, personally, am not having a problem with it, even though I main samurai. I made this thread not to complain, but to bring up discussion on what I think is a valid point that this direction is leading to greater and greater marginalization of classes.
For Byakko, the tank limit break to bypass the tiger was not intended, and yet the strategy is the de-facto way of clearing it now. It's "skip soar" all over again. In all honesty though doing it the "original" way is just a pain. I like that the players were inventive enough to try a strategy that the dev team did not anticipate
RE: the 7 tanks, 1 healer - classes should still be divided according to requirements as they are now. It's just that if two people want to play warriors or ninjas or what have you, it shouldn't make THAT much of a difference.
I get that this isn't a fighting game where smashing buttons leads to amazing results. But when you look at it, putting everything inside of such a small window of potential is just smashing buttons with a glossy coat of paint over it. Rotations and openers are all well and good, but I still think just because "other games do it too" shouldn't be a reason for FFXIV to follow suit.
I like the direction the devs took at the beginning of Stormblood to make each class unique, but some, I think are tied a bit too vigorously to those DPS windows -- I feel it's too "all or nothing" in some cases, and people concentrate more on lining everything up precisely rather than the mechanics and the "choreographed dance" of that particular fight.
Hopefully that helps clarify a bit more what my intention was with this thread.
Relax, Byakko EX is the exception, not the rule. As soon as his fight isn't relevant anymore (which won't take long in a game like this) you won't be seeing the whole "no duplicates" thing anymore until the next time they make a fight that allows a pivotal tank LB3 (or healer LB3 in the case of a fight like A4S, and it's obviously been a long time since that was a relevant fight) to allow total bypassing of a mechanic.
As for the other thing, if you don't like the super precise wtfomg dps classes, don't play them. Problem=solved. Some jobs are inherently more complex than others. This is a good thing because otherwise they would all be carbon copies of each other.
If it was unintended, they would have made the tiger do enough damage for an instant wipe (regardless of tank LB) if it was ignored. They have done this sort of "do the mechanic or die" thing in countless other fights, as well as any fight for which there is an enrage timer. It's a tactic that the devs are no strangers to. They willfully chose not to do that here. I'm pretty sure there is a reason for that.For Byakko, the tank limit break to bypass the tiger was not intended,
Last edited by Fynlar; 02-20-2018 at 02:07 AM.
No, the developers outright stated in the last Live Letter that the tank LB3 strat in Byakko Ex was not how they intended the fight to be done. They intended people to kill the second tiger just as they do the first one. The only reason I can think of that they didn’t make it an instant wipe through tank LB3 would be because people would start crying for the fight to be nerfed, and the developers in the past have shown annoyance at the constant cries for nerfs (this was said sometime around Weeping City/Final Steps of Faith).If it was unintended, they would have made the tiger do enough damage for an instant wipe (regardless of tank LB) if it was ignored. They have done this sort of "do the mechanic or die" thing in countless other fights, as well as any fight for which there is an enrage timer. It's a tactic that the devs are no strangers to. They willfully chose not to do that here. I'm pretty sure there is a reason for that.
Sage | Astrologian | Dancer
마지막 날 널 찾아가면
마지막 밤 기억하길
Hyomin Park#0055
Make your own party if you want duplicate jobs.
91 runs of byakko to get my dog - there is a significant lb3 difference with dupes and no dupes, and if you're in parties going for 5+ clears at a time, those extra minutes build up.
Is it possible to kill the 2nd tiger ye olde way? Yes, and if you are fine with no lb3, create a party that doesn't exclude dupes.
They stated in the live letter that they hadnt taken the tank lb into consideration.So it was actual an error on their side.Probably they never thought to test it and as such it wasnt programmed in to ignore tank lb.If it was unintended, they would have made the tiger do enough damage for an instant wipe (regardless of tank LB) if it was ignored. They have done this sort of "do the mechanic or die" thing in countless other fights, as well as any fight for which there is an enrage timer. It's a tactic that the devs are no strangers to. They willfully chose not to do that here. I'm pretty sure there is a reason for that.
They should have fixed it with an emergency maintenance i guess.And after it being live like that for a week they couldnt really change it in the patch as people who hadnt cleared it yet would have claimed it was unfair because of the people who already got their clear.
Most players will take the 'easiest' route and will readily skip mechanics rather than learn how to handle a fight as a whole. It happened with Zurvan (EX) and it's happening with Byakko (EX). I can't really blame players for taking that route but I do think it is a real shame and that the developers should have made adjustments to the fight once the tricks were discovered. In the case of Byakko (EX) there's a real risk of hostility if there's more than one of the same job hoping to compete for a spot.
It's also very interesting that so many of these groups cannot handle the fight as intended.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.