|
Post by /-/NOX!UZ on Apr 10, 2020 22:15:06 GMT -5
The issues with max_chars_exceeded started it seems after I updated the message of the day and some server messages.
Literally , all I did was expand the intro message and try to include 2 more in game messages about kicking specs during high player volume.
After removing all these changes, things seem to be running fine.
Its beyond me that these small changes started effing things up...
So it seems the size of the server config file has an undeifned limit, in kb it seems, for whatever reason, and when going past that limit causes weird behavior.
The constants connection interruptions on the other hand are most likely due to tens of millions of people stuck at home and on the internet across the US and in NY where the server is hosted.
|
|
moon
Lance Corporal
Posts: 123
|
Post by moon on Apr 23, 2020 16:41:22 GMT -5
|
|
|
Post by /-/NOX!UZ on Apr 24, 2020 21:28:33 GMT -5
Aight smartbutt tell me what I missed!
All jokin aside, if you know theres a certain kb or mb limit to the config file.. or what went wrong, all knowledge appreciated!!!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 25, 2020 19:51:41 GMT -5
The phrase comeuppance for ole Noxie comes to mind... LMAO
Or would it be "just rewards"
Sorry... couldn't help myself......Lol Lip
|
|
|
Post by /-/NOX!UZ on Apr 26, 2020 20:17:50 GMT -5
Lip!
Miss ur arse... legit.
Drop by often and shoot the shit, either in game or on forums.
Youll always be /-/ in my heart... you cigar smokin comudgeon.
|
|
moon
Lance Corporal
Posts: 123
|
Post by moon on May 3, 2020 0:44:37 GMT -5
@nox
First keep in mind this error is not a bug or caused only by any one particular thing; it's a resource limit that has been exceeded. The server must update the client with lots of information, and depending on the type of information and how dynamic the data is, there are different ways and therefore different buffers used to send that information to clients. One such mechanism is commonly known as "CONFIG STRINGS". The mechanism is fairly simple. The server sets and tracks the value of up to 1024 different strings and spits each string as it changes out to every client. When modifications/scripts are added to the server it causes more data to be sent out to all clients. So more config strings, and thus, more information is added that is sent to each client. So the problem is the TOTAL information combined in ALL CONFIG STRINGS must not exceed 16000 bytes (chars). If it does, the game spits out that error. So, to be specific, my guess is the character string issue is a result of additional lengthy messages:
#define MAX_GAMESTATE_CHARS 16000 typedef struct { int stringOffsets[MAX_CONFIGSTRINGS]; char stringData[MAX_GAMESTATE_CHARS]; int dataCount; } gameState_t;
Keep messages short and sweet to avoid the error...
|
|