SysMODBeta

Release Timeline

A changelog that reads like the product actually shipped.

This timeline is curated from real repo work: commit history, shipped module changes, and the execution transcripts already living with the project. It is meant to answer one question fast: what changed, and why should anyone care?

Current featured release

1.0.6 - Rust+ Reliability & Market Alerts

Rust+ gained market subscriptions with automatic match alerts, BattleMetrics visibility, safer server cleanup, and a round of team chat, death notification, and note/timer reliability fixes.

Feature waves

5

Tracked changes

32

Primary surfaces

Rust+ Bot, Web, Worker, Prisma

1.0.6

Release 1

Rust+ Reliability & Market Alerts

This release tightens the Rust+ experience for active teams: watch vending markets without babysitting the map, inspect BattleMetrics context from the dashboard, clean up old servers safely, and rely on team chat plus death alerts to behave under real server pressure.

Released 2026-04-29

32 highlighted commits

Rust+ gained market subscriptions with automatic match alerts, BattleMetrics visibility, safer server cleanup, and a round of team chat, death notification, and note/timer reliability fixes.

Market subscriptions now watch for you

Rust+ market monitoring moved from manual searches into saved subscriptions and automatic notifications.

  • - Added market subscription commands and a dashboard management page for watching buy, sell, or all orders for specific items.
  • - Added automatic market match notifications that reuse Rust+ notification delivery settings for Discord, in-game, or combined delivery.
  • - Added cooldowns and bounded notification fan-out so busy vending activity does not flood channels or overwhelm Discord sends.

BattleMetrics visibility reached the dashboard

Guild admins can now connect Rust+ server context with BattleMetrics data from a dedicated dashboard surface.

  • - Added a BattleMetrics page for Rust+ servers with online player viewing, search, and monitored-player controls.
  • - Added strict BattleMetrics ID extraction from direct IDs or server URLs so paired servers keep their BattleMetrics link reliably.
  • - Cached BattleMetrics player snapshots to reduce repeat fetch cost while keeping the server view responsive.

Team chat delivery became more dependable

Several Rust+ team chat paths were hardened around retries, duplicate suppression, and failure isolation.

  • - Restored broadcast-based team chat receive behavior and primed subscriptions so inbound team messages appear more consistently.
  • - Improved outgoing team message delivery with safer retries, sendability checks, queue isolation, and duplicate guards.
  • - Suppressed bot echo loops and duplicate relay behavior between Discord and in-game team chat.

Notifications got sharper and less noisy

Rust+ notification handling now better reflects what actually happened in game while avoiding unnecessary repeat alerts.

  • - Added team change event handling and notifications for roster updates.
  • - Added alarm notification cooldowns and improved entity-state handling around Rust+ events.
  • - Fixed offline death direct messages and wording so FCM death alerts correctly describe who killed the linked player.

Server management and saved data are safer

Dashboard and command paths now protect Rust+ records more carefully when users edit or remove server state.

  • - Added a confirmed Rust+ server delete action that disconnects the server and cleans up related saved data safely.
  • - Fixed note and timer creation by validating the paired server and using the correct stored server record for database writes.
  • - Handled Rust+ subscription edge cases more gracefully so transient Rust+ API responses do not break the control flow.
1.0.5

Release 2

Growth Automation & Live Operations

This release is built for teams that want faster server launches and less manual overhead: guided setup, smarter update delivery, cleaner permissions, and a dashboard that feels alive while you operate.

Released 2026-04-26

37 highlighted commits

Setup Discord is now a real guided launch flow across key modules, Rust News expanded into YouTube updates with scalable delivery, and the dashboard gained stronger RBAC, visibility, and real-time operational confidence.

Setup Discord became a true activation wizard

