Theme Guidelines

These are the rules every theme listed on Fluxer Bot List (FBL) has to follow. Themes touch the user's client directly — users are trusting both you and us. These rules exist to keep that trust worth something.

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

---

1. Ownership & attribution

• You can only list themes you made or that you have explicit permission to redistribute.
• If your theme is a fork or uses assets (fonts, icons, snippets) from another creator, credit them in the long description and link the original.
• Reposting someone else's theme without permission is an instant denial and a strike against your account.
• If you're the original author and you find a copy on FBL, open a support ticket with proof and we'll take it down.

---

2. The download

• The download URL must lead directly to the theme file (or a small, obvious release page). No link-shortener chains, no ad-gated gateways, no "complete a survey to download."
• Host on something stable — a GitHub release, a direct CDN, or your own site. Avoid expiring file-host links.
• If your theme uses multiple files, bundle them into one download or provide a clear install path at the top of the long description.

---

3. Safety of the payload

• Themes must only restyle the client. No remote code execution, no fetching arbitrary scripts, no exfiltrating tokens or user data.
• If your theme uses external assets (images, fonts), list the hosts in your description so users know what the client will load.
• Do not embed trackers, analytics pixels, or telemetry. Not even "just to count installs."
• Themes that obfuscate their CSS / JS to hide behavior are denied on sight.

---

4. Content quality

• A preview image or screenshot is effectively required. Listings without one are usually denied.
• The thumbnail should be a clean representation of the actual theme, not marketing art that doesn't reflect what the user will see.
• The short description tells someone in one sentence what the theme changes (palette? layout? both?).
• The long description should cover: look & feel, what areas of the client change, install steps, and any known compatibility notes.

---

5. Accessibility & readability

• Text must remain legible against the backgrounds you set. If you ship a dark theme, color-contrast >= WCAG AA is a soft target, not a nice-to-have.
• Don't hide critical UI — mute buttons, ping indicators, typing indicators, mention highlights must remain visible.
• If your theme is intentionally low-contrast / artistic, say so clearly in the description so users know what they're opting into.
• Don't ship motion-heavy animations as the default. Offer a "reduce motion" variant or document how to disable them.

---

6. Licensing

• You must state a license in your long description (or in the downloaded file). "All rights reserved", MIT, CC-BY, anything explicit is fine.
• If your license permits forks, expect them. If it doesn't, don't act surprised when someone does anyway — report it to us and we'll handle it under §1.
• Do not relicense someone else's work.

---

7. NSFW themes

• Themes with adult imagery (backgrounds, mascots, fonts with explicit content) must use the nsfw tag.
• The thumbnail and preview on the listing page must remain SFW. Route NSFW previews behind a secondary link inside the long description.
• Any theme depicting minors in a sexualized way is a permanent ban — no warnings, no appeals.

---

8. Things we will always deny

• Themes that ship with JavaScript whose purpose isn't pure styling (stealing tokens, injecting ads, auto-DMing contacts, rewriting API responses).
• Themes that mimic official Fluxer / Discord support UI in a way likely to fool users into entering credentials.
• Themes that include cracked / pirated fonts or icon sets without license compliance.
• "Themes" that are just a link to a Patreon / buy-page with no actual download.
• Themes whose entire gimmick is a slur, hate symbol, or harassment joke.

---

9. Updates

Themes get updated. When you push a new version:

• Keep the same listing — don't re-submit. Edit the existing one.
• If the update is breaking (changes install path, needs a new base version of the client), flag it at the top of the long description with a date.
• If the update adds scripts, network calls, or new external assets, treat it like a new submission — reviewers may re-check it.

---

10. Appeals

If your theme is denied or banned and you believe it was in error, open a support ticket with:

• A link to your FBL listing.
• A link to the source (repo, page, archive) proving ownership.
• What you believe was misinterpreted.

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

---

Summary

Make it yours. Keep it safe. Don't hide anything. Keep it readable. Ship updates responsibly.

Build good themes. We'll gladly list them.