You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG]: rg_reset_user_model BUG? LAG IF 32 PLAYERS #364
When using the rg_reset_user_model function with update_index set to true, I noticed that during a mass respawn with 32 players, the server experiences significant lag, even freezing for a few seconds.
I’m still not sure whether this is actually a bug or just improper use of the function.
Yes, this is a known problem. rg_reset_user_model updates the userinfo immediately for all players, which can easily flood the network buffer if called on 32 clients at once (for e.g, during a mass respawn).
In AMXX cstrike module this was solved by deferring the updates (cs_reset_user_model), where model resets are postponed and processed gradually every frame.
So for now you should either:
use cs_reset_user_model (if possible in your plugin),
or wait until a similar deferred update mechanism is implemented in ReAPI.
Using rg_reset_user_model directly on many clients at once is not efficient and will cause lag/freeze.
Activity
s1lentq commentedon Sep 26, 2025
Yes, this is a known problem.
rg_reset_user_modelupdates the userinfo immediately for all players, which can easily flood the network buffer if called on 32 clients at once (for e.g, during a mass respawn).In AMXX
cstrikemodule this was solved by deferring the updates (cs_reset_user_model), where model resets are postponed and processed gradually every frame.So for now you should either:
cs_reset_user_model(if possible in your plugin),Using
rg_reset_user_modeldirectly on many clients at once is not efficient and will cause lag/freeze.