Module setup moved from placeholders and scattered pages into real guided flows that reduce launch friction for new guilds.

  • - Implemented full Setup Discord wizard coverage with module-specific steps for welcome, reaction roles, custom embed, forms, rust news, tickets, giveaways, verification, kit4kit, suggestions, and analytics.
  • - Converted suggestion board creation to a guided wizard and placed entry points behind explicit create actions to keep admin flows clean.
  • - Expanded Rust+ onboarding with team info and chat channel configuration so setup reflects real server operations, not just credential wiring.

Rust News expanded into YouTube updates

Rust News now supports YouTube-driven updates and a more scalable fan-out model, giving communities richer and faster content delivery.

  • - Added YouTube integration for Rust News, including guild-level YouTube update support and dashboard-facing configuration paths.
  • - Refactored update delivery to a WebSub fan-out model with global sources for better scalability and timeliness.
  • - Fixed YouTube superadmin endpoint paths and cleaned encryption import boundaries to keep bot/runtime behavior stable.

Permissions and governance got enterprise-grade upgrades

Dashboard access control and privileged operations were hardened so large teams can delegate safely without losing control.

  • - Implemented guild RBAC for the web dashboard so permissions can be enforced per capability instead of broad admin access.
  • - Added platform admin access caching with TTL and invalidation to reduce load while preserving permission correctness.
  • - Improved guild membership fidelity by tracking joined state and refreshing Discord OAuth tokens for accurate guild visibility.

Live operations visibility improved across the board

Operators now get better API observability, faster state refresh, and clearer diagnostics when managing production communities.

  • - Added Discord API observability and upgraded payload handling/viewing with filtering, sorting, and inspection workflows.
  • - Shipped realtime-ish dashboard updates with Redis-backed menu and guild caching for faster perceived responsiveness.
  • - Expanded web help tutorials with a superadmin editor plus file-based tutorial import, validation, and change detection to scale operator onboarding.

Module quality and UX polish

Several core modules received reliability and usability improvements that reduce setup errors and day-to-day support burden.

  • - Shipped the suggestions module with richer admin UI, author edit flow, result channel options, and category controls.
  • - Strengthened verification with wizard setup, channel permission syncing, and race-condition/session-ID fixes in DM challenge paths.
  • - Enhanced welcome messages with channel and role mention support for clearer first-contact communication.
1.0.4

Release 3

Rust+ Onboarding & Backup Recovery

This release turns two of the hardest setup flows on the platform — Rust+ credentials and Kit4Kit trades — into guided experiences anyone can complete, and adds the safety net of scheduled backups you can restore in one click.

Released 2026-04-12

12 highlighted commits

Rust+ integration now guides you from zero to connected with a step-by-step wizard, Kit4Kit handles multi-kit trades and stricter role gates, and database backups are fully schedulable with one-click restore.

Rust+ onboarding wizard

The old integrations page is gone — replaced by a guided, step-by-step flow that walks you through credential setup and validates every step.

  • - Replaced the Rust+ integrations page with a step-by-step onboarding wizard that validates credentials at each stage and shows clear status indicators.
  • - Added a color-coded Rust+ header button with a popover that shows credential status at a glance — green for connected, yellow for pending, red for missing.
  • - Fixed credential generation to work behind the /rp path prefix and ensured incomplete credentials no longer block the wizard.

Kit4Kit multi-kit and role enforcement

Kit4Kit now supports requesting and donating multiple kits in a single trade, and enforces role requirements before anyone can apply.

  • - Requesters and donors can now select multiple kits in a single request or application instead of creating one per item.
  • - Strict role validation now blocks ineligible requesters and donors before they enter the flow, reducing noise and failed trades.
  • - Added completed and no-servers request statuses so both sides always know where a trade stands.

Backup and restore

Database backups can now be scheduled and restored from the dashboard, giving you a real safety net before risky changes.

  • - Added backup artifact management with detailed restore flows so you can schedule automatic backups and roll back in one click.
  • - Backup schedules run on configurable intervals and store artifacts with full metadata for auditability.
1.0.3

Release 4

Kit4Kit Module Wave

From first request to final outcome, Kit4Kit now runs as a full in-server workflow instead of a planned feature stub.

