Helios Rust Console Bot Documentation

Auto Events

Owner setup guide for creating, scheduling, and managing premium /auto events presets.

Page Summary

  • This page covers premium Auto Events setup for scheduled Rust Console events.
  • It is for owners and admins running recurring event rotations.
  • Use it to configure presets, schedule timing, and event-feed visibility.

Related Product Pages

Overview

/auto events opens a premium admin panel for scheduled event spawns. You can create preset events, set frequency, require a minimum player count, configure announcements, and manage events with Run, Pause, Edit, Remove, and Feed controls.

Who This Is For

  • Owners running scheduled world events
  • Admins maintaining event rotation per server
  • Staff handling wipe-day event setup and testing

Requirements

  • Connected server in Helios
  • Manage Server permission in Discord
  • Premium enabled for the target server
  • For Set Location: your Discord account linked with /link
  • For location capture: stand in-game on target server and remain still while capturing

Setup

  1. Run /auto events server:"<SERVER>".
  2. In the Auto Events panel, click Create.
  3. Click Preset and choose the event preset.
  4. Click Name and set a unique event name.
  5. Click Frequency and enter either:
  6. Relative interval (examples: 15m, 12h, 1d 12h) or
  7. 5-field cron expression (UTC timezone).
  8. Click Minimum Pop and set a non-negative whole number.
  9. Click Announcement and configure:
  10. Announcement message text, and
  11. on or off for announcement enabled state.
  12. Click Set Location until all required location slots are filled.
  13. If needed, click Remove Location to clear a saved slot and recapture it.
  14. If your preset needs extra options, configure them before save:
  15. Node Writing preset: set message, orientation, node type, and rotation.
  16. Node Pyramid / Node House presets: set size and node type.
  17. Docked Cargo preset: set locked crate count and docked duration.
  18. Click Save.
  19. Confirm the success reply (Auto event saved. or Auto event updated.).

After You Create an Event

  1. From main panel, click List to review all events and next-run status.
  2. Click Edit to reopen an existing event in the setup panel.
  3. Click Run Event to execute one event immediately.
  4. Click Pause to stop scheduled runs for an event.
  5. Click Remove to permanently delete an event.
  6. Click Feed and select a channel to receive execution updates.

Commands or Controls

/auto events server:"<SERVER>"
/link

Example Use Case

Owner creates a Night Cargo event on a premium server using the Docked Cargo preset, runs it every 12h, requires minimum pop of 20, sets feed to #event-feed, and pauses it during low-pop weekdays.

Common Issues

Problem

/auto events opens but you cannot proceed.

Likely Cause

Server is not premium for Auto Events.

Fix

Enable premium for that server, then re-run /auto events.

Prevention

Confirm premium status before configuring wipe schedules.

Problem

Save fails with missing required setup.

Likely Cause

Name, preset, frequency, preset-specific options, or required locations are incomplete.

Fix

Complete all required fields and set every missing location slot shown in panel preview.

Prevention

Follow the panel in this order: Preset -> Name -> Frequency -> Location(s) -> Preset options -> Save.

Problem

Set Location fails.

Likely Cause

Account is not linked, wrong server, or player position could not be read.

Fix

Run /link, join the correct server, stand still, then click Set Location again.

Prevention

Link all admin/operator accounts before event setup sessions.

Problem

Frequency input is rejected.

Likely Cause

Invalid format or interval lower than 1 minute.

Fix

Use valid input such as 15m, 12h, 1d 12h, or a valid 5-field cron expression.

Prevention

Use a saved schedule cheat sheet for staff.

Tips / Best Practices

  • Keep event names unique and environment-specific (Night Cargo, Weekend Crate Rush).
  • Use Run Event once after setup to validate spawn behavior and feed routing.
  • Keep Minimum Pop above zero for high-impact events.
  • Keep announcement messaging short and consistent with your server branding.
  • Pause seasonal or temporary events instead of deleting them when possible.