Bot Guidelines

These are the rules every bot listed on Fluxer Bot List (FBL) has to follow. They exist to protect the users who install bots from your listing — not to make your life harder. Read them before you submit.

If anything here is ambiguous, default to "what would a reasonable Fluxer developer expect."

---

1. Identity

• The name, avatar, and description of your listing must match the real bot.
• You can't list a bot you don't own. Co-developers should be added as collaborators instead of listing the bot twice.
• Don't impersonate another bot, another developer, Fluxer itself, or Fluxer Bot List.

---

2. Availability

• The bot must be online and reachable when it's approved. We test-invite every submission.
• If your bot is going to be offline for a long period (weeks+), mark the listing as pending from the dashboard so users aren't told to invite a dead bot.
• Sharding and downtime for updates is fine — extended absence is not.

---

3. Commands & behavior

• The bot must respond to a help / info command (slash command or prefix — either works) that tells the user what it does.
• Don't spam channels on join. A single welcome message is fine; a wall of embeds is not.
• Don't DM users unsolicited. Replying to something they explicitly triggered is okay.
• Don't @everyone / @here on user's behalf without explicit opt-in.

---

4. Data handling

• Only store what you actually need. "Because I might want it later" is not a reason.
• If you store message content, voice data, or personal information, say so in the long description and explain how users can delete it.
• Never sell user data. Never send user data to third parties without explicit, informed consent.
• Follow Fluxer's Developer Terms of Service and the local data-protection law that applies to you (GDPR, CCPA, etc).

---

5. Monetization

Paid features are allowed and encouraged — but:

• Core features listed in your description must be free, or the description must clearly say "paid".
• You cannot gate basic moderation (kick / ban / mute) behind a paywall.
• Crypto / NFT integrations must not be hidden. If your bot trades, tips, or mints anything, it has to say so in the listing.

---

6. NSFW content

• Bots with any NSFW feature must use the nsfw tag.
• NSFW features must only work in channels Fluxer has marked as NSFW.
• Child-endangering content is a permanent ban — no warnings, no appeals.

---

7. Things we will always deny

• Nukers, raid tools, self-bots, token grabbers.
• Malware or bots that drop payloads onto user machines.
• DDoS / flood / mass-DM tools.
• Bots that exist primarily to bypass Fluxer's rate limits or ToS.
• Scraped copies of someone else's bot.
• Bots whose entire purpose is to advertise another service on join.

---

8. Appeals

If your bot is denied or banned and you believe it was in error, open a ticket in the support server. Include:

• The bot's client ID.
• A link to the listing.
• What you believe was misinterpreted.

Reviewers read every appeal. They don't always agree, but they will explain.

---

Summary

Be honest about what your bot does. Don't abuse the users that trust you. Follow Fluxer's rules. That's 95% of it — the other 5% is the specifics above.

Ship good bots. We'll gladly list them.