Mastering Server Automation with the InTime Plugin for Minecraft
Running a Minecraft server is like orchestrating a living, breathing world. Every plugin adds a unique flavor, from economy systems to minigames, but sometimes you want certain features to appear only at specific times of day or on certain days of the week. That is exactly where InTime steps in. This lightweight, no-nonsense server plugin gives you the power to enable or disable other plugins on a schedule, and even execute console commands at predefined moments. If you have ever wished that your PvP arena would automatically activate at sunset or that a nightly broadcast would remind players to sleep, InTime is the tool you need.
What Makes InTime Stand Out?
At its core, InTime is a scheduling engine for your server’s backend. Unlike many complex automation plugins that require learning scripting languages or setting up external cron jobs, InTime works entirely within your existing plugin configuration. It reads a simple YAML file and acts on it. The plugin is designed to be as minimal as possible, meaning it won't bloat your server’s memory or cause lag spikes. Despite its simplicity, it unlocks a surprising amount of creative potential.
The two main features are time-based plugin toggling and scheduled console commands. With plugin control, you can define a list of plugins and set time windows during which they should be either forcefully enabled or disabled. The command scheduler lets you fire any console command — complete with arguments — at a precise time, optionally restricted to a specific weekday. This opens doors to automated restarts, temporary world changes, timed giveaways, and much more.
Setting Up Time-Based Plugin Control
Configuring InTime is straightforward. After placing the plugin in your server’s plugins folder and restarting, a configuration file will be generated. Inside, you will find a section called plugins. Here, you list each target plugin by its exact name (as it appears in the /plugins list) and specify its behavior.
Each entry requires a type and a list of times. The type can be either enable or disable. If you set type: enable, the target plugin will be disabled by default and only become active during the time intervals you provide. Conversely, type: disable means the plugin is normally enabled but will be shut down during the specified periods. The time format uses a 24-hour clock, so you write ranges like 9:00-15:30 or 18:00-23:00. You can add multiple ranges to cover different blocks of the day.
A crucial rule to remember: a single plugin can only be managed as either enable or disable, never both. Attempting to mix types for the same plugin will lead to conflicts. Always decide whether you want the plugin to be mostly off and temporarily on, or mostly on and temporarily off.
Example Plugin Configuration
Let's say you have a minigame plugin called samplePlugin that you want to be available only during school hours and again in the evening. Your configuration would look like this:
plugins:
samplePlugin:
type: disable
times:
- 9:00-15:30
- 18:00-23:00
In this scenario, samplePlugin is normally enabled. InTime will automatically disable it between 9:00 and 15:30, and again between 18:00 and 23:00, effectively making it playable only outside those windows. If you reversed the type to enable, the plugin would be disabled by default and only become active during those exact hours.
Scheduling Console Commands with Precision
Version 0.2 introduced a powerful command execution feature. You can define multiple command entries under the commands section. Each entry gets a unique key (like a, b, c), the command itself, its arguments, and the time it should run. Optionally, you can add a weekday parameter to limit execution to a specific day — Monday through Sunday — or use all for every day.
All scheduled commands are executed as the console, meaning they have full server privileges. This is perfect for broadcasting messages, running /save-all, switching game modes, or triggering other plugin functions. The time must be written in the same 24-hour format, enclosed in quotes.
Command Configuration Examples
Here is a practical snippet that announces the start of a new day, says goodnight, and sends a fun Friday message:
commands:
a:
command: say
arguments: A new day starts....
time: '00:00'
b:
command: say
arguments: Good night!
time: '23:00'
c:
command: say
arguments: It's friday! Playing MC until we have to call the doctor!
time: '14:00'
weekday: Friday
Notice how the Friday command uses the optional weekday field. Without it, the command would run every day at 14:00. With it, the message only appears on Fridays. You can craft as many entries as you need, building a full weekly schedule of automated tasks.
Creative Uses for Your Server
The true beauty of InTime lies in its flexibility. Server owners have used it to rotate minigame availability, creating a dynamic experience where different games are active at different hours. Others use it to disable resource-intensive plugins during peak times to save performance. The command scheduler can be employed to run regular backups, clear dropped items, or even change the server difficulty based on the time of day. Because it works at the console level, it can interact with nearly any other plugin.
If you enjoy tinkering with your server’s behavior, you might also appreciate tools that simplify client-side modding. For instance, when you want to explore single-player modpacks or add visual enhancements, the foxygame.net launcher provides a convenient, flexible, and modern way to download and install mods directly from its menu, streamlining the entire process without manual file juggling.
Important Considerations and Limitations
While InTime is lightweight, keep a few points in mind. The plugin only supports 24-hour time format; 12-hour AM/PM notation is not available yet. Also, be cautious when disabling plugins that other systems depend on. If you disable an economy plugin while shops are open, you might break transactions. Test your schedule thoroughly on a private instance before going live.
Another subtlety: the plugin toggling happens based on the configured times, but if the server restarts inside a time window, InTime will correctly reapply the state. However, any manual changes you make via /plugman or similar tools might be overwritten at the next time boundary. It is best to let InTime be the sole manager of those plugins' states.
Support is available through private messages and a ticket system for bug fixes, though general comments on the plugin page may not receive replies. Always check the official resource page for the latest version and changelog.
Conclusion: Automate and Elevate Your Server
InTime is a shining example of how a small, focused plugin can dramatically improve server management. By automating plugin states and console commands, you reduce manual work and create a more immersive, ever-changing world for your players. Whether you run a small community server or a large network, the ability to schedule features adds a layer of polish that keeps players coming back. The configuration is simple, the performance impact is negligible, and the possibilities are limited only by your imagination. Give your server the gift of time-based intelligence, and watch your community thrive.