2014-04-06T10-36-37: LogOut_File: : logfile started
2014-04-06T10-36-37: Net Status: low-level initialize success.
2014-04-06T10-36-37: Note that this new version (12/19/2011) has reduced the frequency of updates so the numbers will be larger
2014-04-06T10-36-37: time = time of logging
2014-04-06T10-36-37: address = address of IP address
2014-04-06T10-36-37: incoming = total size of messages set to me in bytes. Spikes can indicate lag.
2014-04-06T10-36-37: outgoing = total size of messages set from me in bytes. Spikes can indicate lag.
2014-04-06T10-36-37: app_ctos = client to server bytes delta excluding overheads (app data only)
2014-04-06T10-36-37: app_stoc = server to client bytes delta excluding overheads (app data only)
2014-04-06T10-36-37: loss = number of packets lost. Can indicate lags.  Some node on the network is dropping packets or taking to long and we have to resend them.
2014-04-06T10-36-37: sent = number of packets sent. Spikes can indicate lag.
2014-04-06T10-36-37: ping = how long it takes for a packet to get back and forth. Spikes can indicate lag.
2014-04-06T10-36-37: variance = how much the ping is changing from avg ping. Spikes can indicate lag.
2014-04-06T10-36-37: reliable delayed = This occurs when we drop reliable packets from sending this frame because we are sending to much data. Unreliable are more likely to be dropped than reliable.
2014-04-06T10-36-37: unreliable delayed = This occurs when we drop unreliable packets from sending this frame because we are sending to much data.
2014-04-06T10-36-37: app update delayed = This occurs when the app is taking to long to run code caused by network packets (ie CPU) and packets are delayed until the next frame
2014-04-06T10-36-37: Time spent in critical section (frame) = This is the time the network thread is blocking the main thread from doing anything.
2014-04-06T10-36-37: [time], [address], [incoming], [outgoing], [app_ctos], [app_stoc], [loss], [sent], [ping], [variance], [reliable delayed], [unreliable delayed], [app update delayed], [Time spent in critical section (frame)]
12694,X.X.X.X,16543,2608,15202,764,4,88,191,9,0,0,1,0
25047,X.X.X.X,22423,3488,5915,0,13,99,191,8,0,0,1,0
35221,X.X.X.X,29849,4772,7391,150,20,111,195,10,0,0,1,0
45521,X.X.X.X,30005,5512,116,580,22,113,195,10,0,0,1,0
55822,X.X.X.X,30005,6252,0,580,24,115,195,10,0,0,1,0
2014-04-06T10-37-38: 162.249.74.121 disconected.
2014-04-06T10-37-38: ------------------------------------------------------------------------------
2014-04-06T10-37-38: ===== START SUMMARY FOR: 162.249.74.121
2014-04-06T10-37-38: ------------------------------------------------------------------------------
2014-04-06T10-37-38:    Packet Type totals (<- in, out ->):
2014-04-06T10-37-38:  Note that the count for PKT_Dummy is not an actual packet type, it indicates unknown packets that were not properly initialized with a type.
2014-04-06T10-37-38: ID: 0 Count: 5 Bytes: 160 <- |
2014-04-06T10-37-38: ID: 3 Count: 1770 Bytes: 19823 <- |
2014-04-06T10-37-38: ID: 20 Count: 69 Bytes: 345 -> |||||
2014-04-06T10-37-38: ID: 22 Count: 60 Bytes: 1740 -> |||||
2014-04-06T10-37-38: ID: 26 Count: 1 Bytes: 23 <- |
2014-04-06T10-37-38: ID: 31 Count: 5 Bytes: 35 <- |
2014-04-06T10-37-38: ID: 46 Count: 1 Bytes: 17 <- |
2014-04-06T10-37-38: ID: 55 Count: 12 Bytes: 108 <- |
2014-04-06T10-37-38: ID: 79 Count: 2 Bytes: 44 <- |
2014-04-06T10-37-38: ID: 83 Count: 1 Bytes: 5139 <- |
2014-04-06T10-37-38: ID: 89 Count: 1 Bytes: 5 <- |
2014-04-06T10-37-38: ID: 98 Count: 1 Bytes: 407 <- |
2014-04-06T10-37-38: ID: 100 Count: 1 Bytes: 9 -> |
2014-04-06T10-37-38: ID: 101 Count: 5 Bytes: 116 <- |
2014-04-06T10-37-38: ID: 102 Count: 5 Bytes: 132 <- |
2014-04-06T10-37-38: ID: 103 Count: 1 Bytes: 401 <- |
2014-04-06T10-37-38: ID: 105 Count: 10 Bytes: 90 <- |
2014-04-06T10-37-38: ID: 109 Count: 73 Bytes: 657 <- |
2014-04-06T10-37-38: ID: 123 Count: 1 Bytes: 174 <- |
2014-04-06T10-37-38: ID: 135 Count: 3 Bytes: 18 <- |
2014-04-06T10-37-38: ID: 146 Count: 42 Bytes: 546 <- |
2014-04-06T10-37-38: ID: 148 Count: 9 Bytes: 261 <- |
2014-04-06T10-37-38: ID: