VERTEX Documentation

Overview

VERTEX is designed to be powerful without being complicated. Most systems are configured with slash commands, stored per server, and displayed through clean dashboards so staff members can understand what is enabled and what needs attention.

Simple idea: invite VERTEX, give it the required permissions, run the setup commands, and then enable the systems your community needs.

For owners

Control security, backups, status dashboards, setup quality, and server protection.

For staff

Manage moderation, tickets, user history, giveaways, logs, and daily operations.

For members

Enjoy a safer server with verification, roles, giveaways, music, and clear support flows.

Quick Start

Use this setup path for a clean, reliable server configuration.

Invite VERTEXUse the official invite link and select the server where you have permission to manage bots.

Place the role correctlyMove the VERTEX role above the roles it needs to manage. This is required for moderation, verification, reaction roles, and ticket permissions.

Run the setup dashboardUse /setup to review the most important systems and see what still needs configuration.

Configure protection firstSet up AutoMod, raid protection, verification, and audit logs before enabling community extras.

Add support and engagementCreate ticket panels, welcome messages, reaction roles, giveaways, music, and insights dashboards.

Permissions

VERTEX can work with granular permissions. Administrator is convenient, but not always required if the following permissions are available.

Permission	Used for
Manage Server	Configuration dashboards, insights access, setup checks, server-level tools.
Manage Roles	Verification roles, reaction roles, role logs, automated role assignment.
Manage Channels	Tickets, lockdown flows, channel logs, lock/unlock, permission updates.
Manage Messages	Clear command, AutoMod cleanup, moderation actions.
Moderate Members	Timeouts and safety enforcement.
Kick Members / Ban Members	Manual moderation and automated escalations when enabled.
View Audit Log	Executor detection for logs and security events.
Send Messages / Embed Links / Attach Files	Dashboards, logs, ticket transcripts, notifications, and rich responses.
Connect / Speak	Music playback in voice channels.

Important: Discord role hierarchy matters. VERTEX cannot manage members or roles that are above its own role.

Recommended Setup Order

Follow this order to avoid missing permissions or incomplete systems.

Create staff, logs, tickets, verification, welcome, and community channels.
Move the VERTEX role above managed member roles.
Run /setup and review the readiness dashboard.
Configure audit logs and moderation logs.
Enable AutoMod and raid protection.
Configure verification if your server needs gated access.
Create ticket panels for support.
Configure welcome, reaction roles, giveaways, music, and insights.
Run /status, /health, and /ping to verify operations.

Command Guide

Command names may include subcommands depending on your current deployment. Use Discord slash command suggestions to see the exact available options in your server.

Platform

/help, /about, /invite, /support, /guide, /setup

Operations

/ping, /status, /health, /backup, /insights

Moderation

VERTEX includes a complete moderation system with persistent warnings, case IDs, history, and professional logs.

/warnAdd a warning to a member and create a moderation record.

/unwarnRemove or deactivate a warning when appropriate.

/warnsView a member's active warnings.

/historyReview a member's moderation history.

/caseLook up a moderation case by ID.

/timeoutTemporarily restrict a member from interacting.

/kickRemove a member from the server.

/banBan a member from the server.

/clearBulk delete messages from a channel.

/lock /unlockControl whether members can send messages in a channel.

/slowmodeApply a message cooldown to reduce spam.

Best practice: always include clear reasons. Good reasons make staff reviews, appeals, and case history much easier.

AutoMod & Raid Protection

AutoMod protects your server automatically by detecting unwanted behavior and applying configured actions.

Message protection

Anti-spam, anti-links, anti-invites, anti-caps, banned words, automatic cleanup, and staff logs.

Raid protection

Join raid detection and automatic safety responses integrated into the existing AutoMod flow.

Escalation

Auto warn, timeout, kick, and ban based on configured thresholds.

Exceptions

Ignore trusted roles or channels where AutoMod should not intervene.

Recommended configuration

Start with warnings and timeouts before enabling kicks or bans.
Ignore staff channels and trusted bot channels.
Keep logging enabled so staff can review every action.
Use stricter raid settings on public or fast-growing servers.

Tickets

The ticket system gives members a private support space and gives staff a structured workflow.

Panels

Create professional ticket panels that members can use to open support requests.

Claims

Staff members can claim tickets so the team knows who is responsible.

Transcripts

Closed tickets can generate HTML and TXT transcripts for records.

Recovery

Ghost ticket repair helps keep SQLite state consistent after manual channel deletion.

