Titan HM needs to be Fu*king nerfed ASAP

[Hayward]

One thing S-E can do is not allow multiple stacked plumes to count separately. Another is to extend Weight of the Land's cast time by 1 second to make up for the latency issue. Giving people time and a chance to dodge is not "dumbing down" the fight by any stretch. A real "nerf" would be to cut Titan's Heart's HP by 25%, which no one has even suggested.

[sheepysheepy]

One thing S-E can do is not allow multiple stacked plumes to count separately

surely even with lag no one should be eating 2? that just means people are sitting on top of each other when they shouldnt, so getting rid of that really does promote bad play

[Palltard]

One thing S-E can do is not allow multiple stacked plumes to count separately. Another is to extend Weight of the Land's cast time by 1 second to make up for the latency issue. Giving people time and a chance to dodge is not "dumbing down" the fight by any stretch. A real "nerf" would be to cut Titan's Heart's HP by 25%, which no one has even suggested.

I havn't seen Coils yet, but I could only assume in a end game content (coils) I would assume you are practicing to dodge any type of damage that is avoidable before entering the most recent content. Weight of the Land's cast time seems find on a normal day, A.K.A no latency or lag at all. Dont hesitate to dodge stuff, thinking about what to do is worse than just moving out of the way.

[Cryvil]

A real "nerf" would be to cut Titan's Heart's HP by 25%, which no one has even suggested.

This, so much...is there another fight in the game where the encounter is designed to force the party to use the limit break? Against Caduceus, ADS, Garuda's clones, Turn 4, even Asclepius and his babies, limit breaks make the encounter slightly easier, but are -not- mandatory. Titan's heart is the complete opposite. Unless you're overgeared, and sometimes even then, the limit break -is- mandatory.

...no choice, no strategy, no damage meter(I refuse to use third party programs), no room for error. When you fail, you have no idea why you failed...who came up short on the damage. A very dull DPS check...the worst part of my favorite fight.

So yeah. Either add a damage meter to the game or cut titan's heart by 25%.

[TirionCrey]

So yeah. Either add a damage meter to the game or cut titan's heart by 25%.

Holy F...
If the group can't meet the DPS requirement for the heart, you can assume that either one, or several DPS don't do their Job. A group of DPS in AK gear and WP weapons can meet that DPS requirement EASILY if they know how to play their class.

[Cryvil]

Holy F...
If the group can't meet the DPS requirement for the heart, you can assume that either one, or several DPS don't do their Job. A group of DPS in AK gear and WP weapons can meet that DPS requirement EASILY if they know how to play their class.

I've gone on groups with just me, a tank, and 6 relic-holding dps, and watched them fail to kill heart. There's something really screwy about that part of the fight.

+:I'm tired of hearing people say "they're just bad." Losing to landslide...especially a laggy landslide...is fun as hell and never stops being hilarious. Losing to the heart phase is miserable. How about we stop saying everyone struggling with Titan is bad and accept that there's some weird over-the-top difficulty curve in it. I suspect that the fight is one of those trials that's supposed to force the players to learn how to play their classes better. But because there's no damage meter, no indication of how much a DPS should be contributing and how close or far they are to it, the DPS players don't get a chance to learn from their mistakes. If Square refuses to implement such a feature, then they should accordingly reduce the health of the heart.

[Brises]

How about we stop saying everyone struggling with Titan is bad

Because, whenever people say something is too hard, others love to jump in and say how easy it is for them. It's an ego thing.

[Rhained]

I've gone on groups with just me, a tank, and 6 relic-holding dps, and watched them fail to kill heart. There's something really screwy about that part of the fight.

+:I'm tired of hearing people say "they're just bad."

How else do you explain 6 relic holding dps failing heart other than "they're just bad".

[Exstal]

How else do you explain 6 relic holding dps failing heart other than "they're just bad".

This exactly. When 3 relic +1 can do a better job than 6 normal relic, something is wrong.

[Kashaar]

Honestly, the fight is perfectly doable because of the scripted (i.e. always the same rotation) abilities per phase. That's the key - knowing the rotation, or running it with someone who does and can remind you. Scripted encounters are a huge advantage to you as the player - don't overlook that.

First time I did the fight, I had seen the vids, I had the ability cheatsheet next to me and had a familiarity with the ability rotation and what I should do for each one, and I had full DL gear + Garuda weapon. I was as ready as I thought I could be, but honestly, none of that helped quite as much as a couple very experienced people in the run who did two amazing things:

1) Pinged chat before each plume to give an audible reminder that you should pre-move, in case you were tunnel visioning.

2) Put a marker on one player for bomb phase and said "If you don't know where to go, just stack on this person and follow them."

With those two extra elements, it was smooth sailing for everyone, and the fight was a one-shot. I would suggest that rather than asking for the fight to be nerfed or paying for a carry, you look for one or two people who have done the fight successfully to help show your group the ropes. Most servers, I think you'll find someone willing to give you a hand if you ask, particularly if you show you've done your homework and just need a little extra help. YMMV.

Regarding the fight itself, I do agree that you shouldn't /have/ to pre-move in order to work around latency -- that's silly -- and S/E should take latency and their poor position algorithms into account when designing these fights. An extra 0.1 - 0.3s to the abilities might be enough to resolve this until they can fix their position detection code, and allow more people to progress through this without the maddening feeling of being outside the red lines yet still getting hit. Until / unless that happens, though, the suggestions already given (pre-move for plumes, use an ability as soon as you're outside a circle to force position updates, etc) are probably the best you can do.