AntiAFKPlus

AntiAFKPlus watches for movement, chat, interaction, and custom actions to decide whether a player is really AFK. Every detection threshold is configurable; every consequence is permission-gated so staff and donors can bypass rules that apply to regulars.

• Movement + Chat + Interact — Default triggers; each independently toggleable
• Custom Action Hooks — Register your own triggers via the API — block-break, inventory-open, anything
• Per-Rank Thresholds — 5 minutes for guests, 30 for donors, unlimited for staff — all config-driven
• Bypass Permission — antiafkplus.bypass grants total exemption for staff on deep tasks

What happens when a player goes AFK is entirely up to you. Kick, teleport, broadcast, command-execute, or chain them together. Each action is its own config entry with its own permission node.

• Kick — Free up player slots by kicking AFK players after a threshold
• Teleport — Move AFK players to a hub world or safe zone
• Broadcast — Announce AFK status so other players know
• Run Commands — Execute any console command with player placeholder substitution
• Chain Multiple — Warn at 5 min, teleport at 10, kick at 20 — all from one config

Every AFK-related value is exposed as a PlaceholderAPI placeholder. Other plugins can read state without hooking directly. Cross-server AFK sync works out of the box with BungeeCord / Velocity.

• %antiafkplus_status% — 'active' | 'afk' — drops into scoreboards, tab lists, anywhere
• %antiafkplus_idle_seconds% — Numeric idle time for threshold-based displays
• BungeeCord / Velocity — AFK status follows players across servers on your network
• Event API — PlayerAfkEvent + PlayerReturnEvent for addon plugins to react

AntiAFKPlus documentation

The full manual is on this site — installation, configuration, commands and permissions, kept in step with the plugin’s own wiki.

• First Install
• Warning Stages & ActionsConfiguration
• AFK DetectionFeatures
• APIFor Developers
• FAQSupport