Hexed

Hexed documentation

From empty server to a complete community.

Practical setup guides for every major module—what it does, how to configure it, what to test, and the defaults we recommend.

Start setup Command reference

Expansion guide map

Fair casino

8 new games

Party games

14 formats

Gathering v2

Progress & co-op

Social economy

Drops, races, shootouts

Economy controls

Policy & health

Guide 01

Quick start

Invite Hexed, check its role, choose modules and verify the setup.

1

Invite and place the bot role

Add Hexed with the permissions shown by the invite flow. In Server Settings → Roles, place the Hexed role above every role it must manage. It can never act on the server owner or roles above its own.

2

Open the dashboard

Log in with Discord, select your server and open Modules. Enable only the systems you intend to configure; event listeners and commands follow those module switches.

3

Assign staff access

Use the Permissions page to delegate individual Hexed capabilities. Keep Discord Administrator limited, and grant moderators only the bot actions they actually need.

4

Build in a test channel

Create a private setup channel and test greetings, logs, panels and moderation actions there before announcing them. Use the command reference whenever you need exact syntax.

Recommended configuration

  • Keep Hexed above member, muted, jailed, reward and ticket roles.
  • Create separate private channels for moderation logs, security alerts and ticket transcripts.
  • Test one module at a time so a permission problem is easy to isolate.
Related commandshelppingFull syntax
Guide 02

Recommended server foundation

A practical channel, role and permissions layout before enabling automation.

1

Roles

Use separate Owner, Administrator, Moderator, Support, Bot, Muted/Jailed, Member and reward roles. Put Hexed above every managed role while keeping it below trusted human administrators.

2

Operational channels

Create private channels for staff logs, security alerts, appeals, application reviews and ticket transcripts. Keep public welcome, suggestions, games and counting channels separate.

3

Least privilege

Channel overwrites should do most of the work. Avoid giving every staff role Administrator, and use Hexed permission nodes when someone needs a bot action without broad Discord powers.

Recommended configuration

  • Require 2FA for moderation actions in Discord.
  • Keep a private incident channel outside the normal moderator category.
  • Review integrations, webhooks and administrator roles regularly.
Related commandsroleloggingFull syntax
Guide 03

Moderation and cases

Cases, warnings, jail, timeouts, staff delegation and member records.

1

Configure roles first

Create muted and jailed roles, put them below Hexed, then verify channel overwrites. Jail snapshots roles and restores them on release; do not manually delete its role while members are jailed.

2

Use reasons consistently

Moderation actions create numbered cases. Write reasons that another moderator can understand later; add private notes for context that should not appear in the punishment reason.

3

Delegate by action

Grant ban, kick, warn, jail and other permission nodes independently from the dashboard instead of promoting every moderator to Administrator.

4

Review and reverse safely

Use the case history when handling disputes. Reverse the original action through Hexed where possible so the audit trail stays complete.

Related commandsbankickwarntimeoutjailcasesnotesFull syntax
Guide 04

AutoMod

Message filters, heat escalation, exemptions and Discord-native rules.

1

Start with high-confidence filters

Enable scam links, invite abuse, mass mentions and obvious spam first. Add word filters carefully; broad fragments create false positives.

2

Choose escalation

Heat lets repeated violations escalate instead of applying the harshest punishment immediately. Set thresholds appropriate to your community size and message speed.

3

Add narrow exemptions

Exempt staff or trusted bot channels only when required. Avoid exempting the general Member role, which effectively disables the rule for everyone.

4

Test each rule

Use a non-staff test account and confirm the content is blocked, the intended action runs, and the log reaches the correct channel.

Recommended configuration

  • Begin in log/warn mode before enabling automatic bans.
  • Separate link rules from word filters so incidents are easy to diagnose.
  • Revisit thresholds after large events or rapid server growth.
Related commandsautomodfilterFull syntax
Guide 05

Anti-raid

Join gates, mass-join detection, raid mode and honeypot protection.

1

Set a join baseline

Choose minimum account age and avatar requirements that fit your audience. Communities expecting brand-new Discord users should use a lighter gate and rely more on verification.

2

Configure burst detection

Set mass-join thresholds above normal invite spikes but below a damaging raid. Raid mode can lock entry paths while staff investigate.

3

Add a honeypot

Place the bait channel where automated raiders can see it, clearly tell legitimate members not to interact, and confirm its action and alert channel.

4

Prepare recovery

Document who can disable raid mode, where alerts arrive, and how legitimate members rejected by the gate can contact staff.

Recommended configuration

  • Do not make honeypot instructions ambiguous.
  • Send security alerts somewhere raiders cannot view.
  • Lower thresholds temporarily before advertised high-traffic events only if staff are online.
Related commandsantiraidhoneypotFull syntax
Guide 06

Anti-nuke

Protect roles, channels, bans and other destructive administration actions.

1

Establish trusted actors

Whitelist only the owner, essential administrators and known automation. A whitelist bypasses protection and should stay very small.

2

Tune action limits

Set limits for destructive bursts such as channel deletion, role deletion, bans and kicks. Use tighter limits for actions that almost never happen legitimately.

3

Choose containment

Hexed can neutralize the actor by removing dangerous roles. Verify its role is high enough to act on every administrator you expect it to contain.

4

Run a controlled drill

With a disposable role/channel and a trusted test account, confirm detection, containment and alert delivery. Never test against production structure.

Recommended configuration

  • Anti-nuke cannot contain the server owner or roles above Hexed.
  • Keep trusted/whitelist entries minimal and review them monthly.
  • Maintain Discord audit-log access for incident reconstruction.
Related commandsantinuke configFull syntax
Guide 07

Tickets

Panels, intake questions, staff workflows, transcripts and access control.

1

Design the workflow

Create a ticket category, support role, transcript channel and one panel per request type. Separate support, reports and purchases when they need different staff or questions.

2

Build the intake modal

Ask only questions staff need before replying. Use clear labels and examples; long forms reduce completion and create low-quality answers.

3

Set panel and staff controls

Publish the panel, then test create, claim, trainee access, allow/deny member access and close behavior. Confirm users cannot see other tickets.

4

Verify closure and transcripts

Close a test ticket and confirm the transcript reaches the private archive with the correct participant and timing data.

Recommended configuration

  • Use a private transcript channel with retention appropriate to your policy.
  • Keep panel copy explicit about response times and prohibited misuse.
  • Review ticket statistics to spot queues that need more staff or better intake questions.
Related commandsticketFull syntax
Guide 08

Greetings and onboarding

Welcome/goodbye messages, auto-roles, role menus and server onboarding.

1

Create a member path

Decide what a newcomer sees before verification, after accepting rules and after selecting interests. Keep the first screen short.

2

Configure greetings

Build welcome, goodbye and boost messages with the visual message builder and preview variables before publishing.

3

Assign baseline roles

Use auto-role only for safe baseline access. Put optional colors, regions, interests and notifications behind button or reaction-role menus.

4

Test as a newcomer

Join with a test account and verify channel visibility, role assignment, links and welcome mentions from start to finish.

Related commandswelcomeautorolereactionrolebuttonroleFull syntax
Guide 09

Automation

Autoresponders, reaction triggers, sticky messages, timers, boards and bump reminders.

1

Pick the smallest trigger

Prefer exact keywords and scoped channels over broad contains-matches. Add a cooldown when a trigger could fire repeatedly in active chat.

2

Build reusable messages

Use the shared embed/container builder for consistent branding and variables. Preview fallbacks for users, channels and roles.

3

Avoid automation loops

Do not configure bots to trigger one another. Exclude bot messages and keep recurring timers comfortably below Discord rate limits.

Related commandsautoresponderreactiontriggerstickytimerboardbumpreminderFull syntax
Guide 10 Premium guild

Activities and engagement

Guild-health analytics, fair voice tracking, retention, leaderboards and giveaway requirements.

1

Enable collection

Activities is premium-guild gated. Enable it before expecting historical totals; tracking begins when the module is active and does not fabricate earlier data.

2

Choose visible metrics

Use messages, media, eligible voice minutes and game contributions independently. Overall score is optional and must be enabled by a server administrator.

3

Understand eligible voice

A member must be with another participant and cannot be self/server muted or deafened. Solo and inactive voice sessions do not count.

4

Connect giveaways carefully

Start with an attainable recent-message or activity requirement. State the rolling window in the giveaway copy so members understand eligibility before entering.

5

Read guild health, not only volume

Use the dashboard’s active-member trends, channel health, activation cohorts, role comparisons and member drilldown. Export the current authorized filter to CSV when deeper analysis is needed.

Recommended configuration

  • Publish metric definitions alongside competitive leaderboards.
  • Use multiple contribution types so text-heavy communities do not exclude voice or game participants.
  • Avoid changing score weights mid-week.
Related commandsactivities statsactivities leaderboardactivityinsightsgiveaway startFull syntax
Guide 11 Premium guild

Campaigns and live events

Automatic Hexed-wide campaigns and premium server events spanning Activities, Games, and Economy.

1

Understand the two scopes

Hexed always maintains a free global campaign that rotates automatically. Premium guilds can also run local campaigns, and members make progress in both from the same eligible actions.

2

Start from a template

Open Dashboard → Campaigns and copy Community Kickstart, Game Night League, Economy Week, Creator Showcase, Voice & Social, or Seasonal Festival. Templates fill the structure and suggested targets but deliberately leave rewards empty.

3

Choose trusted objectives

Select metrics already verified by Activities or the Battle Pass pipeline. Members cannot submit totals themselves; message cooldowns, eligible voice rules, game results, and economy command completion remain authoritative.

4

Budget and publish

Set dates, points, and optional per-objective coin or title rewards. Guild objectives cannot award gems and may award at most 10,000 coins each; those limits do not apply to Hexed-managed global campaigns. Review the possible maximum payout before publishing and use points-only objectives when a reward is not necessary.

5

Track and claim

Members use `campaign` to see deadlines and progress, `campaign claim <objective>` for one-time rewards, and `campaign leaderboard` for proportional point rankings.

Recommended configuration

  • Use three to six objectives so the event stays readable.
  • Mix conversation, voice, games, and economy metrics instead of rewarding one behavior exclusively.
  • Keep rewards proportionate to normal weekly earnings and use titles for prestigious milestones.
  • Do not change the meaning of an objective after members begin progressing.
Related commandscampaigncampaign claimcampaign leaderboardFull syntax
Guide 12 Premium guild

Games and Royale

Premium-guild channel, board, word, creative, music, survival and daily games with shared engagement rewards. Economy and casino commands are not part of this gate.

1

Create a games channel

Use a dedicated channel where lobbies and turn updates will not overwhelm regular conversation. Enable the Games module for the guild.

2

Configure announcements

Optionally choose an opt-in game role to ping when a Royale lobby opens. Do not ping broad community roles for every match.

3

Run the lobby

Start the selected mode, let members join through the lobby UI, then begin. Royale modes differ in format and narration, while Solo Death focuses on an individual run and Death Battle resolves direct combat.

4

Enable spectator betting

Spectators use the Bet button, choose a participant privately and enter an amount in a modal. Explain closing times and server limits before stakes open.

5

Choose a party format

Use party create for Fill-in-the-Blank, Bingo, Typing/Fastest/Most Words, Connect Four, Checkers, Hangman, team trivia, emoji/caption/drawing/music guessing or the daily puzzle. Join and play actions are stored durably, while judged creative rounds require the host to choose a participant.

Related commandspartyfillblankbingotypingracefastestwordmostwordsconnectfourcheckershangmanteamtriviaemojiguesscaptioncontestdrawguessmusicguessdailypuzzleroyalehungrygamesdeathbattlesolodeathtriviacountingwordchainFull syntax
Guide 13

Economy

Earning, banking, businesses, prestige, crews, crafting, pets, markets and PvP.

1

Learn the account model

Coins and core ownership are global across participating servers. Wallet funds are exposed to robbery; bank funds are safer but subject to limits and the configured economy rules.

2

Build income

Use jobs, daily streaks, gathering and quests for active income. Businesses generate passive income but require condition management; each prestige level boosts business output and prestige upgrades are weekly.

3

Use markets and groups

Craft from gathered materials, trade items or pets through auctions, invest in the changing market, and form crews for a shared vault and heists.

4

Understand safeguards

Transfers are limited across incoming and outgoing volume over 24 hours. Crew vaults are capped. Padlocks stop one robbery per 24 hours, while shields protect for 8 hours followed by an 8-hour recovery window.

