So I was recently told that after mapchanges, damage logs are retrievable for past rounds, but not shot logs or chat logs. I think it would serve to everybody's benefit if chat and shot logs were saved for a period of time (few days maybe?). A recent report I made was basically bust because of the fact that we can't retrieve shot logs or chat logs. I mean if you think about it, all someone has to do is say "I saw you shooting" on an RDM report and unless a demo can prove otherwise, they're S.O.L. , Al
Chat logs are in the console and go back to a certain point. Shot logs aren't that useful for the most part anyways, but are sort of embedded in the damage logs. EDIT: by a certain point, I mean a few maps worth of chat
The console chat logs have no timestamp though, and again they're only good for a map or two until they get cleared out of the console. And shot logs are hugely useful, how many times have people claimed T-baiting, or "you shot at me", or "I saw you throw a harpoon", "you placed C4", "you threw a nade" etc. etc.
The reason I say shot logs are not that useful is because they do not show time stamps that are concurrent with when it actually happened. Obviously they are still used, but I'm not even sure if it's possible to extend them past the current map.
I'm not sure what you mean. The timestamps from the shot logs are only really useful for matching them up with chat logs. Other than that, the point of the shot logs is to determine what order things happened in. If person A shot person B before B shot A, then you know who instigated the gunfight and potentially if they RDM'ed.
Example 1 Example 2 The above was taken just now. What happens with shot logs after a while, is that the older shots disappear from the top and are replaced by new "shots" that come in. To illustrate, in the 1st picture it says 00:01 - ELCAPOGUZMAN has shot with a Crowbar. This does not necessarily mean that at 1 second into the game this player used their crowbar. In this case things do match up with exactly what happened, because I happened to screenshot it as the game was starting. But after a while they are not accurate.
Couldn't we modify the system to write shot logs to file (with a real timestamp) as they come up then? Seems like a fairly easy thing to do.
Well I mean I know it's possible, and then so people don't have to retrieve the files to get the logs, we could have a page on the website here where all the past shot logs are forwarded so people can browse them and post them on reports and such. I can even do it but I don't have the log system source code or anything like that.
-1. I have TTT Damagelogs on my server. If you don't clear old logs (Which most likely auto clears), it lags the server out. Imagine having to wait 2 seconds for the menu to open. Now it takes 4-5. -1
??? I said we should write them to file and have them accessible through a web interface. How would that lag the server..
The damageinfos shot logs in old damage logs will sometimes appear of the logs are recent. We currently don't have a time stamped chat log and I think that would be the first step if you were to want that saved. Even then, it could only provide so much information given the fact that some players use mics.
Chat logs have been suggested http://www.seriousttt.com/threads/kos-logs.13684/ http://www.seriousttt.com/threads/text-chat-with-time-stamps.12488/ Spoiler Please search before suggesting I don't see why shot logs for previous rounds would be needed really. Normally, if a mod needs to go back to previous logs it's usually to find a kill, Though this may help with a forum report/appeal however If this becomes a constant problem, I recommend recording demos and reporting on the forums if a word v. word situation happens
Do you mean these? Spoiler It shows the shot logs between the players involved in the last 10 seconds upon right clicking. So, they cannot exactly get away with "They t baited" [kinda]. Kinda, as in, traitorous acts do not expire..so if the player actually t baited, the actual shot logs will show[These logs stay for the map rotation or occasionally also till they become old logs]. However, the shot log tab is tmi for most of the staff members; as in, that thing goes on for 30 pages or so.. It's too complicated. Usually, players react right away for t-baiting. So, that's not always the issue. But for when it is, as if the player claims he t-baited about 21 seconds in, I would personally just spectate the responding player to make sure he does not loophole troll. As far as chat logs go, just as what others have stated, people use the mic chat 70% or the time unless when it's pressed for a command. So... going main down, the one time our staff members would actually need this is when a t buddy throws a nade and warning it with his command after releasing it. In this very situation, they would be useful. But, I would rather just encourage to let one of these cases slide.. if it happens one more time, then start recording. The demo files take very low space.
