Server Menus and AFK Management: GUIPlus + AntiAFKPlus

Two halves of a server that feels run

Menus and AFK handling sound like unrelated problems — one is front-of-house UX, the other is housekeeping — but they are two halves of the same impression: does this server feel looked after? Vanilla Minecraft gives you neither. There is no built-in way to open a shop or a warp list from a command, and the vanilla server does nothing about a player who parks at a grinder overnight and holds a slot the whole time. Both gaps get filled by plugins, and both are easy to fill badly: menus that are static item grids with nothing behind the clicks, and AFK kickers that boot a donor mid-conversation because the timer treats everyone the same. Before looking at our two utilities, fix the checklist.

• Menus need logic, not just icons — A button a player cannot afford should know that before the click goes through — which takes conditions on balance and permissions, not just a command bound to a slot.
• Editing workflow decides how much you iterate — If every menu tweak means editing a text file and restarting, you will stop tweaking; an editor you can use live is what keeps menus maintained.
• AFK rules must respect ranks — A flat kick timer hits staff and donors first; thresholds and bypasses need to be permission-aware from the start.
• Detection should be honest — AFK should mean no movement, chat, or interaction — and the plugin should let the rest of your stack vouch for a player before it acts.

GUIPlus: menus with the logic built in

GUIPlus is our GUI editing suite: €14.99 one-time (price at time of writing), for Spigot and Paper 1.16 through 26.2. Its defining feature is that you build menus without leaving Minecraft — the system menus handle the heavy lifting, so every item, condition, click event, scene and chat fetcher is click-to-configure, and menus you already have can be converted: drop your DeluxeMenus and custom GUI folders into plugins/GUIPlus and the converter takes care of them.

The logic layer is what separates it from a static menu. Conditions gate any item or scene on permissions, balance, level, XP, cooldowns, items held or empty inventory slots, integer and double checks and a conditional placeholder, each with its own fail message. Twelve click event types run commands, message the player, send titles, close inventories, give, set or remove money, give custom items, open chat fetchers or player pickers, and save information per player — a bank balance, say — for later use. Economy plugs into the economy plugin you already run with has-money conditions and money-remove / money-give events, so charging for a button is a config entry, not a script. Custom items survive the trip: NBT support means items from ItemsAdder, Oraxen, Nexo, and AdvancedEnchantments work in menus, and the Item Cloner quickly adds new items by cloning an existing one. One thing to be clear-eyed about: GUIPlus is the interface and the logic, not the feature underneath — the kit, warp, or crate behind a button is still delivered by a command chain to whatever plugin owns it.

The presentation layer is equally deep. Animated lores cycle any sequence of lore lines on an item, written in the in-game lores editor with no programming. Animation Scenes build any menu animation you want, open conditionally — show scene A, check the conditions, show scene B — and link up with other plugins through events. The Player-Picker runs a command against a chosen online or offline player from inside a menu, the Chat Fetcher prompts for free-form input in chat and pipes the response into its click event when the conditions pass, and aliases register no-prefix commands — /shop, /bank, /warps, /crates — including taking over a command from another plugin. If the menu you are wiring up is a crate-key shop, pair this with the criteria in our crates plugin guide.

AntiAFKPlus: AFK management that is actually free

AntiAFKPlus is free — not freemium, not a trial, simply free — and covers Spigot and Paper 1.7 through 26.2. Detection watches movement, chat, and interaction, each independently toggleable, and an API lets you register custom triggers — block-break, inventory-open, anything — so activity your server considers legitimate keeps the timer alive. Thresholds are per-rank and config-driven: 5 minutes for guests, 30 for donors, unlimited for staff, or whatever your ladder looks like, and the antiafkplus.bypass permission grants total exemption for staff on deep tasks.

What happens at the threshold is entirely up to you. The built-in actions are kick, teleport (to a hub world or safe zone), broadcast, and executing any console command with player placeholder substitution — and they chain, so a single config can warn at 5 minutes, teleport at 10, and kick at 20. Each action is its own config entry with its own permission node. It also plays fair with the rest of your stack: AntiAFKPlus defers to plugins that explicitly mark a player "active-ish" — FarmLimiter is the stated example — and only triggers when no other plugin says otherwise.

For networks and integrations: every AFK-related value is exposed through PlaceholderAPI — %antiafkplus_status% returns 'active' or 'afk' and %antiafkplus_idle_seconds% gives numeric idle time for threshold-based displays — cross-server AFK sync works out of the box on BungeeCord and Velocity, and an event API (PlayerAfkEvent and PlayerReturnEvent) lets addon plugins react. The free-versus-paid logic mirrors what we wrote in LPC Free vs LPC Pro: when a free plugin covers the whole job, the honest advice is to install it and keep your money — and for AFK management, this free plugin is the whole job.

Side by side, and where they connect

These are complementary tools, not a bundle — neither requires the other, and there is no discount for running both. They are also very differently shaped products, which the table makes plain.

The connection point is PlaceholderAPI. AntiAFKPlus exposes its state as placeholders precisely so other plugins can read it without hooking in directly, and GUIPlus conditions can branch on PAPI placeholders — so a menu can react to AFK state, showing a status line built from %antiafkplus_status% or gating a button on %antiafkplus_idle_seconds%. Both plugins also speak fluent commands: GUIPlus click events run command chains and AntiAFKPlus actions execute console commands, so each can drive the rest of your stack without custom code.

When each is worth installing

The decision here is simpler than most plugin choices, because one of the two costs nothing.

• AntiAFKPlus: if AFK players cost you anything, install it — It is free, lightweight, and permission-aware; the only real question is whether you need an AFK policy at all — if slots fill up, grinders run overnight, or idling earns rewards on your server, you do.
• GUIPlus is worth €14.99 if… — Your players interact with the server through menus — shop, warps, kits, bank — and you want conditions, economy hooks, and animations behind those clicks, edited in-game rather than in YAML.
• Skip GUIPlus (for now) if… — Your server has no real menu surface — a small whitelist SMP where everything happens in chat and commands — because a GUI editor with nothing to edit is shelfware.
• Run both when… — You operate a public server with a menu-driven hub and contested player slots: GUIPlus handles the front door, and AntiAFKPlus quietly keeps the population honest behind it.