This suggestion is basically a command which tells both date and time on the server's side, short command is recommended for quick screenshotting. This can reduce the hassle of searching screenshots since you have double screenshots for most evidences occured in the server, usually when you received/sent a payment, you can just type a command which gives the timestamp and then screenshot just once, rather than twice for the screenshot timestamps which takes space in the screenshot folder. There may be time where you need to rapidly react and screenshot like in the case of attempt killing from other players, this won't be issue IF both timestamps from this command which tells date and time from server's side and screenshot timestamps are both accepted. Spoiler: Note Though if screenshot when lagging, double screenshotting timestamp is required before being disconnected since this command will not work. tl;dr: Make a command that tells the server's side date and time, probably timezones (UTC) as timestamp addition, as well as making it as a alternative form of accepted timestamp in screenshots.
You can see the server time using tab, however it's not too comfortable to tap F2 while holding tab, and if you're holding tab you're doing that outside of the chat interface, therefore only a couple messages are shown (and only if they were received a very few seconds earlier). So it's a terrible tool if you want to collect evidence. I think this command should be top priority, for a simple reason: double-F2 shows your local time, and it's not obvious what's the time zone of the screenshot and usually people just don't care because they completely neglect this issue; you have to manually convert the time (IF you realize the timezone is different and only if you are meticulous enough); it's ridiculously easy to tamper with: you just change your local time (hell, you could even change day, month and year), take the screenshot, then set it back correctly. Let me state the obvious: point 3 is the critical one and, in my opinion, after a brief amount of time to let users get used to this new tool, double-F2 should not be accepted anymore. I think it's a very bad idea to rely on something so easy to tamper with, when it's evidence we're talking about! ps: speaking of which, as it's something very easy to implement, it could be a good idea if this command showed both server time and UTC.
Not to mention it doesn't show the date from server side as well. Sounds good to include UTC too, adding that to the main post. Spoiler Come and think of it, what if there is a scoreboard which tells the server time and date (as well as UTC), taking the same location where McMmo scoreboard would stay? Will that do better? Since it make screenshotting with evidence even easier as if the server time (and date) would always be there. Or maybe make both scoreboard and chat message which both tells time for convenience?
Probably both might be better, as someone might not like the persistent scoreboard and disable it: should they need to make a screenshot, they would have to enable it and then disable back with two commands, while with a single command then can get a mere chat output. But I think discussing on these details might be premature, let's see what they say on the general idea first
Your first two points are really only relevant in cases where agreements in cases where specific times are mentioned (eg "You owe me 1k at 3pm today), having two different time zones on an official server time listing would cause exactly the same issues. Sure, you can say that players ought to mention a time zone, but if they were doing that from the get-go your first two points are irrelevant anyway because specifying a time zone changes a relative time to a definite time. Although I don't think that the issue being presented here is very much an issue, this seems a simple enough thing that I have no issues with it, provided that it exclusively provides the time according to US Eastern Time Zone (ie official server time), as that's the time that is used for nearly all official server events, expirations, time listings, etc. Adding UTC sounds good on paper but in practice I don't see it being practical or relevant.
