# XH-I01: The server refused a player's userinfo changes (/docs/xhlds/codes/xh-i01)

**Printed:** when the server refuses a player's `setinfo` or `fullinfo`, at most every 10 s per player, also in the server log.

A player's game sent `setinfo` or `fullinfo` commands that the server refused: their settings (userinfo) were full, or a key or value had characters it does not accept. The line names the player and their address, says how many changes were refused since the previous line and why. Each refusal goes to that player's console only; the server console gets one line per player at most every 10 s, also in the server log.

**Is it a problem?** A few now and then, no: some games and scripts send more settings than fit, and the player plays on. Hundreds or thousands every 10 s from one player is someone sending them on purpose: without the limit the server would print one line for each, which can freeze it.

**What to do:** for a few, nothing. For many, kick or ban the player (the address is on the line), and keep [`sv_rehlds_stringcmdrate_max_avg`](/docs/rehlds/settings#sv_rehlds_stringcmdrate_max_avg) and [`sv_rehlds_stringcmdrate_max_burst`](/docs/rehlds/settings#sv_rehlds_stringcmdrate_max_burst) at their defaults (250 and 500, not `-1` or `0`): then the server bans a player who sends commands that fast by itself.

## On the server [#on-the-server]

[`xhlds_explain XH-I01`](/docs/xhlds/commands#xhlds_explain) prints this explanation on the server console, also over rcon.
