Your First 10 Minutes With Airwavy

Most setup problems that show up weeks later — a moderation action that silently fails, a role that never gets granted — trace back to something skipped in the first few minutes: a role placed wrong, a permission never granted, a feature enabled but never actually tested. Getting the sequence right up front means every feature you add after inherits a working foundation instead of compounding an unnoticed problem.

Discord gives you a fresh bot member with its role at the bottom of the list, and no assumptions about what you'll configure first. Everything from here is a sequence you control.

This order deliberately front-loads the checks that would otherwise cause confusing failures later.

1. Invite Airwavy using the official invite link, and confirm it appears in the member list.
2. Open Server Settings → Roles and position Airwavy above member, verified, reaction-role, and moderation-target roles — while keeping owner and administrator roles above it.
3. Sign into the dashboard with Discord and select your server.
4. Configure one reversible feature first — welcome messages or logging are good choices — save it, then reload the page to confirm the stored state actually persisted.
5. Run the guide's expected-result test from a non-administrator account before enabling anything community-wide.

1. Confirm Airwavy is online and present in the member list.
2. Confirm the dashboard loads your intended server and its feature cards.
3. Run a harmless command like /help and confirm it responds.
4. Confirm your one test feature saves, reloads, and behaves exactly as documented — not just that the save button didn't show an error.
5. Only after all four check out, move on to the next feature you actually want.

• Configuring several features before testing any of them — if something's wrong with role placement, you'll now have several broken features to debug instead of one.
• Treating a successful save as proof something works — confirm the actual Discord behaviour from a non-administrator account.
• Starting with a destructive or high-stakes feature (moderation actions, anti-nuke) before confirming the basics work.
• Skipping the dedicated permissions guide because 'it seems to be working so far.'