limit break 2.1 penaltyFollow

This is one of the dumbest things yet for DF, I see the reason for pug parties... I went to do ifrit HM through DF and the party dropped 3 times before starting.. First time we had no blm so they dropped because of nails. Second time we had 3 BLM so there was going to a penalty of how fast the limit break would build so everyone dropped again..

With DF You have no choice who you get thrown in with so they should remove the penalty to limit break with multiple of the same job.

Edited, Dec 30th 2013 12:22pm by Nashred

That requires people to discuss strategy and more importantly listen to/follow it... Words are too much work for some folks.

I dont think some of you get the point... I just used ifrit as a example because that is a major case where you sit for 15 min waiting for a party longer for some jobs only to have people back out. Then do the same all over again till there is a perfect party... My point was not if it could be done without the perfect party.

My real point is: Why should a party be penalized on limit break because you end up with two blm or two BRD on DF.. The problem is DF throws who ever in your party.. You dont get too choose.






Edited, Dec 30th 2013 2:10pm by Nashred

I did a party finder for chimera for someone in the FC the other day. There were 4 pairs. LB never got past about 1.25.

I got a DF with 3 pairs and both tank jobs too. It made Ifrit take FOREVER because we had to auto-attack to build the LB. Stunning isn't the guaranteed builder it used to be either. Ifrit now resists stuns.... a lot.

It's an assinine restriction and should be done away with.

I just mentioned it... We did the Chimera fight with 4 pairs and couldn't get the LB over 1.25 - 1.5 or so.

Same with Ifrit. During a fight with 3 pairs and both tanks, the LB bar was at about 1.75 when the nails popped. We had to auto-attack him until the bars were full after the ineveitable wipe. It's a combination of stun resistance and the nerf for him.

Edited, Dec 30th 2013 10:59am by LebargeX

You are right it is the problem with people backing out. They are not dropping out because of what you say though. They are doing it because they dont want to waist time..
I think most people already know you can beat it with out a optimum party .. They are in a rush at this point and dont want to waist any time and the first too drop is almost always the tank because they can get in a another party instantly.. They wont sit for 30 minutes or longer to try and maybe beat it. I have seen them drop WP not having a perfect party. Just like with all these dungeons most will only run the the one that is the quickest like wp if they still need tomes but with primals the lb is far more important.. . Its life and you aint going to change that unless there is a penalty for dropping..







Edited, Dec 30th 2013 2:26pm by Nashred

You know what I mean...

I did Titan HM with 3 pairs last night and the LB only hit 1.75 by the heart phase and that was with the dps taking it easy in an attempt to build the LB. Luckily, we had enough dps to down the heart using only 1 bar because we couldn't the second bar full in time to use it on the heart. The new restrictions on LB are just stupid IMO.

Edited, Dec 30th 2013 4:10pm by princessary

The idea isn't dumb, their approach is. It's completely reasonable that they'd want people to avoid stacking the same jobs if they're trying to shed the 'cookie cutter' mentality. They need to adjust their mentality though.

Instead of nerfing groups with multiples of the same class, they should buff groups that are more diverse. I don't think this is something that should carry over to DF at all though. Just my two pennies.

By putting this system in place though, they are regulating which "cookie cutter" you are even able to use. It's not very effective for them to remove one cutter, to only replace it with another. The only choice you have now if you're looking to build the LB effectively is which four of the five dd's do you take into an instance if you run with both tanks and both healers. That's five cutters you have to choose from now, where before there were many more.

The changes made to classes should have been enough to get away from stacking bards and paladins in some of the end game raids, which I think is what they were aiming for, IDK.

I full heartedly agree with not having it be a part of the DF though. That makes about the most sense if they really want to not penalize someone for using the DF, which is, IMO, the only thing that is being really being negatively effected by this change.

IDK man, most of the people running HM Ifrit are undergeared at the point that you can 1st attempt it. I have watched undergeared parties with no aoe LB, armed with a good strategy and good execution still fall short on nails. It's not the people that are fully geared with +1's and max stats that really need the LB, it's players that are fresh to lvl 50 that could really use it to conquer things like Ifrit.

It's a double-edged sword.

People were so reliant on LB3 from SMN and BLM on Ifrit prior to the patch that other classes and other compositions were just shunned all together. Didn't see a BLM or SMN in your party? Might as well drop group.

Now at least people understand that it isn't impossible to do without LB3. You have the BLM/SMN use LB2 (or even LB1) on a couple of the nails. You finish off those nails and gain LB back. You now use the melee LB to finish off the rest. Don't think you're going to make it and have one nail left? Tank LB2 can sometimes save you.

One thing I will say is that it was poorly implemented. We understand the purpose but, at the same time, you screwed a bunch of people over that already had a static group of players with set jobs for 3 months now. Since you neglected WAR for so long and implemented it poorly, most groups were double PLD which automatically cuts the LB generation down substantially. Groups with two of the same class are now cut even further.

I'll give you an example. Tonight, we did Twin again but this time everyone was on a different job. We actually had LB3 by the time the 4 snakes were all up. As I cited above, with two repeated classes we may have gotten to 2 and 4/10ths of the bar. With four repeated classes, it is just bothersome.

LB is a really neat mechanic and it feels like they are taking some of the spotlight away from it. They had the opportunity to make adjustments to certain LBs this patch but chose not to do so. Perhaps if each job had its own LB that served a purpose for a specific fight, people would be more inclined to take different classes instead of stacking them. I have a feeling this is why BRD was stuck with the healer LB instead of a DPS one (and the fact that they're too lazy to implement a ranged physical LB).

They could have modified tank LB so that it actually was worthwhile to use it outside of very specific fights like Ultima or emergency mode in Garuda Ex and Titan HM/Ex. They could have adjusted healer LB so that it wasn't a joke outside of LB3. They could have added a ranged LB for BRD, a SMN-specific LB for each of their summons, etc. It just feels like it was a bandaid fix to a problem that has been going on since the game was released.

Edited, Dec 31st 2013 6:30am by HitomeOfBismarck