aboutsummaryrefslogtreecommitdiff
path: root/evtclib
diff options
context:
space:
mode:
authorDaniel <kingdread@gmx.de>2020-06-12 12:31:48 +0200
committerDaniel <kingdread@gmx.de>2020-06-12 12:31:48 +0200
commitdda777e70121324c4855b94ee2b985f9eda7a251 (patch)
tree46ea22055aff5cf9df59ce28ab4d96056f2ab3cb /evtclib
parent9c7df815d2b19929fe5ca5295c8a5526bcfcee73 (diff)
downloadraidgrep-dda777e70121324c4855b94ee2b985f9eda7a251.tar.gz
raidgrep-dda777e70121324c4855b94ee2b985f9eda7a251.tar.bz2
raidgrep-dda777e70121324c4855b94ee2b985f9eda7a251.zip
compute fight duration from event times
It seems a bit iffy to use the local timestamp to compute the fight duration: First of all, the event timestamps have higher precision, being counted in milliseconds rather than seconds. Second, it is more reliable, as we always have a first and a last event, whereas the LogStart and LogEnd may not exist. Third, we may want to change how this value is calculated in the future anyway, as some bosses have a bit of a pre-log before the fight actually starts (arcdps starts the log when you get into combat, which might be before the boss actually spawns, like on Ensolyss). In either case, this function is probably a strong contender for being implemented properly in evtclib.
Diffstat (limited to 'evtclib')
0 files changed, 0 insertions, 0 deletions