How about a command for only the killmessages. I never turn the actual chattime on since the clutter bothers me and it also doesn't timestamp kills.
/set killtime system
/set killtime all
/set killtime off
so it would give you an instant timestamp for everyone one who dies either in your system or anywhere red messages.
This would help bounty claiming immensely. No more accidentally missed timestamp so you cannot claim properly... which you have to as the rules demand it.
If I am understanding this correctly, you're looking to have just the kill message timestamped?
Wouldn't it make more sense to use enable timestamps for everything and just use the tool created by Protege for filtering through logs? Then the bounty logs are saved and you can easily remove any annoying timestamps.
Also I know this is a old thread, but a late answer is better than no answer.
(11-28-2017, 01:52 PM)Laz Wrote: If I am understanding this correctly, you're looking to have just the kill message timestamped?
Wouldn't it make more sense to use enable timestamps for everything and just use the tool created by Protege for filtering through logs? Then the bounty logs are saved and you can easily remove any annoying timestamps.
Also I know this is a old thread, but a late answer is better than no answer.
it's much easier to just use ctrl+print scr with sharex, so I can see the use for this
Done. A pull request will be created later today, after some minor code formatting cleanups.
First death, no timestamp
Second death after enabling them, timestamp
Third death, global death messages were turned off. Diemessage is still turned on, but no timestamp because you can't see the death.
If chattimes are enabled, you shouldn't get duplicate timestamps. Haven't tested that, but theoretically in the code it shouldn't. - This change was given to someone running a private server. If they tell me I screwed up, I'll make a quickfix before the pull request.
(03-24-2018, 11:11 PM)Remnant Wrote: Done. A pull request will be created later today, after some minor code formatting cleanups.
First death, no timestamp
Second death after enabling them, timestamp
Third death, global death messages were turned off. Diemessage is still turned on, but no timestamp because you can't see the death.
If chattimes are enabled, you shouldn't get duplicate timestamps. Haven't tested that, but theoretically in the code it shouldn't. - This change was given to someone running a private server. If they tell me I screwed up, I'll make a quickfix before the pull request.
Happy stamping
Bumping this because it went unnoticed and undocumented.