Set the few server-wide details that shape every Atom interaction.

Customizations is intentionally narrower than its name may imply. Language has its own locale workflow, Prefix has command-specific validation, Rank Card has a full visual editor, and Experience owns activity policy. This page collects the values whose effect is broad and whose change frequency should be low.

That separation prevents one large miscellaneous form from becoming the hidden source of every server behavior. When diagnosing an issue, administrators can map the symptom to the appropriate editor instead of searching through an undifferentiated settings catalogue.

The bot nickname changes how the member appears inside the selected Discord server where the platform and permissions allow it. It does not create a new bot, transfer ownership, or change the authenticated Atom application. Keep the name distinct from human moderators and other automation.

If the server uses a branded nickname, update onboarding and support references at the same time. Members should be able to connect the visible profile with Atom’s commands, rank cards, and automated messages even when the local name is different.

Maximum Level defines the ceiling for the server’s progression. Evaluate it beside the formula and expected earning rate: a cap of 25,000 may be technically valid but socially meaningless if no member can approach it, while a low cap can strand committed members without a next goal.

Place final rewards and community messaging before the cap. Decide what happens after a member reaches it and whether the server will later extend the curve. The dashboard stores a number; the community experiences a conclusion to the progression journey.

The form validates current values and keeps the previous configuration when a dashboard action fails. Record broad changes, particularly a new maximum level, because their effect can appear later in leaderboards, rank cards, rewards, and announcements rather than immediately on the page.

After saving, verify the bot member presentation and a representative progression surface. If one output still shows old information, identify whether it is cached, permission-limited, or driven by a more specific editor before repeating the global save.