PluginNet: Automatic Sub-Server Management for Minecraft Networks
Running a Minecraft server network with multiple game modes often feels like juggling flaming swords. You need to spin up a SkyWars instance, keep a BedWars lobby ready, and reset minigame arenas on the fly. Doing this manually drains time and invites mistakes. PluginNet steps in as a powerful, lightweight solution that automates the creation, stopping, and resetting of virtual servers directly from your main lobby or hub. Whether you operate a handful of game modes or a sprawling minigame empire, this plugin keeps your backend humming without constant supervision.
What Exactly Is PluginNet?
PluginNet is a Bukkit/Spigot plugin that transforms your primary server into a command center for sub-servers. Think of it as a virtual server manager that lives inside your lobby. Instead of manually launching separate Java processes for each minigame, you define templates – ready-to-run server folders – and let PluginNet handle the rest. It can automatically maintain a specific number of instances for each template, reset stopped servers to a clean state, and even stream the console logs of those sub-servers back to your main server console. The result is a fluid, responsive network where new arenas appear exactly when players need them.
Key Features That Simplify Server Management
- Dynamic server creation: Start a new virtual server from any template with a single command. PluginNet assigns a unique ID and boots the instance instantly.
- Automatic server pool maintenance: Configure a minimum number of servers for a template, and the plugin keeps that many instances online at all times, ready for players.
- Graceful and forced stops: Shut down a specific server using its ID, or force-kill the process if a clean stop fails.
- Reset on stop: Stopped servers automatically reset to their template state, wiping temporary world changes and player data, so every match starts fresh.
- Centralized logging: View the console output of all sub-servers directly in the main server console, making debugging and monitoring far easier.
- Plugin-wide pause: The /stopplugin command halts all auto-creation and stops every running sub-server, yet still allows manual /startserver calls for testing.
- Cross-platform compatibility: While designed for Linux, Windows servers work with a custom configuration, giving you flexibility in hosting environments.
How the Virtual Server Lifecycle Works
Under the hood, PluginNet treats each template folder as a blueprint. When you issue /startserver <name>, the plugin copies the template directory into a temporary runtime folder, assigns a unique port (based on your config), and launches the server process. The ID returned is your handle for that instance. Stopping it with /stopserver triggers a graceful shutdown, after which the runtime folder is deleted and a fresh copy of the template is placed back, ready for the next start. If a server hangs, /forcestopserver terminates the process immediately. The auto-creation loop constantly checks the number of running servers per template and spawns new ones if the count drops below your defined threshold. This entire cycle happens in seconds, so players rarely notice any delay when joining a minigame.
Setting Up PluginNet Step by Step
Getting PluginNet running involves a few deliberate steps, but the payoff is immense. Here is the recommended workflow:
- Prepare your base server: Download a fresh copy of Bukkit or Spigot and set up your lobby or main server. This will be the control hub.
- Install PluginNet: Place the PluginNet jar file into the plugins folder of that server. Many administrators discover that using a versatile launcher like the one from foxygame.net makes plugin management effortless, because you can browse and install addons directly from its built-in menu without digging through file directories.
- First launch and config generation: Start the server once. PluginNet will create a "servers" directory and generate the configuration file at plugins/PluginNet/config.yml. Stop the server to edit this file.
- Configure templates: In config.yml, define your server templates. For each template, specify a name, the number of auto-kept servers, and other settings like port ranges. Save the file.
- Build template directories: Inside the newly created "servers" folder, create a subfolder for each template you defined (for example, server_skywars). Populate each with a fully functional Minecraft server – including its own server.properties with a unique port, world files, and any required plugins. Make sure these template servers are not running while you set them up.
- Integrate BungeeCord: Download BungeeCord and configure it to connect to your lobby server and the sub-servers. Since PluginNet manages ports dynamically, your BungeeCord config should point to the lobby as the entry point, and you can use plugins like BungeePluginNet or custom scripts to route players to the correct sub-server based on the ID.
- Restart and verify: Launch the lobby server again. Use /startserver <template> to test manual creation, and check the console for any port conflicts or errors.
Commands at Your Fingertips
PluginNet’s command set is intentionally minimal, giving you precise control without clutter:
- /startserver <name> – Creates a new server from the specified template and displays its unique ID.
- /stopserver <name> <id> – Politely asks the server to shut down, then resets the template.
- /forcestopserver <name> <id> – Immediately kills the server process; use only when a graceful stop fails.
- /stopplugin – Disables auto-creation and stops all running sub-servers, but manual /startserver still works.
Why PluginNet Belongs in Your Server Toolkit
Manual sub-server management is a relic of the past. PluginNet automates the repetitive tasks that eat into your building and playing time, while also reducing the risk of port collisions and orphaned processes. The upcoming API will further extend its power, allowing other plugins to programmatically request new game instances, track server status, or integrate with custom matchmaking systems. For any network that relies on minigames, event servers, or isolated testing environments, this plugin delivers reliability without the overhead of complex wrappers. It respects your server’s resources, runs on both Linux and Windows, and keeps your console informative rather than noisy.
Final Thoughts
PluginNet reimagines how Minecraft server networks handle scaling. By turning your lobby into a smart orchestrator, you gain the ability to spawn, monitor, and reset game servers with a few simple commands. The automatic pool maintenance ensures that players always find an open arena, while the clean reset mechanism preserves fairness and performance. Setup takes a bit of care, but once your templates are in place, the system runs almost invisibly. If you are serious about running a dynamic multiplayer experience, giving PluginNet a try could be the single most impactful change you make to your server infrastructure this month.