/tg/Station 13

I've made runtime logs public for anybody to download. All ips (based on a regex) are replaced with -censored- but it's otherwise been left alone.

https://tgstation13.org/parsed-logs/

It's not automatically updating yet, but when it is, it will update about every hour at 10 after 15 minutes and will not show runtimes for the last round if another round hadn't started yet.

It's happening ~

Automatic update is happening, it happens at 10 after.

Added parsing of runtimes into their condensed form using the runtime condenser

With a bit of (awful, awful) regex, I've got the logs parsed and loaded into MySQL.

On June 28th, there were 348 explosions, 857 instances of someone 'Seizing up and falling limp' (three of which were me), 101 law changes, 284 items spawned by admins, 11 people saying 'got wood' and so on and so forth.

It would be better to log some of that stuff directly rather than needing it to be parsed, but cool nonetheless.

Runtime logs will now roll over at the end of the day.

Both servers now have -verbose to prevent not displaying runtime logs or the stack trace.

More Info: http://www.byond.com/forum/?post=1886190

>first day of -verbose
>first day my PR is on the server
>The following runtime has occured 286793 time(s).
>my fault
>mfw

duncathan wrote:>first day of -verbose
>first day my PR is on the server
>The following runtime has occured 286793 time(s).
>my fault
>mfw

But at least we know. It's better to know than to pretend there's no problem.

As of last round, the public runtime logs now include a log of the GC failures. GC failures are also condensed. Happy reference hunting.

Why aren't these being updated anymore? Last one was on the 5th.

DrPillzRedux wrote:Why aren't these being updated anymore? Last one was on the 5th.

(because in reality, nobody gives a shit about them, they just like to whine about transparency.)

No actually there's a very good reason they've not been updated.
The admins would rather you not know though as it makes it more of an issue.

They'll probably be back up soon.

the runtime logs are actually very useful

There was a change in log format for asay

I had to rewrite the log parser.

A bug was causing it to runtime and not get to the final step of pushing the update to the publicly visible folder.

I think i fixed it, we shall see at 10 after when it re-parses the logs that were uploaded at the top of the hour.

How do I fid out if an antag won or not. (I had to leave mid round so I camped out in a escape pod)

dapocalypse wrote:How do I fid out if an antag won or not. (I had to leave mid round so I camped out in a escape pod)

This is the wrong thread for that.

Try this site:
https://atlantaned.space/statbus/round.php

You can try to find what you're looking for there. I don't think you can check if an individual traitor won though.

TribeOfBeavers wrote:I don't think you can check if an individual traitor won though.

This data is not tracked. We know who was an antag, what the objectives were, and the overall success rate, but not who did/had what.