Riposte is out of control

sigh

reported for trolling =[

Nope. This thread is a false alarm I believe.

I think the number of extra swings I counted is a bug in GamParse v2.0.0.99C BETA.

This mob can quad attack (bite) and bash. With riposte we see an extra attack line because our "riposte! (strikethrough)" line is counted (and shouldn't be). This is the same line that is not muted a la dodge, parry, block, etc..

----

[Mon Mar 06 15:43:47 2023] A deepwater gnasher bites YOU for 4914 points of damage. (Strikethrough)
[Mon Mar 06 15:43:47 2023] A deepwater gnasher tries to bite YOU, but misses!

[Mon Mar 06 15:43:47 2023] A deepwater gnasher tries to bite YOU, but YOU riposte! (Strikethrough)
[Mon Mar 06 15:43:47 2023] A deepwater gnasher bites YOU for 4914 points of damage. (Riposte Strikethrough)

[Mon Mar 06 15:43:47 2023] A deepwater gnasher tries to bite YOU, but YOU riposte! (Strikethrough)
[Mon Mar 06 15:43:47 2023] A deepwater gnasher bites YOU for 9199 points of damage. (Riposte Strikethrough)

-----

[Mon Mar 06 15:44:21 2023] A deepwater gnasher bites YOU for 13393 points of damage. (Strikethrough)

[Mon Mar 06 15:44:21 2023] A deepwater gnasher tries to bite YOU, but YOU riposte! (Strikethrough)
[Mon Mar 06 15:44:21 2023] A deepwater gnasher bites YOU for 33623 points of damage. (Riposte Strikethrough)

[Mon Mar 06 15:44:21 2023] A deepwater gnasher bites YOU for 22198 points of damage. (Strikethrough)

[Mon Mar 06 15:44:21 2023] A deepwater gnasher tries to bite YOU, but YOU riposte! (Strikethrough)
[Mon Mar 06 15:44:21 2023] A deepwater gnasher bites YOU for 5459 points of damage. (Riposte Strikethrough)

----

[Mon Mar 06 15:45:35 2023] A deepwater gnasher bashes YOU for 3873 points of damage. (Strikethrough)

[Mon Mar 06 15:45:35 2023] A deepwater gnasher tries to bite YOU, but YOU riposte! (Strikethrough)
[Mon Mar 06 15:45:35 2023] A deepwater gnasher bites YOU for 7046 points of damage. (Riposte Strikethrough)

[Mon Mar 06 15:45:35 2023] A deepwater gnasher tries to bite YOU, but misses!

[Mon Mar 06 15:45:35 2023] A deepwater gnasher bites YOU for 21327 points of damage. (Strikethrough)

[Mon Mar 06 15:45:35 2023] A deepwater gnasher tries to bite YOU, but misses!

[Mon Mar 06 15:45:36 2023] A deepwater gnasher bites YOU for 10220 points of damage. (Strikethrough)

[Mon Mar 06 15:45:37 2023] A deepwater gnasher tries to bite YOU, but YOU riposte!
[Mon Mar 06 15:45:37 2023] You slash a deepwater gnasher for 39410 points of damage. (Riposte Critical)

[Mon Mar 06 15:45:37 2023] A deepwater gnasher bites YOU for 21327 points of damage. (Strikethrough)

[Mon Mar 06 15:45:37 2023] A deepwater gnasher tries to bite YOU, but YOU riposte! (Strikethrough)
[Mon Mar 06 15:45:37 2023] A deepwater gnasher bites YOU for 29261 points of damage. (Riposte Strikethrough)

----

Conclusions:

1. I do not believe there is a bug with riposte combat leading to extra NPC swings at this point in time. In my case, this accounting would be a GamParse bug afaic.
2. Looking at the raw logs, I see nothing weird other then combat results being split over 2 seconds.
3. I do not see NPC defensive checks. I believe that PC are overwelming NPC defenses and they are muted. I.e. I do not see any ripostes of a riposte either.
4. PC riposte swings can miss.
5. I do not see NPC "(riposte strikethough)" swings missing. This means that when an NPC strikes through an attempted PC riposte, they will always hit you. These are not extra swings, just unmuted logging. The only time it's reported as a "tries" is when the damage is absorbed by a rune. E.g.

[Mon Mar 06 12:56:16 2023] A deepwater gnasher tries to bite YOU, but YOUR magical skin absorbs the blow! (Riposte Strikethrough)

This isn't oddness at all. When they go through a Riposte (or through a Parry or through a Dodge), they've *already* passed their Hit/Miss check. We can only attempt defenses against swings that would hit. We're like spiderman, we can see if it's going to hit us before we react.

This happens regularly and is annoying to deal with.

None of the current publicly available versions of GamParse are accurate. My internal version is, but it is not in a state fit to release and development on that stopped a while ago because it just wasn't fixable and I spent way too much time on it.

I started over from scratch about a year ago, and am about half done so it also is not in a ready state yet. Notable improvements are:

• Multi-threaded
• Can parse multiple logfiles at the same time in a single instance (like gina)
• Better character/pet/npc identification and tracking.
• Tradeskill parsing
• Much faster parsing
• Uses less memory

To be fair, I should say it's not kept up with log format changes (vs an original bug). Glad to hear you're working on a new parser!

Pay attention to Denyu, his memory is far better than mine in this regard.