Paradigm 2.5.0b

This beta adds a complete support-ticket workflow, configurable server-side inventory menus, and much more precise Local Dashboard access control.

New

• Added the Tickets module:

  • Players can create, list, view, reply to, close, and reopen their own tickets with /ticket. Tickets use short, human-friendly references such as T-1, while their internal records remain uniquely identified.
  • Staff can use /tickets to work through the queue and can claim, unclaim, assign, reply to, prioritize, recategorize, resolve, close, or reopen tickets.
  • Tickets keep the full conversation and workflow history, including assignment, status, priority, and category changes.
  • Configurable categories support their own default priority, player permission, and staff-handling permission.
  • Added ticket notifications for creators and eligible staff, plus optional automatic closing for resolved and waiting-for-player tickets.
  • Tickets are available in the Local Dashboard with filters, queue summaries, full conversation/history views, and revision-aware updates to prevent one staff member silently overwriting another's change.
  • Ticket data works with Paradigm's JSON, SQLite, MySQL, and MariaDB storage. Shared SQL storage can optionally relay ticket notifications between servers in the same network without exposing message text through the event feed.

• Added configurable server-side inventory menus:

  • Define chest-style menus as JSON files in config/paradigm/menus/, with placeholders, permissions, visibility/open conditions, click actions, filler items, and optional timed refreshes.
  • Menu items support names, lore, glint, custom model data, and tooltip hiding across supported Minecraft versions.
  • Added /paradigm menu administration commands to list, inspect, reload, open, close, and review active menu sessions.
  • Added a Local Dashboard menu editor with validation, reload feedback, and active-session visibility.
  • Custom Commands and menu definitions now share the same extensible action/condition system. Menus add open_menu, close_menu, and menu_back; shared actions also cover chat messages, action bars, titles, sounds, teleports, player commands, and console commands.
  • Menu support is implemented for every supported Fabric, Forge, and NeoForge target. No client-side mod is required.

• Added granular Local Dashboard permissions:

  • paradigm.dashboard.access controls dashboard sign-in, while paradigm.dashboard.manage remains the full superadmin override.
  • Added page-specific permissions for overview, servers, storage, audit, permissions, moderation, and tickets.
  • Added separate view/edit permissions for each dashboard configuration section and storage configuration; menu visibility and menu administration are also independently permission-gated.
  • The dashboard now receives the authenticated user's capabilities and hides pages they cannot use; the API enforces the same restrictions server-side. Existing broad dashboard/config permissions remain valid for backwards compatibility.

• Added a Companion API guide for server-side integrations, covering capability checks, optional dependencies, cached permission checks, safe message delivery, and external placeholders.

• Added option to disable version update checks

Changes

• Ticket configuration is stored in config/paradigm/tickets.json and can be reloaded with /paradigm reload tickets.
• Reloading all Paradigm configuration now also refreshes ticket settings and ticket maintenance tasks.
• Staff-chat delivery now uses the shared permission-aware messenger path.
• Added ticket lifecycle hooks to Paradigm's internal event system for integrations that need to react to ticket creation, replies, assignments, resolution, closure, or reopening.

Fixes

• Fixed shared-SQL ticket polling potentially losing events when more than one polling batch was created in the same millisecond. The feed now continues using the event ID as a deterministic tie-breaker.
• Hardened ticket notifications and storage handling around unavailable platform/storage state so an auxiliary notification failure does not break a completed ticket mutation.

Compatibility

• Menus and Tickets are server-side features; players do not need to install Paradigm or another client mod.
• Existing Custom Command actions and conditions continue to work; the shared dispatcher adds menu actions without requiring command definitions to be rewritten.
• Tickets fall back to local-only notifications on JSON storage. Cross-server notifications require shared SQL storage and can be disabled in tickets.json.
• Dashboard users who already have paradigm.dashboard.manage, paradigm.config.view, or paradigm.config.edit retain their existing access while granular permissions can be introduced gradually.