What Onyx can build and configure
The distinction that matters: a template can give you a channel called tickets. Onyx can give you a working ticket system. Here is everything it reaches.
Structure and features
Channels and categories
Text and voice channels grouped into categories, named for the community you described rather than a generic preset.
Roles and permissions
Roles with the permission overrides that make them mean something, including channels only certain roles can see.
Welcome messages
The greeting new members get, the channel it lands in, and the variables inside it.
Goodbye messages
The same for members who leave, configured independently of welcomes.
Moderation and automod
Word filters, link rules, and the automod behaviour that runs without a human watching.
Anti-raid and safety
Mass-join detection and lockdown, plus the anti-nuke limits that cap what any single account can do.
XP and leveling
Message and voice XP, cooldowns, no-XP channels, and the roles awarded at each level.
Tickets
The support panel, the category tickets open into, and which roles can see them.
Logging
Which events get logged and where: edits, deletes, joins, leaves, moderation actions.
Join-to-create voice
A lobby channel that spawns a temporary room the joiner owns, and cleans it up afterwards.
Invite tracking
Who invited whom, leave tracking, and the invite rewards that go with it.
Reaction roles
Self-assign role menus, including the message members pick from.
Polls and onboarding
Poll setup, and the onboarding questions a new member answers on the way in.
Why configuring beats generating
Every AI server tool can produce a channel list. That is the easy half, and it is also the half that leaves you with the actual work still to do: a server full of empty channels with no welcome flow, no automod, no ticket panel and no permissions worth the name.
The settings are where the hours go. Onyx reaches them because PeakBot owns them — the same bot that builds the structure is the bot that runs it afterwards, so there is no hand-off to a second tool that has to be configured separately.
What it will not touch
Anything outside PeakBot. It does not configure other bots, and it cannot change Discord-level settings that belong to the platform rather than to a bot, such as a server’s age-restricted channel flags or its Discovery listing.
It also will not delete things you did not ask it to. Cleaning up an existing server is something you ask for explicitly, and it still goes through the plan step like everything else.
Related
How it works, step by step · Every PeakBot feature · PeakBot vs MEE6