EXCLUSIVE RUST PLUGIN Rust Custom Event Scheduler 1.0.26

Rust Custom Event Scheduler​

Features​

• Randomized Event Queue — Events fire in a different order every cycle to keep gameplay fresh and unpredictable
• Smart Buffer Timing — Configurable random delay (min/max minutes) between every event keeps spawn timing varied
• Auto-Cycling — When all events have run, the list re-randomizes automatically and starts a new cycle
• Max Active Events — Control how many events can run simultaneously; prevents event stacking
• Discord Notifications — Rich embed messages for every scheduler action (load, queue, start, end, delay, cycle reset)
• Console Logging — Full console output for every scheduler action with local server time
• Player Command — Players type !events or /events — both are silent (not shown in chat), and the result broadcasts to all players so everyone benefits from the cooldown
• Dynamic Config — Add your own events by editing the config file — no code, no reload required on first load
• Local Server Time — All times display in your server's local timezone, auto-detected and abbreviated (e.g. CST, PST, EDT)
• Self-Managed Events — Events without a stop command (convoys, trains, etc.) are tracked by run time with no stop needed
• Managed Events — Events like boss monsters get an automatic stop command fired after their run time expires

Installation​

1. Download rCEventScheduler.cs
2. Place it in your oxide/plugins/ directory
3. Restart the server or run: oxide.reload rCEventScheduler
4. Edit the config at oxide/config/rCEventScheduler.json
5. Set your Discord webhook URL for admin notifications (optional)

Configuration​

Global Settings​

Per-Event Options​

Note: Events with an empty Event Stop Command are self-managed. The scheduler tracks their run time but does not issue a stop command — the event ends on its own (e.g. a convoy that despawns naturally).

Click to expand...

Note: If Required Plugin is set and that Oxide plugin is not loaded when the server starts, the event is silently omitted from the queue. A single warning message lists all skipped events and their missing plugins.

Click to expand...

Player Command​

Broadcast: The result is sent to all players on the server, not just the player who typed the command. Since the cooldown is global, everyone benefits from one trigger.

Click to expand...

Anti-spam: Both commands share a global 5-minute server-side cooldown. The player who triggers it during cooldown receives a private message showing seconds remaining — other players are not notified.

Click to expand...

[ My Rust Server Event Scheduler ][/FONT][/COLOR][/FONT][/FONT][/COLOR][/FONT]
[FONT=Mona Sans VF][COLOR=rgb(240, 246, 252)][FONT=Monaspace Neon][FONT=Mona Sans VF][COLOR=rgb(240, 246, 252)][FONT=Monaspace Neon]Active Events:
  ● Boss Monster Oni
Next Event: Convoy
Starts at: 4:23 PM CST  (~38 min)

The header uses your server's name automatically, pulled from ConVar.Server.hostname (your server.cfg hostname).

Click to expand...

Disable this command in config with "Enable Player Events Command": false

Click to expand...

Discord Notifications​

Event	Color	Description
Plugin Loaded	Blue	Lists all loaded events by name
Queue Randomized	Purple	Shows the new randomized event order
Next Event Scheduled	Teal	Event name, scheduled time, countdown, queue position, and events until reshuffle
Event Delayed	Orange	Max active events reached — shows new retry time
Event Started	Green	Event name, run time, expected end time
Event Ended	Orange	Event name and how it ended (self-managed or stopped)
Cycle Complete	Purple	All events ran — new randomized cycle starting

How It Works​

PLUGIN LOADS
  └── Counts and logs all enabled events (console + Discord)
  └── Randomizes the event queue and logs the order
  └── Calculates first buffer time (random between min/max minutes)
  └── Waits buffer time, then fires first event

BUFFER FIRES
  ├── Active events < Max Active Events?
  │     YES → Fire next event → run start command
  │           → Schedule stop command after run time (if defined)
  │           → Schedule next buffer → repeat
  │     NO  → Wait: Event Run Time + new buffer calculation → retry

ALL EVENTS IN QUEUE HAVE RUN
  └── Log "Cycle Complete" to console + Discord
  └── Re-randomize the full event list
  └── Log new randomized order to console + Discord
  └── Resume scheduling from the top

Adding Custom Events​

Support & Community​

• Discord Support - Join our community for help and discussions

Development & Testing Server​

• Server: Darktidia Solo Only | Monthly | 2x | 50% Upkeep | No BP Wipes
• Find Server: View on BattleMetrics