Scribd
Upload
3 views1 page

Game Connection Warning Logs

The document contains a series of warnings related to a game server, indicating that the specified game is invalid and that multiple connections have exceeded their packet quota after re-sending packets. The warnings are logged with timestamps and detail the connection IDs and the maximum packet limit. Additionally, there is a note about the processing time for active block modifiers.

Uploaded by

lucync2015
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
3 views1 page

Game Connection Warning Logs

The document contains a series of warnings related to a game server, indicating that the specified game is invalid and that multiple connections have exceeded their packet quota after re-sending packets. The warnings are logged with timestamps and detail the connection IDs and the maximum packet limit. Additionally, there is a note about the processing time for active block modifiers.

Uploaded by

lucync2015
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

-------------

Separator
-------------

2025-07-13 16:12:30: WARNING[Main]: Game specified in default_game [default] is


invalid.
2025-07-13 16:13:55: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:14:00: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:14:01: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:14:02: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:14:03: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:14:03: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:14:07: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:14:08: WARNING[ConnectionSend]: con(49/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:06: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:07: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:07: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:07: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:07: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:08: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:09: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:11: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:11: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:12: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:15: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:16: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:19:43: WARNING[ConnectionSend]: con(33/1) Packet quota used up after
re-sending packets, max=1024
2025-07-13 16:20:14: WARNING[Server]: active block modifiers took 213ms (processed
214 of 267 active blocks)

You might also like