Aikar adc43dff10
Run timings reports after end of tick ...
I believe we are getting data corruption by doing it in the middle of the tick, as I was seeing
really odd reports from automated ones vs command ones.
This will break issueing timings over rcon single command mode and getting the report link in the response back
But I will try to restore that (and make RCON no longer cause spikes) soon.
Reports will still generate, just because its async, the RCON connection
will drop if not in terminal mode before its done.
2017-02-04 20:46:27 -05:00
2016-03-26 22:23:42 -07:00
2016-03-18 00:24:00 -04:00
2016-12-21 11:53:41 -06:00
2016-02-29 17:09:49 -06:00
2016-12-20 16:34:27 -06:00
2016-02-29 17:09:49 -06:00
2016-10-30 00:13:31 -05:00
2016-10-30 21:42:38 -05:00
2016-08-27 18:41:58 -05:00
2017-01-20 09:01:53 -06:00
2017-01-06 15:45:59 -06:00
2016-04-13 20:23:07 -07:00
2016-03-28 22:43:05 -04:00
2016-03-27 20:48:50 -05:00
2017-01-30 22:33:54 -06:00
2016-02-29 17:09:49 -06:00
2016-03-03 03:46:26 -06:00
2016-04-02 18:10:38 -07:00
2016-12-16 22:13:45 -06:00
2016-03-18 00:29:35 -04:00
2016-11-30 17:31:46 -06:00
2017-01-06 15:45:59 -06:00
2016-04-01 00:18:18 -04:00
2017-01-06 15:45:59 -06:00
2017-01-20 05:21:44 -06:00
2016-02-29 17:09:49 -06:00
2016-03-11 22:30:18 -06:00
2016-03-08 22:23:59 -08:00
2016-03-19 09:57:19 -07:00
2016-06-24 00:16:46 -04:00
2016-11-18 23:58:56 -05:00
2016-03-28 21:24:45 -04:00
2016-11-16 20:23:38 -06:00
2017-01-06 15:45:59 -06:00
2017-01-25 22:27:42 -06:00
2017-01-06 15:45:59 -06:00
2016-02-29 17:09:49 -06:00
2016-12-20 16:34:27 -06:00
2017-01-06 15:45:59 -06:00
2016-11-19 11:31:01 -06:00
2016-02-29 17:09:49 -06:00
2016-11-23 13:02:47 -05:00
2016-02-29 17:09:49 -06:00
2016-12-20 16:34:27 -06:00
2017-01-06 15:45:59 -06:00
2016-12-21 11:21:40 -06:00
2017-01-13 23:00:33 +11:00
2016-03-28 22:10:01 -04:00
2017-02-04 20:46:27 -05:00
2016-03-12 09:43:39 -07:00
adc43dff10