Configure an idle-player timeout on Minecraft Java

Minecraft Java can disconnect idle players after a chosen interval. This can be useful for a small community that wants abandoned sessions to leave automatically. It is an activity rule, not a guarantee that farms will stop running or that every AFK method will be detected. Plugins may implement different AFK policies alongside it.

Decide the policy before enabling it

Tell players how long they may remain inactive and whether staff have separate rules. Consider accessibility needs and time spent reading instructions or chatting elsewhere. Do not choose a very short interval solely to make the online list look tidy. A rule that repeatedly removes legitimate players creates more support work than it saves.

Check the plugin list for existing AFK or idle-kick features. If another system already manages this, decide which one should be authoritative. Two independent timers can produce inconsistent kick messages and make exemption permissions difficult to understand. Record the current player-idle-timeout value before changing anything.

Apply the built-in setting

Download server.properties privately, announce a restart and stop the server cleanly. Edit the existing entry, using minutes rather than seconds. This illustrative example sets a thirty-minute limit:

player-idle-timeout=30

A value of 0 disables this built-in timeout. Save and start the server. Keep the release in mind: consult the reference matching the installed Minecraft/Paper build, especially when comparing a 1.21.11 configuration with current 26.x documentation. Do not add duplicate keys or copy a YAML-style key: value line into the properties file.

The timer responds to recognised client activity. That is not the same as detecting whether a human is paying attention. Avoid promising that this setting prevents every idle machine, automated action or farming technique. If you need a different policy, describe the requirement before selecting a plugin rather than layering random exemptions.

Verify with an ordinary account

Run a supervised test during a quiet period using a non-operator account. Note the join time, leave the player safely positioned and wait through the selected interval. Record whether the disconnect happens and what message appears. Do not put the test player near hazards or carry valuable items for this check.

Then repeat with normal activity to confirm an active session is not being removed unexpectedly. If the timer seems inconsistent, check the server log for the actual kick reason. A proxy timeout, network disconnect or plugin kick is a different event. Testing with an administrator alone can hide permission-based behaviour introduced by plugins.

Undo or investigate

If the policy causes problems, restore the previous value, or set player-idle-timeout=0 during a clean stop and restart. Keep the test notes so staff can explain why the rule changed. No world or player inventory restoration is needed.

If all players leave and the server then appears paused, investigate the empty-server pause setting separately. If a player disconnects while actively playing, collect the relevant log interval and client message rather than increasing the idle limit without evidence.

Reference

Paper reference for idle timeout and empty-server pause.