5

Configure server policy

Premium managers can set transfer tax and exemptions, treasury routing, role income, command costs, starting balances and local account ceilings. Global transfer and owner safety limits remain authoritative.

6

Advance gathering disciplines

Fishing, mining and hunting have separate locations, equipment condition, bait, skill trees, collections and records. Premium servers can host co-op expeditions and weekly collection goals.

Recommended configuration

  • Keep substantial funds in the bank rather than the wallet.
  • Read confirmation screens before auctions, wagers and large purchases.
  • Use buffs before their intended activity; replacement warnings prevent accidental waste.
Related commandsbalanceworkdailybusinessprestigecrewshopgatheringroleincomeauctionFull syntax
Guide 14

Betting and casino

Free economy/casino play, event markets, interactive Royale bets and responsible server configuration. Guild-hosted Games remain premium.

1

Set server limits

Administrators should choose stakes appropriate to their economy. Start low, observe coin flow and increase limits only if losses cannot destabilize normal progression.

2

Use the interaction flow

For game events, press Bet, choose an outcome or participant in the private menu, enter the amount and review the confirmation. Bets lock when the market closes.

3

Understand settlement

The system settles eligible bets when the underlying event completes. Players participating in an event may be excluded from wagering on that event to reduce manipulation.

4

Use interactive risk games

High-Low, Tower and Double-or-Nothing keep resumable server-side state and show the current cash-out. All-In requires a second confirmation with the exact stake and post-loss wallet. Per-game switches, stakes, cooldowns and membership tiers layer beneath global limits.

5

Join official events

Official Hexed casino tournaments and poker tables are labeled separately from community-hosted games. Tournament entry fees are escrowed and players receive isolated chips. Workers open and settle events; at poker tables they deal and enforce turn timers but never choose a player action. Premium server managers can opt into announcements and an optional role ping from Betting settings.

Recommended configuration

  • Make limits and closing rules visible in the game channel.
  • Treat wagers as optional entertainment, not the primary way to progress.
  • Review unusual bet concentration before expanding limits.
Related commandsbetblackjackcrapshighlowtowerscratchcupsdoubleornothingcardwarallincashdropanimalraceshootoutlotterypokerFull syntax
Guide 15

Giveaways

Entry rules, activity gates, rerolls and fair operational practices.

1

Define eligibility

Choose duration, winner count, prize and any role or activity requirements. Requirements should be achievable before the giveaway ends.

2

Publish clear rules

State whether recent messages, voice or game participation is required and which time window is evaluated. Avoid changing conditions after entries open.

3

Close and verify

Let the scheduled worker end the giveaway, then verify winners still meet external rules before fulfillment. Use reroll only for a documented disqualification.

Related commandsgiveaway startgiveaway endgiveaway rerollFull syntax
Guide 16 Premium guild

Cooperative Worlds and collections

Turn varied server activity into bounded, guild-owned progress across research, projects, expeditions, encounters, collectibles, and a permanent museum.

1

Enable the world

A manager enables Cooperative Worlds from Games → Cooperative Worlds or with world setup. Choose an announcement channel, optional role, timezone, voting, and automatic encounters.

2

Install the persistent world board

After world setup, run world send in a dedicated channel. Hexed installs eight bot-authored panels for the living vista, Town Hall, research, museum, expeditions, projects, encounters, and chronicle. Use world panels, refresh, repair, or remove to maintain it without deleting progress.

3

Earn and redeem tickets

Qualified messages, media, eligible voice, games, invites, community games, and campaigns produce capped daily tickets. Buttons and modals or world contribute convert tickets into Supplies, Knowledge, Relics, or Resolve. Resources never become coins and cannot be transferred.

4

Research 120 discoveries

Browse eight branches and fifteen tiers from the Research Observatory or dashboard. Every node states its prerequisites, exact resource costs, numeric buffs, mechanic and content unlocks, visual world changes, votes, progress, and research unlocked next.

5

Explore, build, and defend

Ten regional expeditions and a broad project catalog use durable multi-phase contributions. Encounters accept personally capped button actions and settle through a retry-safe worker that edits the original panel with the result.

6

