Allow users to set equivalent of ACT's "Number of seconds to wait after the last combat action to begin a new encounter"

[loldcv]

Hello

I am missing a feature from the regular ACT named "Number of seconds to wait after the last combat action to begin a new encounter".

Would it be possible to make this value configurable? To me it looks like its just this:

private const int endEncounterOutOfCombatDelayMs = 5000;

in EnmityEventSource.cs would have to be made configurable.

Best regards

[SayuShira]

Yes, please 🙏 Or up it to like 10 seconds-ish, which would relieve my issue/use case:

Been wondering and started looking why my Striking Dummy fights split into two to three logs. Seeing this issue I tested it.
Turns out, it's because I often happen to recast two Motifs back to back. Three second cast, times two, with no outgoing damage aaand I'm in a new log >.<

Knowing that now, I can of course work around that to get accurate numbers. So thanks for this issue already, loldcv!
But ideally, the fight would not be split when I am still casting things. With Picto having up to nine seconds of no-damage casts, a higher default would prevent this from happening to others.

[DJFarr]

Bumping this, as I prefer to have my DPS meter track entire dungeons as one encounter.

[marzent]

I think this feature would be best implemented first in upstream OverlayPlugin, and then we can pull in that change...

Lately I am trying not to diverge too much again from them, so maybe one day the projects can be somewhat shared.

[marzent]

In the meantime, maybe the added option from #133 also somewhat helps with the issue, if you want to manually manage encounter ending via /endenc.