Dev Request: Ability to see Wyrm Wave's recast timer

[Nemekh]

I just use the GCD timer. With my latency in mind, I pull my oGCDs around the half of the GCD and get very stable 13 WWs in every Bahamut.

You're not doing 13 ww with 2 am. Even at best case where Bahamut phases are recorded with 12ww 2 am one action is almost always a ghosted action.

The current state is just encouraging people to perform suboptimal Bahamut rotations just because it looked like all actions were valid.

[KarstenS]

You're not doing 13 ww with 2 am. Even at best case where Bahamut phases are recorded with 12ww 2 am one action is almost always a ghosted action.

You're right. Its 12, not 13. 7 GCD and 5 oGCD. But look here. Its doable to bring them out constantly. 36 WW = 3 Bahamuts x 12 WWs.

[zuzu-bq]

Sometimes it gosts and FFLOGs counts as it didn't. But you can constantly make it show as 12 in there.

[KarstenS]

Sometimes it gosts and FFLOGs counts as it didn't. But you can constantly make it show as 12 in there.

With the exception of DoT and HoT ticks it uses the data of the battle log. So its the game itself that says yes or no.

In another kill I have 35 WWs and the reason was I sucked up my rotation to a point I got trisaster not ready during Bahamut. Clearly a mistake on my side.

[Nemekh]

With the exception of DoT and HoT ticks it uses the data of the battle log. So its the game itself that says yes or no.

In another kill I have 35 WWs and the reason was I sucked up my rotation to a point I got trisaster not ready during Bahamut. Clearly a mistake on my side.

It actually does not use the contents of the battle log and it's because of this lack of checking against it that ghosted actions slip through and count towards the damage total in a given report when they should not. What it uses is a particular message sent which is the basis behind how all the net logs are generated. This message is technically saying "this is what will happen", not "this is what has happened". In other words there is a time difference in when that data is received vs when the damage is confirmed in game. If Bahamut despawns before this confirmation happens, while the damage data is recorded the damage never happens in game.

Even in cases of a "recorded 12 ww" in almost every case one action has to give way. Whether that's a wyrmwave or an akh morn. Now if you are interested in how you can check in game to see if an action was ghosted or not against a log, count the damage entries and/or count how many "Demi-Bahamut casts" messages. If you're in The Balance discord I have the checks pinned in smn_questions.

Addendum: Comparing Summon time with final Bahamut action time from what you linked from your report.

00:01:37.043 for Summon Bahamut
00:01:57.094 for his final Wyrmwave. That WW was certainly a ghost. The time is too close to when the despawn happens, in recorded ms it's actually after 20000ms has passed.

00:03:28.808 for Summon Bahamut
00:03:48.439 for Akh Morn. You ghosted Akh Morn in order to get that 12th ww!!

00:05:25.913 for Summon Bahamut
00:05:45.699 for his final Wyrmwave. Again, like the first summon case due to the timing.

This is a field that has been researched extensively. So please, when we say avoid the 12 ww meme so that you can achieve consistent real damage, take that advice to heart. You're not playing optimally this way. There's a good reason the recommended count is always 11 real ww + 2 real akh morns.