LCARS SUPPORT OPERATIONS
File a numbered support ticket below.
LCARS-Prime Support OperationsLCARS will show servers where you have Manage Server / Administrator access or a dashboard role delegated by that server. Servers where LCARS is not yet installed still require Discord administration permission to install the bot.
Authorize with DiscordYou have Discord administration access here, but LCARS cannot manage the server until the bot is installed.
Select any control surface to open its tab. Existing module controls can be enabled or disabled here. Planned systems open a dedicated Coming Soon page.
Automatically send messages and give roles to your new members and send a message when a member leaves your server.
You must select a channel to post in before saving.
The welcome card is posted in the Welcome Message Channel selected above. The built-in background uses LCARS styling; a custom image removes LCARS visual branding so the server artwork stands on its own.
Drag the avatar or text directly on the preview, or use the X/Y controls for precise placement.
LCARS creates new roles without permissions. Configure permissions and hierarchy directly in Discord after creation.
You must select a channel to post the goodbye message before saving.
Private messages can use text or rich embeds. Role buttons are unavailable in direct messages, but external links and channel buttons are supported.
Create a central channel to welcome new members and share essential server information.
Select any text channel on this server. Existing channel permissions are not changed.
Drag each banner or embed into the order it should be published. The delete control stays on the right side of every element.
LCARS supports up to 20 sequential elements. Every banner is generated as an image when Publish is selected. Recommended banner ratio: 545 x 127 px. Uploads may be PNG, JPG, GIF, or WebP up to 768 KB.
LCARS creates the role with no permissions. Configure any special permissions directly in Discord.
Per-server identity: LCARS applies this display name and icon to its own Discord member profile in this server. The same icon can be used by the built-in LCARS welcome visuals. Custom welcome-card and welcome-banner images are intentionally left free of LCARS visual branding; clearing the server icon restores the bot's global avatar in Discord.
Choose the Discord channels used by reusable LCARS placeholders. These assignments are shared by Welcome & Goodbye and any other feature that supports the same server variables.
Server owners, Administrators, and Manage Server members have full Server Setup access automatically. Existing /welcome manage channel assignments remain synchronized with these fields.
Keep slash commands in the right places by allowing selected channels or entire categories. Threads inherit permission from their parent channel or category. Server owners and members with Administrator or Manage Server retain emergency command access.
When disabled, LCARS remains available for moderation, tickets, welcome tools, roles, and server management. STFC lookup, roster, crew, account, combat-log, and recommendation commands are blocked.
The server owner, Administrator, and Manage Server members keep full access automatically. Add normal Discord roles here when you want trusted personnel to use only selected LCARS dashboard tabs.
This dashboard uses the same Computer configuration, channel, role, and permission services as /computer-setup. No parallel Computer settings are created here.
Visible only to the configured LCARS owner. Every Discord server currently connected to LCARS appears here. Enabling a server makes Computer Setup available to that server's authorized administrators; they never receive this bot-wide directory.
Choose the actual Discord channel names here. These selections are used when Launch Scope is set to Configured Channels.
These are the exact Computer Manager and Computer User role stores already used by /computer-setup. Dashboard access roles above are separate: one controls the web console, the other controls LCARS-Computer itself.
/computer-setup, only the Discord server owner or configured LCARS owner may change Computer Manager/User roles and Computer access mode.Words, spam, links, attachments, strike windows, and audit logging use one consistent rule language.
Enter several new rules at once with commas, for example: free nitro, crypto giveaway, scam link.
Members with a checked role are exempt from the server's AutoMod word filters and shared spam/rate rules. This uses the existing global automod_exemptions role records rather than creating a second exemption system.
Temporary mutes can last up to 28 days.
One shared message keeps warnings consistent. Individual rules only need an override when the wording truly differs.
Stack multiple policies so repeat offenders escalate automatically — for example timeout at 3 strikes, kick at 4, temporary ban at 5, and ban at 6. Each threshold can use its own rolling time window.
Timeouts can last up to 28 days.
Catches burst spam and repeated messages. Global AutoMod immune roles bypass both rate and duplicate checks.
LCARS can inspect posted URLs and attachment links. Server/channel/role exemptions will be added when this control is wired to the moderation runtime.
This filters message text, filenames, attachment URLs, and embed descriptions. Reading words drawn inside image pixels would require a separate image-analysis feature.
Each switch is independent and takes effect after Save Changes. Message edits include before/after text when Discord's cache contains the original. Delete events can identify the message and cached author, but Discord does not provide the identity of the person who clicked Delete in the raw delete event.
Live management view — not the audit log. Review active strikes, temporary mutes/timeouts, and temporary bans, then release them when appropriate.
A complete XP-only progression system. It does not read or modify the STFC playercard. Members use /show-rank for their current server level and can personalize that card with /rank-card.
Optional. Achievement XP advances member levels and /show-rank even when no Discord role rewards are configured.
This default is used by /show-rank. Members can override the accent, background, and overlay with /rank-card.
Open any command to configure role/channel exceptions, cooldown scope, private responses, command cleanup, and response behavior.
Reward participation across messages, forums, voice, Go Live, LCARS commands, STFC searches, and Computer inquiries. Milestones run from 10 through 100,000 and announce with a bronze, silver, or gold LCARS badge banner.
Turn individual categories on or off without deleting member progress or past awards.
Thresholds must remain between 10 and 100,000. XP and badge tier are editable per server. The same ladder applies independently to every enabled category.
Numbered support records with public/private routing, staff assignment, escalation, submitter or staff closure, archival, searchable history, and a permanent audit trail.
Create the permanent LCARS message members use to file a private ticket or recover links to their existing tickets. Updating it edits the existing Discord post whenever possible.
File a numbered support ticket below.
LCARS-Prime Support OperationsDiscord has no private forum posts. A private ticket requested in Forum mode safely falls back to a private ticket channel in the selected category.
OPEN ASSIGNED ESCALATED RESOLVED CLOSED ARCHIVED
Future subscription controls for this Discord server. This surface uses the existing Discord dashboard login, but it cannot charge, renew, cancel, or change access yet.
Core achievements, levels, rank cards, tickets, reaction roles, and essential server controls remain useful without a subscription.
Possible paid value centers on automation, analytics, exports, theme packs, larger limits, and multi-server convenience.
LCARS will not grant or remove paid access until one authoritative entitlement policy is selected, provider events are verified on the server, and test-mode lifecycle checks pass.
Owner-controlled deterministic exact rewrites. Access is limited to the LCARS owner and roles the owner explicitly delegates on the owner server. No external AI and no hidden inference layer.
The trigger is canonicalized by the existing local Computer parser. Editing an existing rule changes only its approved exact rewrite.
Manual, low-overhead acquisition from the configured STFC data source. This control is visible and callable only by the configured LCARS owner. It never applies changes to production master/player tables.
The numbered workflow above is the normal path. Use these controls only for recovery, detail-only audits, cleanup, or a supervised one-button cycle.
Not initializedZIP files are disposable transport packages. The immutable profile/raw archive remains canonical, so a deleted verified ZIP can be rebuilt without downloading STFC.Space again.
No sync runs recorded yet.