BE ADVISED: NAVCOM AI is absolutely in beta testing. It may break but it is being rapidly actively developed. Documentation for each feature is only added once each new feature is absolutely feature complete and polished.
We don't test on animals. We test on production!
Overview
NAVCOM AI is a powerful, reliable tool crafted for Star Citizen Discord servers. We get it—you’re tech-savvy, you’ve got your server running smoothly, and the last thing you want is some new bot throwing a wrench in your setup. NAVCOM isn’t here to disrupt; it’s here to enhance what you’ve already built. It integrates seamlessly, bolsters security, and automates tedious tasks, all while keeping you in control.
Here’s how NAVCOM can work for you:
- Security You Can Trust: With global RSI.com handle verification, NAVCOM ensures only verified members access your channels, reducing impersonation risks across all servers it’s in.
- Effortless Organization Management: Sync your server roles with in-game orgs and ranks automatically—no more manual updates when someone gets promoted.
- Community Engagement Without the Hassle: Dynamic voice channels for squads, reaction roles for self-service, and custom welcome messages keep your server lively with minimal effort.
NAVCOM taps into the SENTRY database for real-time citizen and org data, giving you the intel you need without leaving Discord. It’s not about replacing your workflow—it’s about making it better, safer, and easier. Stick with what works, and let NAVCOM handle the rest.
Commands
Below are all the commands NAVCOM offers. Each one is designed to solve a real problem, with clear explanations and examples to show you how it fits into your server.
/verify [rsi_handle]
Lets users verify their RSI.com account by adding a unique code to their bio. Once confirmed, their identity is trusted across all NAVCOM servers.
Example: /verify MyHandle → Add the code to your RSI bio, and you’re verified in minutes.
Permissions: Anyone can use it.
Why It’s Useful: Keeps your server secure by ensuring members are who they say they are.
/citizen [handle]
Fetches detailed info on a Star Citizen player from the SENTRY database—bio, orgs, ranks, and more.
Example: /citizen MyHandle → See their org affiliations and citizen record.
Permissions: Open to all users.
Why It’s Useful: Perfect for vetting recruits or scoping out allies without leaving Discord.
/org [sid]
Pulls up an organization’s profile from SENTRY—name, member count, and description.
Example: /org ORG123 → Get the lowdown on ORG123’s size and purpose.
Permissions: Anyone can use it.
Why It’s Useful: Helps you research orgs for alliances or rivalries with minimal effort.
/set_org_role [org_sid] [role]
Assigns a Discord role to all verified members of a specific org.
Example: /set_org_role ORG123 @ORG_Member → All ORG123 members get the @ORG_Member role.
Permissions: Admins only (customizable).
Why It’s Useful: Automates role management so your server mirrors in-game orgs effortlessly.
/set_rank_role [org_sid] [rank_number] [role]
Maps a Discord role to a specific rank within an org (0-5, where 5 is highest).
Example: /set_rank_role ORG123 5 @Leader → Rank 5 members in ORG123 get @Leader.
Permissions: Admins only (customizable).
Why It’s Useful: Reflects in-game hierarchy in your server without constant manual tweaks.
/set_multi_org_behavior [behavior]
Controls how NAVCOM handles users in multiple orgs: focus on main org only, main org ranks with all memberships, or all orgs and ranks.
Example: /set_multi_org_behavior main_org_only → Roles based on main org only.
Permissions: Admins only (customizable).
Why It’s Useful: Gives you flexibility to match your server’s org policy without overcomplicating things.
/refresh_roles [member]
Updates a member’s roles based on their current RSI data.
Example: /refresh_roles @User → Syncs @User’s roles after a promotion.
Permissions: Admins only (customizable).
Why It’s Useful: Keeps roles accurate without waiting for hourly updates.
/manual_verify [user] [rsi_handle]
Manually verifies a user’s RSI handle, skipping the bio code process.
Example: /manual_verify @User MyHandle → Verifies @User as MyHandle instantly.
Permissions: Admins only (customizable).
Why It’s Useful: Quick fix for trusted members or verification hiccups.
/set_verification_role [role]
Sets a role automatically given to verified users.
Example: /set_verification_role @Verified → New verified users get @Verified.
Permissions: Admins only (customizable).
Why It’s Useful: Grants instant access to member-only areas securely.
/set_nickname_config [format] [source]
Customizes verified users’ nicknames (e.g., [ORG] Name) using RSI handle or display name.
Example: /set_nickname_config org_name rsi_handle → Nicknames become [ORG] Handle.
Permissions: Admins only (customizable).
Why It’s Useful: Keeps your server organized and visually consistent.
/set_reaction_role [message_id] [emoji] [role]
Assigns a role when users react to a message with a specific emoji.
Example: /set_reaction_role 1234567890 👍 @EventParticipant → 👍 gives @EventParticipant.
Permissions: Admins only (customizable).
Why It’s Useful: Lets members self-assign roles, reducing your workload.
/remove_reaction_role [message_id] [emoji] [role]
Deletes a reaction role setup.
Example: /remove_reaction_role 1234567890 👍 @EventParticipant → Stops 👍 role assignment.
Permissions: Admins only (customizable).
Why It’s Useful: Easy cleanup when a role setup is no longer needed.
/list_reaction_roles
Shows all active reaction role configurations.
Example: /list_reaction_roles → Lists all setups like 👍 → @EventParticipant.
Permissions: Admins only (customizable).
Why It’s Useful: Keeps you on top of self-service role assignments.
/add_dynamic_vc [starting_channel] [base_name] [target_category]
Creates numbered voice channels (e.g., Squad 01) when someone joins a starting channel.
Example: /add_dynamic_vc #JoinHere "Squad" #VoiceChannels → New squad channels spawn.
Permissions: Admins only (customizable).
Why It’s Useful: Perfect for events or squad ops without manual channel creation.
/remove_dynamic_vc [starting_channel]
Disables a dynamic voice channel setup.
Example: /remove_dynamic_vc #JoinHere → Stops new channel creation.
Permissions: Admins only (customizable).
Why It’s Useful: Tidies up when dynamic channels aren’t needed anymore.
/grant_command_access [command_name] [role]
Gives a role permission to use a specific command.
Example: /grant_command_access verify @Moderators → Moderators can use /verify.
Permissions: Admins only.
Why It’s Useful: Fine-tunes access so trusted roles can help manage the server.
/deny_command_access [command_name] [role]
Blocks a role from using a specific command.
Example: /deny_command_access manual_verify @Everyone → Only admins can manually verify.
Permissions: Admins only.
Why It’s Useful: Locks down sensitive commands for added security.
/list_command_permissions
Lists all custom command permissions on your server.
Example: /list_command_permissions → Shows who can use what.
Permissions: Admins only.
Why It’s Useful: Helps you audit and manage access controls easily.
/set_welcome_message [channel] [message]
Sets a custom welcome message for new members, with {user} to mention them.
Example: /set_welcome_message #welcome "Welcome {user} to the crew!" → Greets newbies.
Permissions: Admins only.
Why It’s Useful: Makes new members feel at home without you typing every time.
/disable_welcome_message
Turns off the welcome message feature.
Example: /disable_welcome_message → Stops welcome messages.
Permissions: Admins only.
Why It’s Useful: Quiets things down when you don’t need greetings.
/help [command_name]
Shows detailed help for any NAVCOM command.
Example: /help verify → Explains how /verify works.
Permissions: Anyone can use it.
Why It’s Useful: Quick reference for you or your members, no manual needed.
Installation
Adding NAVCOM to your server is simple and safe. Click below to invite NAVCOM with the exact permissions it needs:
Add NAVCOM to Your ServerOnce invited, NAVCOM starts working with your existing roles and channels. Set up verification or roles as needed—it’s all optional and builds on what you’ve got. No overhaul required.
Explanation of each permission required:
- View Channels - Used with the dynamic voice channels feature.
- Manage Channels - Used with the dynamic voice channels feature.
- Manage Roles - Used by the verification roles, org roles, rank roles, and react roles features.
- Manage Nicknames - Used by the Nickname manager feature.
- Send Messages - Used by the welcome message feature.
- Embed Links - Used by the News feature.
- Attach Files - Used by the News feature.
- Add Reactions - Used by the reaction roles feature.
- Move Members - Used by the dynamic voice channels feature.