Invalidate timers with random spawn if it's possible that a kill has happened and was not seen
fstenstrom opened this issue ยท 0 comments
For example:
- Player kills Rustfeather
- Player goes somewhere else (e.g. A. Harvester) for a while
- Player returns to Rustfeather on other char. Timer is now still considered valid and shows 0s->7m 00s.
If the timer shows 0s->X then that means that it's possible that an unregistered kill has happened, and it should not be allowed to share the timer.
A better option would probably be to just say "Time since last Rustfeather death: 23m 00s", and let players deduce for themselves if it's possible that a kill has been made/missed. For these kind of timers, overwriting with fresher values should be possible. See #59.