Change Details

No idea what's causing this. The effects though, are increased server lag, and tons of log spam. No strong correlation seen with any other log entries, aside from perhaps ~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |head [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD ~$ grep -v PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l 19281 ~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l 33390 Only log entry that seems to intermix consistently is: [2016-05-25 14:25:25] [SERVER][RAIL] collision time limit reached. Returning to last possible

No idea what's causing this. The effects though, are increased server lag, and tons of log spam. ~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |head [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD ~$ grep -v PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l 19281 ~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l 33390 Only log entry that seems to intermix consistently is: [2016-05-25 14:25:25] [SERVER][RAIL] collision time limit reached. Returning to last possible

No idea what's causing this. The effects though, are increased server lag, and tons of log spam. No strong correlation seen with any other log entries, aside from perhaps ~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |head [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD [2016-05-25 14:10:43] PDLDLKDJLKDJLKDJLKDJLKDJDLKJD ~$ grep -v PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l 19281 ~$ grep PDLDLKDJLKDJLKDJLKDJLKDJDLKJD log.txt.1 |wc -l 33390 Only log entry that seems to intermix consistently is: [2016-05-25 14:25:25] [SERVER][RAIL] collision time limit reached. Returning to last possible