Curate 200 relics

Discover relics across ten regions, historical eras, five rarities, and four variants. Inspect provenance, manage duplicates, and donate permanently to the museum. Completing exhibitions unlocks world monuments, districts, biomes, regions, festivals, and museum wings.

7

Watch the world grow

The World Vista is a deterministic evolving scene. Settlement levels, completed research, museum milestones, monuments, portals, observatories, and active encounters visibly alter the image while state-hash caching keeps interactions fast.

8

Operate safely

Pausing or losing premium stops progression without deleting data. Project and encounter cancellation always previews its consequence. The owner dashboard can inspect aggregate health and queue a retry-safe recovery pass.

Recommended configuration

  • Keep automatic encounters in one visible game channel and use a dedicated opt-in notification role.
  • Let member research votes guide manager decisions, while checking prerequisites before committing resources.
  • Review world history after cancellations or recovery operations; every durable mutation has an audit or ledger record.
  • Encourage varied activity instead of message spam—the total daily ticket cap is lower than the sum of category caps.
Related commandsworldresearchexpeditionworldbosscollectionmuseumFull syntax
Guide 17

Last.fm music

Account linking, now playing, listening charts, taste comparisons and custom cards.

1

Connect your account

Open your Account page in the dashboard and authorize Last.fm. The callback returns you to Hexed and stores the account link; Last.fm can take a moment to reflect a new authorization.

2

Use listening commands

Show the current track, recent scrobbles, top artists, albums and tracks, or compare listening taste with another linked member. Command aliases are listed in the command reference.

3

Customize now playing

From Account, edit the now-playing embed/container with the exposed track, artist, album, user and global variables. Preview the result and configure automatic reactions.

Related commandsfmloginfmnowplayingrecenttopartiststasteFull syntax
Guide 18

Voice and transcription

Join-to-create channels, voice moderation and speech-to-text.

1

Configure VoiceMaster

Choose a join-to-create channel and category. Members receive a temporary channel they can name, limit and manage; Hexed removes it when empty.

2

Set voice moderation access

Delegate move, mute and deafen controls only to staff roles that need them. Timed voice punishments can be reapplied when a member reconnects.

3

Choose transcription channels

Allow-list channels for automatic voice-message transcription, or leave automatic mode off and use the message context action on demand.

Related commandsvoicemastertranscribeFull syntax
Guide 19

Social profiles and roleplay

Profiles, affinity, families, reactions and top-level roleplay interactions.

1

Build a profile

Set bio, pronouns, vibe, theme and other public details from Discord or the account dashboard. Profiles use the existing shared social identity.

2

Build bonds

Interactions such as hugs and compliments build affinity and hearts. Blocks apply both ways and prevent affinity, gifts, reputation, marriage and adoption.

3

Use family features

Proposals use explicit accept/decline controls. Adoption and family relationships prevent loops, while divorce, disown and runaway actions update the tree.

Related commandsprofilehugroastcomplimentpickupratemarryfamilyFull syntax
Guide 20

Logging and audits

Route operational events to private channels without flooding Discord.

1

Split by audience

Send moderation and security events to staff-only channels. Message, member, role, channel and voice logs can use separate destinations when volume is high.

2

Enable useful categories

Log what staff will actually review. High-volume edit and voice events can obscure critical cases when everything shares one channel.

3

Test delivery

Generate a harmless event in each enabled category and confirm the correct channel, detail level and staff visibility.

Related commandsloggingFull syntax
Guide 21

Troubleshooting

The fastest checks when a command, panel or automation does not respond.

1

Check module and premium access

Confirm the module is enabled for the server and, where marked, that the guild has premium access.

2

Check role hierarchy

Hexed must sit above the target member and every role it grants, removes or restores. Discord owner and higher-role protections cannot be bypassed.

3

Check channel permissions

Verify View Channel, Send Messages, Embed Links, Read Message History and any action-specific permissions in the exact channel or category.

4

Check user authorization

For account integrations such as Last.fm, reload the dashboard after authorization and allow a short propagation window before reconnecting.

5

Collect useful context

When asking for support, include the server ID, channel ID, command name, approximate time and any visible error. Never send API keys, bot tokens or shared secrets.

Related commandspinghelpFull syntax