Released 2026-04-12

10 highlighted commits

Kit4Kit is now a complete request-and-trade system with guided Discord flows, admin oversight, and the polish needed to run it live.

Kit4Kit goes live

The module now covers the full request lifecycle instead of stopping at setup.

  • - Shipped the Kit4Kit foundation across Prisma, dashboard setup, Discord provisioning, and panel sync.
  • - Turned the placeholder request button into a guided flow for requests, donor applications, private trade threads, transcript capture, and outcome tracking.
  • - Added runtime priming so active requests and reminders recover cleanly after restarts.

Admin control and visibility

Guild staff can now review and moderate Kit4Kit activity from the dashboard.

  • - Added a history view for requests, applications, trade threads, outcomes, transcripts, and moderation metadata.
  • - Added request cancellation and trade-thread moderation actions backed by validated bot handlers.
  • - Clarified lifecycle state with open, expired, and cancelled request states plus a requester-facing Complete action.

Matching and runtime polish

A focused polish pass reduced friction and conflicting applications in the live flow.

  • - Simplified server selection, filtered invalid donor targets, and enforced donor eligibility before apply.
  • - Added cross-provider kit support, automatic role creation, duplicate donor guards, and fixed participant thread permissions.
  • - Auto-dismissed temporary interaction UI and standardized UTC date formatting to avoid stale Discord state and hydration mismatches.
1.0.2

Release 5

Verification And Identity Hardening

This release is about trust and control: better onboarding challenges, better identity signals, safer admin operations, and less operational drag in production.

Released 2026-04-11

10 highlighted commits

Verification grew into a full workflow, user registration and platform roles gained stronger security controls, and a focused ops pass tightened moderation and deployment behavior.

Verification workflow

Verification moved from a simple gate into a configurable intake and challenge pipeline.

  • - Added the verification workflow with analytics, reminder handling, and resolver plumbing so guilds can track and manage onboarding progress.
  • - Introduced rand challenge fields with configurable settings and added a valid-rule path so form-generated checks can enforce stronger responses.
  • - Expanded application form schema and publishing support while continuing the move away from older DM-session flows toward embedded intake and cleaner modal handling.

Identity and admin controls

User management now carries more useful security context and clearer privileged boundaries.

  • - Implemented user registration with IP tracking and security alerts to make suspicious activity easier to surface and investigate.
  • - Improved user management and notifications with stricter validation, better optional-field handling, and Discord guild synchronization that keeps platform state aligned with server membership.
  • - Added a platform admin role and permissions system so elevated operations can be scoped through first-class access controls instead of ad hoc checks.

Moderation and operational polish

A smaller but important pass removed rough edges across giveaways, runtime metadata, and production deploy behavior.

  • - Added giveaway cancel and delete lifecycle handling with confirmation dialogs so destructive actions are explicit and message cleanup is more reliable.
  • - Made bot startup presence configurable from environment variables and normalized welcome embed colors to safely support both string and numeric formats.
  • - Removed illegal Prisma defaults from ticket role-list columns, tightened ingress websocket handling and deployment scripts, and reduced Kubernetes resource requests to improve production autoscaling behavior.
1.0.1

Release 6

ChangeLog Control Surface

This update closes the loop between release authoring, dashboard visibility, and Discord delivery so updates can be shipped and pushed from one place.

Released 2026-04-10

2 highlighted commits

The release system now has an operator-grade control loop: guild admins can configure ChangeLog delivery from the dashboard and force-post the newest release instantly without falling back to slash commands.

Manual release delivery

Guild admins no longer need to leave the dashboard to push a release into Discord.

  • - Added a dashboard button that force-posts the newest ChangeLog release immediately to the configured guild channel.
  • - Wired a dedicated bot socket event for ChangeLog publishing so manual posts use the same validated publish pipeline as automated delivery.

Release continuity

