exceedexceedDocsSign in
Getting Started

Enabling Features

How exceed features are turned on per-server with feature flags — why most start off, and how to enable exactly what you need.

Most features start off

exceed ships almost everything disabled by default. Leveling, automod, starboard, tickets, music, giveaways, antinuke — none of them do anything until you switch them on for your server.

This is deliberate. Adding exceed to a server shouldn't change how it behaves on day one. You decide, feature by feature, what your community actually needs, and the rest stays dormant. No surprise XP messages, no automod deleting posts you didn't expect, no extra channels.

Feature flags

Behind the scenes, each feature has a per-server feature flag — a simple on/off switch stored for your server alone. Turning a feature on in one server has no effect on any other server running exceed.

A flag controls only whether the feature runs, not how it's configured. The flag and its settings live together on the same dashboard page, so the flow is always:

  1. Open the feature's page in the dashboard sidebar.
  2. Toggle the feature on.
  3. Configure its settings (channels, roles, messages, thresholds).
  4. Save.

The bot reads the flag continuously, so the moment you enable a feature it starts working — and the moment you disable it, it stops.

Tip: Turning a feature off does not erase its configuration. Your settings are kept, so you can re-enable later and pick up right where you left off.

Enabling a feature, step by step

Take leveling as a concrete example:

  1. Open Leveling under the Engagement group.
  2. Toggle leveling on.
  3. Choose an announcement channel for level-up messages and set your XP rate.
  4. Save. XP starts tracking immediately.

Every feature page in these docs names the exact dashboard page where you enable it, near the top, so you always know where to go.

Where flags fit alongside other controls

Feature flags answer "is this feature running at all?" Two other systems answer related questions:

  • Permissions decide who can run commands and trigger actions, even for features that are enabled.
  • Premium governs access to add-on capabilities on licensed servers.

A feature has to be enabled first, then permissions decide who gets to use it.

Next steps