Jump to content

Got another error


oliveirapt

Recommended Posts

Game and server kept running, but everybody just lost connection to Beginners #2 on [UJE] Fuel Dump with above error message. Server was close to being completely full.

  • 100 1
Link to comment
Share on other sites

55 minutes ago, Lt Steiner said:

Game and server kept running, but everybody just lost connection to Beginners #2 on [UJE] Fuel Dump with above error message. Server was close to being completely full.

If i remember correctly, Fueldump in any version is well known for causing that Problem.

especially when someone is giving ammocrates or medpacks infintely to the spawn, in order to do a little XP-farming.

it had something to do with too little com_hunkmegs on the clients. Clients need to have com_hunkmegs increased to above 128 or 512 something...

Edited by Vice86
  • 100 2
Link to comment
Share on other sites

Digging around the code and lore, looks like this happens when server has too many resources or entities. It could be to many PK3s. We had a lot of players in that map—meaning more entities like medpacks, bullets, and so on. See the following code snippets where it warns about exceeding the static parameter:

 

First snippet

// warn admins
if (cstotal > MAX_GAMESTATE_CHARS - 800) // 5% of MAX_GAMESTATE_CHARS
{
    Com_Printf(S_COLOR_YELLOW "WARNING: Your clients might be disconnected by configstring limit [%i chars left] - reduce the ammount of maps/pk3s in path\n", MAX_GAMESTATE_CHARS - cstotal);
}

 

Second snippet

if (len + 1 + cl.gameState.dataCount > MAX_GAMESTATE_CHARS)
{
    Com_Error(ERR_DROP, "MAX_GAMESTATE_CHARS exceeded");
}

 

Unfortunately, the configstring is a static parameter afaik; so I don't think we can configure it (the clients themselves need to dynamically allocate memory to make room for the growing configstring as well).

  • Like 1
Link to comment
Share on other sites

1 hour ago, Apollonius said:

Unfortunately, the configstring is a static parameter afaik; so I don't think we can configure it (the clients themselves need to dynamically allocate memory to make room for the growing configstring as well).

hence the increasing of com_hunkmegs?

Link to comment
Share on other sites

1 hour ago, Vice86 said:

hence the increasing of com_hunkmegs?

It needs to be dynamically increased, which is not possible as of now afaik. Yeah you can set it to a higher value, but that could fail (if it works that is), like in this case.

See specifically this comment and the one immediately following it: https://github.com/etlegacy/etlegacy/issues/588#issuecomment-830598045.

There's the compatibility issue as well so... 🤷‍♂️

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.