The shared release catalog now advances with the shipped update instead of waiting for the next manual pass.

  • - Published the next curated release entry in the shared catalog so the dashboard and bot both point at the same newest version.
  • - Bumped shared runtime version constants to 1.0.1 to keep bot-visible release state aligned with the newest shipped update.
1.0.0

Release 7

Platform Expansion

A bigger release focused on user-facing workflows, deployment reliability, and enough platform polish that updates now deserve their own broadcast channel.

Released 2026-04-10

7 highlighted commits

The dashboard moved from a server control panel into a release-ready platform: public tickets, bug tracking, template deployment, personal AI settings, and cleaner production ingress all landed in the same wave.

Community workflows

More of the product is now visible and usable without side channels or manual admin work.

  • - Added a public ticket intake flow with detail pages so support requests can start outside Discord staff-only views.
  • - Shipped a dashboard-integrated bug tracker with moderation, public issue history, and a cleaner reporting pipeline.
  • - Introduced delete-server cleanup and safer guild removal flows so dashboard actions now match database reality.

AI and operator tooling

Configuration moved closer to the real user and the real deployment path.

  • - Added personal AI mode, provider selection, and layered guild or user fallback resolution.
  • - Improved quota checks, warning caching, and client action wiring to reduce broken settings flows.
  • - Auto-save for AI interview answers now keeps longer setup flows from losing progress.

Templates and deployment

Template-driven server setup became a first-class workflow instead of loose scripts.

  • - Built the initial Discord server template system and added deployment preparation flow support.
  • - Consolidated production ingress to a unified path-based model and aligned socket environment handling.
  • - Refined deployment scripts and runtime validation around unified ingress and template execution.
2026.04.08

Release 8

Ops And Alerts

Less guesswork during incidents, better long-running visibility, and more useful Rust+ state changes reaching the right people.

Released 2026-04-08

5 highlighted commits

This release tightened the operational side of the platform with durable file logging, upkeep alerting, and a round of Rust+ notification quality fixes.

Logging and diagnostics

  • - Added 24-hour rotated file logging with retention to make server-side debugging survivable across restarts.
  • - Mirrored stdout and stderr into rotated logs so failures outside structured logging still leave a trace.

Rust+ notifications

  • - Introduced upkeep alerts for Tool Cupboards with configurable thresholds.
  • - Improved offline duration handling and player identification fallback in team event notifications.
  • - Removed incompatible emoji from in-game messages to keep Rust+ relay output stable.

Runtime confidence

  • - Population trend tracking and related debug output made time-tracker behavior easier to verify under load.
2026.04.02

Release 9

Support And Deployments

This was the release where the product stopped being only features and started becoming a system you could actually run.

Released 2026-04-02

5 highlighted commits

A support-system wave landed alongside infrastructure work: the ticket system started taking shape, Rust News became easier to configure, and the deployment story got much more serious.

Ticket system foundation

  • - Implemented the first ticket system foundation with queue management and helpdesk structure provisioning.
  • - Expanded ticket web-admin behavior and cleaned up support-side flows for staff usability.

Module ergonomics

  • - Rust News now auto-enables when its channel is configured from the web dashboard, closing a real config mismatch.
  • - Responsive layout work made module and settings pages easier to use on smaller screens.

Deployment baseline

  • - Added the first complete Kubernetes deployment set for the platform.
  • - Updated Docker Compose and build steps so monorepo package builds and database migration steps run more reliably.
2026.03.31

Release 10

Community Systems

The platform started to feel less like a moderation bot and more like a suite for running a real server community.

Released 2026-03-31

4 highlighted commits

Analytics, giveaways, and clan-management groundwork established the first big wave of community-facing modules beyond core moderation.

Analytics

  • - Added the analytics module with dashboard charts and seeded platform support for phase-one rollout.

Giveaways

  • - Launched the giveaway system with weighted entries, dedicated channel management, and draw or resync flows.

Guild structure

  • - Started the clan-management module and broadened the product beyond moderation-only workflows.