Tangerine

Install guide

After Discord: wire Tangerine into your server

Follow these checkpoints once you have joined the community. Mirror the Midnight Orchard visual tokens already loaded globally—same Fraunces/ Figtree rhythm, citrus glow CTA, lime focus rings.

Six checkpoints

  1. 01

    Join the community Discord

    Open the live invite link below so you are inside the server where installs and troubleshooting threads stay.

    You need an account and membership before generating OAuth redirects tied to your guild.

  2. 02

    Create or open a Discord application

    In the Discord Developer Portal, create an Application (or reuse one). Under Bot, add a bot user to this application.

    Keep application ownership scoped—bots inherit token scopes from this application.

  3. 03

    Choose intents deliberately

    Enable privileged intents only when you truly need them. Message Content Intent unlocks reading plain messages your bot consumes.

    Presence Intent or Server Members Intent are heavier privileges—flip them only when your fork listens for presence/members.

  4. 04

    Secure your bot token

    Generate once from the Bot tab, copy into deployment secrets (never commit `.env`), rotate immediately if leaked.

    Treat the token like a password—scope `.gitignore` and CI masked vars accordingly.

  5. 05

    Build the OAuth invite URL

    Under OAuth2 > URL Generator, pick scopes (`bot`, plus `applications.commands` if you expose slash commands) and permission integers matching features.

    Paste the resulting authorize URL into a pinned moderator channel so admins bless installs uniformly.

  6. 06

    Channel posture inside your guild

    Install using Server Settings → Roles → Bot Role hierarchy so moderation bots remain authoritative.

    Wire slash/audio/text handlers toward canonical channels after onboarding completes.

FAQ

Do I need a voice worker?
Optional—speech/music-heavy setups typically deploy or subscribe to a voice-capable worker. Pure chat adapters skip continuous voice pipelines.
Can I run text-only?
Yes—omit voice intents unless required and configure adapters so commands resolve entirely via REST/text gateways.