Third party [Server] numSnapshotEntities wrapping

[Valkyrie]

Hello, there was this message showing up in the console during one of the (many) crash Sentinel is undergoing daily : Restarting server due to numSnapshotEntities wrapping

Here is a copy of the screenshot :

There was no crashlog generated.

 

[Spaghetti]

There was no crashlog generated.

Because it's not a crash.

// this can happen considerably earlier when lots of clients play and the map doesn't change
if ( svs.nextSnapshotEntities >= 0x7FFFFFFE - svs.numSnapshotEntities ) {
    SV_Shutdown( "Restarting server due to numSnapshotEntities wrapping" );
    Cbuf_AddText( va( "map %s\n", Cvar_VariableString( "mapname" ) ) );
    return;
}

This is engine code that is unmodified by OpenJK's changes. The solution is simple: Don't stay on the same map forever with a large number of players. Do a map change every once in awhile. Probably once every 20 duel mode rounds or so. Which means you just need to set a round limit.

 

[Valkyrie]

Because it's not a crash.

// this can happen considerably earlier when lots of clients play and the map doesn't change
if ( svs.nextSnapshotEntities >= 0x7FFFFFFE - svs.numSnapshotEntities ) {
    SV_Shutdown( "Restarting server due to numSnapshotEntities wrapping" );
    Cbuf_AddText( va( "map %s\n", Cvar_VariableString( "mapname" ) ) );
    return;
}

This is engine code that is unmodified by OpenJK's changes. The solution is simple: Don't stay on the same map forever with a large number of players. Do a map change every once in awhile. Probably once every 20 duel mode rounds or so. Which means you just need to set a round limit.

Thanks you. It was also peaking my curiosity on why there was no crashlog indeed. You answered that!
Regarding the round limit, it is set to 50 (roundlimit and fraglimit, both are set)

It appears nothing happens (score isn't... scored) at the end of a round. Which lead to the map not accounting any limit in rounds.

 

[Spaghetti]

If duel mode is not incrementing the round limit counter then that is a separate issue which we could fix.