QueuedSudo: Delayed Commands for Minecraft Servers

QueuedSudo: Delayed Command Execution for Minecraft Servers Running a Minecraft server often means juggling dozens of administrative tasks, from teleporting players to running scheduled commands. Essentials /sudo is a staple for many admins, but it lacks one critical feature: the ability to delay...

Download QueuedSudo for Minecraft 1.9

Original name: QueuedSudo

Minecraft: 1.9

FileVersionLoaderSize
QueuedSudo-v0.4.2-beta.jar1.9—68 КБDownload
QueuedSudo-v1.0.0-rc1.jar1.9—79 КБDownload
QueuedSudo-1.1.0-RC.jar1.9—94 КБDownload

QueuedSudo: Delayed Command Execution for Minecraft Servers

Running a Minecraft server often means juggling dozens of administrative tasks, from teleporting players to running scheduled commands. Essentials /sudo is a staple for many admins, but it lacks one critical feature: the ability to delay a command until a player actually joins a specific world. That is exactly the gap QueuedSudo fills. Instead of firing a command immediately and hoping the target is online, this plugin queues your instruction and executes it the moment that player steps into the world you specify. Think of it as a smart, patient version of /sudo that respects server context and player presence.

What Makes QueuedSudo Different

Traditional /sudo commands run instantly on a player who is currently connected. If the player is offline or in a different dimension, the command fails or behaves unexpectedly. QueuedSudo changes the game by allowing you to attach a world condition. You can tell the server: “Run this chat message or command as PlayerX, but only when they join the Overworld,” or “Execute this console command as PlayerY the moment they enter the Nether.” This is invaluable for adventure maps, minigame lobbies, or any setup where world-specific triggers matter.

The plugin is currently undergoing a major overhaul, and development builds are available on GitHub. The core concept remains simple: a single command with a few flags that gives you granular control over when and where a sudo action fires. There is no clutter, no bloated config—just a focused tool for a specific server-side need.

Installation and Dependencies

Setting up QueuedSudo requires a couple of library plugins. You will need Kotlin (at least version 1.5.0) and HikariLib (version 0.3.3-beta or newer, as the plugin was tested against that release). Make sure both are placed in your server’s plugins folder before dropping in the QueuedSudo JAR. If you prefer a hassle-free setup, you can manage these dependencies through a modern launcher like foxygame.net, which lets you browse, install, and update mods and plugins directly from its menu. This approach saves time and ensures you always grab the correct versions without digging through multiple download pages.

After a restart, the plugin will generate a default configuration. By default, QueuedSudo sends one request to GitHub on startup to check for updates. This can be disabled inside the config file if you prefer complete offline operation. HikariLib also performs its own update checks, but rest assured that no personal data is ever transmitted. The built-in /hpm commands only fetch or download when you explicitly tell them to, and all network activity is strictly read-only—no uploading or posting occurs.

Permissions and Command Usage

The permission node is refreshingly minimal. Only queued-sudo.admin is required to use the plugin’s features. An important safety net: any player with OP status will automatically ignore all queued sudos directed at them. This prevents accidental abuse where an admin could be forced to execute unwanted commands. Additional permission nodes may be introduced in future updates based on community feedback.

The sole command is /queuedsudo. Running it without any arguments opens a clean graphical user interface (GUI) where you can manage existing queues visually. For command-line enthusiasts, the full syntax is:

  • /queuedsudo <player> --group <groupName> [-c | -o] --executable <chat/command>

Here is what each flag does:

  • <player> – The target player who will run the command or send the chat message.
  • --group <groupName> – The world group where the execution should happen. For example, “survival” or “lobby”.
  • -c – Execute the action as a chat message (the player will say it in chat).
  • -o – Execute the action as a command (the player runs the command).
  • --executable <chat/command> – The actual message or command string to run. If you use -c, this is the chat text. With -o, this is the command without a slash.

For example, to make player “Steve” say “Hello world” in the survival world group when he next joins it, you would use:

/queuedsudo Steve --group survival -c --executable "Hello world"

To run a command like /spawn as Steve when he enters the lobby group, you would type:

/queuedsudo Steve --group lobby -o --executable "spawn"

The GUI provides an even friendlier way to build these entries, showing all active queues and letting you cancel them with a click.

Practical Use Cases

QueuedSudo shines in scenarios where timing and world context are everything. Here are a few ideas:

  • Adventure maps: Automatically give a player a quest item or display a hint when they enter a puzzle room world.
  • Minigame hubs: Run a command that teleports a player to a team selection area the moment they join the minigame world.
  • Roleplay servers: Make a character speak a line of dialogue as soon as they walk into a tavern region (using a world group that matches that area).
  • Maintenance tasks: Queue a cleanup command for a player who is currently offline but will log into a specific world later.

Under the Hood and Future Plans

The plugin is actively being reworked, so you may encounter development builds with experimental features. The author welcomes suggestions via Discord (hawu#8223). The codebase relies on Kotlin for its concise, modern structure and HikariLib for streamlined database and messaging utilities. Because QueuedSudo only reads input streams from its update checks and never uploads anything, it remains lightweight and privacy-conscious.

If you run into any issues, remember that OP players are immune to sudos by design. Also double-check that your world groups match exactly what your server uses. The plugin does not create worlds or groups; it simply listens for a player’s join event in a group you define.

Conclusion

QueuedSudo takes a familiar admin tool and gives it the patience it always needed. By deferring command execution until a player enters a chosen world, it opens up creative possibilities for automation, storytelling, and server management. The setup is straightforward, the permissions are simple, and the GUI makes queue management painless. Whether you are building an elaborate adventure or just want to tidy up your server’s command flow, QueuedSudo is a smart addition to your plugin roster.