Typical workflow

Member opens a ticket from the panel.
Staff member claims the ticket.
Staff helps the member and adds other users if needed.
Ticket is closed when resolved.
Transcript is generated and sent to the configured log channel.
Ticket can be reopened or deleted depending on the situation.

Verification

Verification helps protect your server by requiring members to complete a verification step before gaining full access.

Use captcha verification for public servers.
Assign a verified role after successful completion.
Keep logs enabled to track verification attempts.
Use session expiration to prevent abandoned verification attempts from staying active forever.

Role hierarchy: VERTEX must be above the verified role to assign it.

Welcome

Create polished welcome messages with variables, images, colors, and server branding.

Variable	Meaning
`{user}`	Mentions the joining member.
`{username}`	Displays the member's username.
`{server}`	Displays the server name.
`{membercount}`	Displays the current member count.

Example: Welcome {user} to {server}! You are member #{membercount}.

Reaction Roles

Reaction roles let members assign roles to themselves through professional panels.

Use reaction roles for interests, notifications, colors, games, platforms, or community categories.
Keep role names clear and short.
Make sure VERTEX can manage every assigned role.
Use cleanup and sync features to keep panels reliable over time.

Giveaways

VERTEX supports multiple giveaways at once, automatic endings, and rerolls.

Good giveaway setup

Use clear prize names.
Set realistic durations.
Use a dedicated giveaway channel.
Reroll only when a winner is invalid or unavailable.

Music

Music is powered by Lavalink and designed for stable multi-server playback.

/music playPlay a track or add it to the queue.

/music queueView the current queue.

/music pausePause playback.

/music resumeResume playback.

/music skipSkip to the next track.

/music stopStop playback and clear the queue.

/music disconnectDisconnect VERTEX from the voice channel.

/music volumeAdjust playback volume if enabled.

Tip: if music does not play, check that Lavalink is online and that VERTEX has permission to connect and speak.

Server Insights

Server Insights helps owners and staff understand server activity, growth, channel usage, and operational workload.

/insights overviewShows the main server activity summary.

/insights activityDisplays message and active user trends.

/insights growthShows joins, leaves, and net growth.

/insights channelsLists the most active channels and activity distribution.

/insights staffShows staff and operational activity when data is available.

Use it weekly: insights are most useful when reviewed regularly, not only when something goes wrong.

Audit Logs

Audit logs help staff understand what happened, when it happened, and who performed important actions when Discord exposes that information.

Message deletes and edits.
Member joins and leaves.
Voice activity.
Channel and role changes.
Guild updates.
Executor detection where available.

Backups

Backups help protect important configuration data and operational state.

Use manual backups before major configuration changes.
Keep scheduled backups enabled where appropriate.
Review retention so old backups do not grow forever.
Backup access is owner-protected.

Health & Status

Health and status commands help operators verify that VERTEX is running correctly.

/pingChecks bot response, Discord API latency, Lavalink detection, SQLite health, memory, and status signals.

/healthShows system health information and alerts.

/statusShows infrastructure, service, manager, and performance dashboards.

Latency note: short Discord API spikes around 200–300 ms can be normal.

Troubleshooting

Problem	What to check
A command does not appear	Make sure slash commands are deployed and the bot was invited with applications.commands.
VERTEX cannot assign roles	Move the VERTEX role above the target role and check Manage Roles permission.
Moderation fails	Check role hierarchy and required permissions like Moderate Members, Kick Members, or Ban Members.
Ticket channels are not created	Check Manage Channels, category permissions, and the configured ticket setup.
Transcripts do not send	Check Attach Files, Send Messages, Embed Links, and the ticket log channel.
Music does not connect	Check voice permissions, Lavalink status, and whether the user is in a voice channel.
AutoMod is too strict	Adjust thresholds and add ignore roles or ignore channels.
Insights look empty	Insights need activity data. Wait for new messages, joins, leaves, or staff actions to be collected.

Best Practices

Start secure

Configure logs, AutoMod, verification, and backups before opening your server widely.

Keep channels organized

Use dedicated channels for logs, tickets, welcome messages, giveaways, and staff discussions.

Use clear staff policies

Make sure staff know when to warn, timeout, kick, ban, claim tickets, and close tickets.

Review data

Use insights, history, and logs to improve the server instead of guessing.

Final recommendation: keep VERTEX simple for members and powerful for staff. Enable only what your server actually needs, then expand as your community grows.

Run your Discord server with confidence.

What you can do with VERTEX