How to Build and Run a World of Warcraft Guild Discord Server With YourBot

Updated September 2026

Start a World of Warcraft guild Discord server by designing the member journey first, using YourBot’s Start Your Server to build the foundation, then configuring the services that run recruitment, raids, dungeon groups, voice, and everyday guild life. A useful guild server should answer five questions: How do I join? Where do I sign up? Who is forming a group? Where do we talk? How do I reach an officer?

YourBot brings those workflows into one configurable bot and dashboard. Its ten built-in services cover the standard operations; the marketplace and Plugin Builder provide a path for a specialized feature later.

This guide follows Emberwatch, a fictional 120-member Retail WoW guild with Tuesday and Thursday evening raids, Mythic+ groups, and a social membership. The channel names, schedules, capacities, and policies below are recommended example settings—not automatic YourBot defaults or a real customer case study.

The manual sections work whether you use Start Your Server or create the channels yourself.

Build Around How Guilds Actually Operate

Recruitment is more than an invite link. For example, Chosen Guild’s published joining process starts in Discord, collects character information, and hands the request to an officer. Joining the community and receiving an in-game guild invitation are separate steps.

Use that distinction throughout your own setup. A person can be a welcome visitor without being an accepted guild member. A guild member can enjoy social events without holding a progression-raiding position. A player selecting “Tank” is declaring an interest, not proving readiness to tank your next raid.

Before creating channels, write a short guild brief: game edition, region, home realm or recruitment scope, schedule with time zone, progression goals, social expectations, application process, and officer contacts. Put the member-facing version in #guild-information.

For Emberwatch, the goal is a friendly, organized Retail guild—not a public server with a channel for every class, specialization, dungeon, and alt.

Give Each YourBot Service a Clear Job

These are built-in YourBot services, not ten separate bots to invite. Plan your subscription for the server using the current pricing page; marketplace licenses and AI usage may introduce additional charges.

Enable each service only when somebody will configure and maintain it. Covering all ten does not mean every guild needs all ten on its first evening.

1. Establish Roles Before Automating Access

Separate access roles, staff responsibilities, and self-selected interests.

Do not let an interest role unlock officer channels or bypass recruitment. Also avoid treating two Discord role grants as an automatic “must have both” access rule; test the combined permissions rather than relying on role names.

Place the bot above the roles it must assign, but do not move it above senior staff merely for convenience. Discord’s role hierarchy still limits which roles and members a bot can manage. Administrator does not remove that hierarchy requirement.

2. Build the Foundation With Start Your Server

Sign in with the Discord account that owns the server, select the correct community, and open Start Your Server. The builder is owner-only. Check the building as indicator so you know which bot application needs access. It needs channel visibility and the appropriate Manage Channels and Manage Roles permissions for the approved changes.

Use this prompt as a starting point:

Build a Discord layout for Emberwatch, a 120-member Retail World of Warcraft
guild in the North American region. We raid Tuesday and Thursday,
20:00–23:00 America/New_York, and run Mythic+ and social activities.

Separate visitors, accepted trials, guild members, and officers. A visitor
clicking Verify must not automatically become a guild member or raider.
Offer self-selected Tank, Healer, DPS, Raid Alerts, Mythic+ Alerts, and
Guild Streams roles without administrative permissions.

Create a compact welcome/rules/application area; guild chat, introductions,
crafting and screenshots; raid signups, strategy and logs; a Mythic+ listing
channel; announcements, streams and giveaways; and private officer,
recruitment-review, moderation-log and ticket-log channels.

Keep one permanent Raid Voice room. Create a separate Join-to-Create lobby
for five-person parties. Keep officer channels and recruitment reviews private.

Enable the ten built-in YourBot services and configure the supported settings.
Use Welcome for visitor verification, Tickets for recruitment and officer
contact, Sentinel for moderation, Beacon for raids, Group Finder for parties,
Join-to-Create for party voice, and Analytics for community activity.
Prepare destinations for Announcements, Social Feeds, and Giveaways; we will
create the actual schedules, subscriptions, and draws manually afterward.

Preserve existing channels and roles where practical. Do not delete anything,
start public giveaways, or activate punitive moderation during this setup.
Show any work that still needs manual configuration.

For an existing guild, replace the example role names with your actual roles. Reusing them is usually less disruptive than creating a second membership hierarchy.

Keep the proposed layout compact

A practical starting layout is:

START HERE — visible to newcomers
  #welcome-and-verify
  #rules
  #guild-information
  #choose-roles
  #apply-and-contact

GUILD LIFE — Trial and Guild Member access
  #guild-chat
  #introductions
  #crafting-and-alts
  #screenshots

RAIDS AND GROUPS — Trial and Guild Member access
  #raid-signups
  #raid-strategy
  #logs-and-vods
  #mythic-plus-lfg
  #group-planning

GUILD UPDATES — approved members
  #announcements
  #guild-streams
  #giveaways

VOICE — approved members
  Raid Voice
  Create Party Room

OFFICERS — appropriate staff only
  #officer-chat
  #recruitment-review
  #mod-log
  #ticket-log
  #analytics-alerts

Make #group-planning a Forum only when your Discord server supports that channel type. Otherwise, start with the Group Finder listing channel and add the optional forum later. Channels containing rules or official announcements should normally be read-only for members.

Review what will actually change

Inspect Channels, Roles, and Services, not just the conversational summary. Use See it as for a newcomer, Visitor, Trial, Guild Member, and Officer. Check who can read and who can post.

Review the Safety check, keep deletions unchecked, and inspect the individual operations before approving the build. Save the pre-build snapshot and read the final report. Structural undo does not restore messages deleted with a channel.

The Start Your Server guide explains the complete review and recovery flow.

Important: enabling a service is not the same as finishing it. The builder supports a defined set of service settings. Announcement schedules and Social Feeds subscriptions still need to be created manually; event rosters, recruitment forms, and other specialized configuration also deserve their own review.

3. Manual Setup: Welcome and the New-Member Journey

Open Welcome → Settings. Set Welcome Channel to #welcome-and-verify, write the greeting, and preview the message or welcome card.

A useful greeting is specific:

Welcome to {server}, {user.mention}!

Read #rules and #guild-information, then verify below.
Choose your gameplay interests in #choose-roles.
To join the guild or speak privately with an officer, use #apply-and-contact.

Verification opens the visitor workflow. Guild and raid acceptance are
separate officer decisions.

Replace the plain channel labels with actual Discord channel mentions when configuring the message.

Configure verification deliberately

Under Verification Gate, enable verification, select #welcome-and-verify as Verify Channel, and choose Visitor as Verified Role. Add the short rules acknowledgment you want displayed.

Select Save All Settings, then Post / Update message. Saving the settings and posting the verification message are separate actions.

Review autoroles as well. Do not place Guild Member, Raider, or staff roles in an automatic joining flow. Welcome’s verification step can delay autorole and buddy assignment until the member clicks, but the assigned roles still need to be appropriate.

Let people choose interests, not privileges

In Role Menus, publish Tank, Healer, DPS, and the notification roles to #choose-roles. Allow off-spec players to identify more than one gameplay interest where that fits your menu configuration.

Use Start Here Channels to point newcomers toward the rules, guild information, role selection, and applications. Keep welcome DMs optional; the joining process must remain usable when someone has DMs disabled.

The built-in Buddy System can pair newcomers with a configured Buddy Pool Role. For Emberwatch, select Veteran Guide and give volunteers a simple job: answer initial questions and help the newcomer find an appropriate activity. That is already a Welcome feature; it does not need a custom mentor plugin.

Test: a new account verifies, receives Visitor, selects interests, and can apply—but still cannot read recruitment reviews or raid strategy. An officer then assigns Trial and confirms the intended guild channels appear.

4. Manual Setup: Tickets for Recruitment and Officer Contact

Open Tickets. Build your staff teams and intake forms before publishing the member-facing panel.

Create a Recruitment team from the officers who actually review applications. Being a Raid Lead should not automatically entitle somebody to every private member report.

Use a review queue for applications

Create a panel named Join Emberwatch. In Behavior, choose Channel Mode → Form (review queue — no channel) and set Review Channel to #recruitment-review.

Under Routing, select the Recruitment Staff Team and the application Intake Form. A practical form asks for:

• Character name, realm, and region
• Main class/spec and any comfortable off-spec
• Interest in raiding, Mythic+, social play, or several of these
• Availability, including time zone
• Optional public character or log link, plus anything officers should know

Ask about experience without making applicants share credentials, authentication codes, private account screenshots, or unnecessary personal information.

The panel supports Role granted on Accept, Accept DM, and Reject DM. Leave the role grant blank while testing. Later, use Trial only when the guild has explicitly decided that accepting this application also grants trial access.

Accepting the Discord application does not invite the character into the WoW guild or synchronize an in-game rank. An officer completes that step in game.

Use private conversations for sensitive matters

Create a separate Contact an Officer panel using Private Channel mode. Route it to the appropriate team and category, with a name such as officer-{number}.

Use this for member concerns, absence discussions, and questions requiring a conversation. Staff should claim the ticket, keep private notes appropriately restricted, and close it with an explanation.

Add an SLA policy only when officers can maintain the target. A volunteer guild can publish “we review applications each evening” rather than implying around-the-clock support. Keep transcripts and exported records restricted; they may include intake answers and staff notes.

Test: submit an application and a private officer request with a normal account. Verify routing, acceptance/rejection messages, role grants, requester visibility, and an unrelated member’s inability to read either record.

5. Manual Setup: Sentinel Without Punishing Normal Guild Conversation

Open Sentinel and use its setup flow to establish the moderation log, quarantine role, and moderator roles. Confirm your Officer or Moderator role is selected rather than assuming its name will be recognized automatically.

Start with the Standard protection preset and keep starter rules in log-only while you tune them. Sentinel supports both rule-level testing and a broader log-only control for rules.

For a WoW guild, review spam rate, repeated messages, mention floods, suspicious links, and newcomer behavior. Test ordinary character links, combat-log links, recruitment text, and legitimate guild excitement in the rule tester. A boss kill can generate capital letters and repeated celebration messages without being an attack.

Inspect what would have happened before enabling deletion, warnings, or timeouts. Use narrow exceptions where justified rather than exempting the entire guild from moderation.

Review raid-response settings separately. A log-only rule configuration is not a substitute for understanding the actions configured for a join surge. Record who can intervene and what the quarantine role actually permits.

Keep Discord’s native safety controls available, but avoid duplicate punishment. One incident should not receive unrelated warnings from two bots and a second escalation nobody intended.

Test: run a harmless sample through the rule tester, inspect the resulting behavior, and check staff access to cases and reports. Test actual enforcement only in a controlled setting with a volunteer account—not during a live raid.

6. Manual Setup: Beacon Events for Raid Nights

Use Beacon Events for the guild’s scheduled commitments. Begin with its announcement and log destinations, then create the first raid from a template or the event editor.

The editor follows Event Info → Roles → Design → Actions → Finish.

Configure one event before repeating it

In Event Info, use a title such as Emberwatch Raid Night — Tuesday. State the content, difficulty, preparation expectations, voice channel, and expected finish time in the description.

Enter the date carefully: the reviewed Beacon editor treats Date & Time as the browser’s local time, then converts it for storage and Discord display. An officer in another time zone should not blindly type 20:00 because the guild raids at 20:00 Eastern. Check the displayed Discord timestamp before publication and recheck recurring events around daylight-saving changes.

For this example, set Max Participants to 20. In Roles, use WoW Raid or Quick Add and review the Signup Role Tree. A sample roster is:

Tank:2, Healer:4, DPS:14

That is Emberwatch’s example composition, not a requirement for every raid difficulty or encounter. Adjust it to your actual team. Signup labels represent intended play roles; they do not verify a character’s gear or specialization.

Publish the expectations as well as the buttons

Use the Design fields for Requirements, Loot Rules, Voice Channel, and Contact where useful. Link the guild’s actual policies rather than writing a different loot rule on every event.

In Actions, choose Opt-in, set a Signup Deadline, and add reminders. A reasonable starting policy is a deadline 60 minutes before the raid and reminders 60 and 15 minutes before it. These are proposed settings, not required defaults.

Leave Auto-create voice channel off for Emberwatch’s main raid because the guild already has permanent Raid Voice. A special event can use automatic voice separately after its category, timing, and participant access are configured.

Review the full/waitlist behavior, then save the reusable template and configure recurrence for the guild’s chosen weekdays. Officers should explain how standby players are contacted and how the final roster is selected.

Test: have several members select different roles, withdraw, and fill a small test event so you can inspect the waitlist. Confirm a reminder reaches the intended audience and the date displays correctly for an officer in another time zone.

7. Manual Setup: Group Finder for Mythic+ and Other Parties

Use Group Finder when the main job is assembling a suitable party. It supports planned starts as well as pickup groups; the distinction from Beacon is the workflow, not simply “now versus later.”

Configure the board

In Group Finder → Settings, select #mythic-plus-lfg as Listing Channel, a staff destination for Log Channel, and an alert destination only when the guild wants shared alerts.

For a first rollout, choose Max Active / User: 2, Default Expiry: 2 hours, and a listing cooldown of 60 seconds. These are suggested anti-clutter settings; change them after observing your guild.

Keep cross-posting off while establishing the local workflow. Add a Forum Channel and enable automatic forum threads only after confirming the forum exists and its permissions are correct.

Separate two kinds of approval

Require Listing Approval means staff review a listing before it becomes active. Join Mode → Request means a group leader approves people joining that group. They solve different problems.

Trusted guild members may not need staff approval for every listing. A demanding run can still use Request joining so its leader checks the applicants.

Build a useful dungeon template

Create a WoW dungeon template with five positions: one Tank, one Healer, and three DPS. Include region, activity, and a short description explaining the run’s purpose.

Offer meaningful experience labels such as Learning, Chill, and Farm. Describe intent—teaching, completion, or pushing—rather than relying on a key number alone.

A member can create a listing from the template or /group create, then set Party Size, Expires In, optional Starts In, Join Mode, and Visibility. Confirm the creator’s own position is reflected before telling others how many spots remain.

Start with Local distribution, but do not treat that label as a confidentiality guarantee. Group Finder also has a public-facing listing surface. Keep personal contact details and sensitive guild information in private workflows, not listing descriptions.

Test: create a five-player group, select roles, fill it, try the waitlist, have someone leave, and close the run. Separately test Request joining so officers understand what needs approval.

8. Manual Setup: Temporary Voice Without Duplicate Rooms

Open Join-to-Create Voice Channels. Select Create Party Room as the lobby and the approved-members Voice category as the destination.

Set a readable name such as Party — {display_name}, a user limit of five, and Delete when empty on. Keep Raid Voice permanent.

Review the permission mode. For this layout, inheriting the correctly configured category is straightforward: Trial and Guild Member can join; Visitor cannot. Self-selected Tank or DPS roles should not grant an alternative route into restricted voice rooms.

Review Creator is owner deliberately. It can give the room creator meaningful channel-level controls, including renaming and member-management actions. Leave it off during initial testing, then enable it when the guild wants members to manage their own rooms and understands the scope.

The bot needs the channel and member-moving permissions for this workflow. Test inside the actual category, where permission overrides matter.

Use one voice-creation mechanism per activity. For Emberwatch, raids use the permanent room and Mythic+ parties use Join-to-Create. Do not also activate a second automatic room for the same group merely because another service offers one.

Test: join the lobby, confirm the transfer and five-person limit, bring another member in, then leave. The room should remain while occupied and disappear after the last person leaves.

9. Manual Setup: Announcements for the Weekly Guild Brief

Open Announcements and create the weekly schedule message. Configure Internal label, Channel, Timezone, Message, and Recurrence.

For Emberwatch, use #announcements, America/New_York, Weekly, Sunday, and 18:00. Unlike Beacon’s date input, this form has an explicit time-zone field. Do not assume every service inherits one universal clock setting.

Keep the message useful:

EMBERWATCH — THIS WEEK

Raid nights: Tuesday and Thursday. Use #raid-signups for event details.
Keys and teaching groups: post in #mythic-plus-lfg.
Crafting help: use #crafting-and-alts.
Applications and private officer contact: #apply-and-contact.

Update your signup when availability changes. A standby signup is not a
confirmed raid position.

Keep @everyone and @here disabled. Use an optional notification role only when the message genuinely warrants a ping.

A recurring static announcement does not automatically pull this week’s roster, guild-bank inventory, or raid progress. Update changing content yourself; use Beacon for event-specific reminders rather than duplicating them here.

Test: schedule a short-lived test post in a staff channel, verify time and mentions, then remove that test schedule before creating the public recurring one.

10. Manual Setup: Social Feeds for Streams and Useful Updates

Open Social Feeds, choose the supported source, and supply the account, channel identifier, or feed URL in the format requested by that source.

Start with the guild’s own Twitch stream or YouTube channel. Set Display name, Destination → Channel to #guild-streams, and an optional Ping role such as Guild Streams. Keep the recommended polling interval unless there is a reason to change it.

The editor provides Only post if it mentions and Never post if it mentions. Include keywords match at least one term; an exclusion match blocks the item. Both inspect title/body text rather than proving which game a streamer is playing.

For example, a mixed-game video feed could include World of Warcraft, WoW and exclude sponsor, giveaway. Test the result against real titles; abbreviations can match unrelated content or miss a video titled only with a boss name.

Do not assume a dedicated Battle.net/WoW news connector. The reviewed game catalog does not supply one. For news, add a working, approved RSS feed when available, or have officers publish selected official links through Announcements. A normal webpage is not automatically an RSS feed.

Test: confirm a relevant new item reaches the test channel, an excluded item does not, and only the intended role is mentioned.

11. Manual Setup: Analytics for Guild Health, Not Player Rankings

Open Analytics, then Settings. Set Exclude Bots to Yes, choose the Timezone (display), review Data Retention, and configure Excluded Channels.

Exclude officer discussion, recruitment review, ticket logs, moderation logs, and automated feed channels from the measurements where appropriate. New private ticket channels need continued attention; do not assume excluding one existing channel automatically excludes every future ticket.

Use Excluded Roles carefully: excluding Officer can remove that person’s activity across the server, not just activity in officer chat.

The current settings also expose Invite Tracking, which requires Manage Server. Enable it only when recruitment-source attribution is useful and that permission is justified.

Review weekly message and voice participation, channel activity, and retention. Ask whether trials are finding groups and whether an apparently quiet text channel is accompanied by healthy voice activity.

Discord activity is not encounter attendance, damage performance, loot eligibility, or an objective measure of guild commitment. Do not automatically award Raider or Officer because somebody accumulated messages or voice hours.

Use a modest alert to prompt investigation, not punishment. School schedules, vacations, progression breaks, and game updates can change activity. Keep rewards cosmetic or community-oriented when using them.

Test: generate known activity in an included channel, compare with an excluded one, and verify dashboard access with an ordinary member. Explain the enabled tracking to the guild before relying on it.

12. Manual Setup: Giveaways for Community Celebrations

Giveaways is optional. Use it for a guild anniversary or an artwork prize, not as a replacement for the raid’s loot policy.

Create a giveaway with Title, Description, and #giveaways as Channel. Choose Duration or Pick dates, checking the time zone shown by the form, then configure the Prize tiers.

For an equal-entry community draw, leave Booster weight at zero and do not add Role weights. Review minimum account age and member days only when those restrictions match the published eligibility rules.

A Dedup window excludes recent winners when enabled. Explain that rule before entries open rather than surprising a member after selection.

State who supplies the prize, who is eligible, when the draw ends, and how the winner claims it. For this example, entry requires no payment. Do not request a WoW password or account access, and do not imply that YourBot automatically delivers an in-game reward.

Test: run a clearly labeled no-prize test with volunteers, inspect entry behavior and the result, and verify the staff workflow before publishing a real giveaway.

13. Add a Custom Guild Feature Only After the Foundation Works

Browse the marketplace before building something new. Review the listing, capabilities, data handling, and current installation terms rather than assuming a plugin exists for every WoW idea.

A useful first Plugin Builder project is a crafting-request board. It complements the guild’s existing channels without replacing recruitment, events, or group formation.

Create an Emberwatch crafting-request plugin for our YourBot server.

Members submit a character name and realm, item or recipe name, desired
quality, whether materials are ready, and an optional deadline note.
Administrators choose the request channel and approved Crafter role.

Approved crafters can claim a request. The requester or assigned crafter
can mark it completed; the requester can cancel it. Prevent duplicate
claims and unauthorized edits. Store state separately for each server.

Provide a dashboard listing Open, Claimed, Completed, and Canceled requests.
Keep contact details out of public listings. Use manual user input only:
no Battle.net login, no account credentials, no automatic in-game orders,
no gold transfers, and no assumption that recipe data has been verified.

Show clear errors for missing permissions, unavailable channels, and stale
buttons. Make the request board usable without mandatory DMs.

This is a proposed custom plugin, not an existing built-in crafting service.

Review the generated plan, commands, storage, and dashboard before approving the build. Inspect the source and validation results, then test the committed version through the Dev Portal. Check the current development-install duration and limits in the interface; a temporary test install is not permanent deployment.

A developer can continue the same plugin using the YourBot SDK. The local tools include yourbot dev and yourbot validate; source can be maintained in VS Code and submitted through the supported upload or repository workflow. The result targets YourBot’s managed plugin runtime, not an unrestricted standalone bot.

Keep dependable recurring raid reminders in Beacon or Announcements instead of assuming an AI-generated plugin has an independently running scheduler.

Keep WoW Integrations and Discord Automation Distinct

YourBot organizes the community around the game. Do not assume it automatically imports guild ranks, verifies a character, synchronizes every alt, reads combat logs, distributes loot, or places in-game crafting orders.

Keep your actual character, roster, and combat-analysis links in #guild-information and #logs-and-vods. Officers can consult them without pretending Discord activity is equivalent to in-game evidence.

Blizzard separately documents Battle.net/Discord linking and guild-chat integration for the Curse of Ula’tek update. Follow Blizzard’s instructions and confirm availability in your game edition before adding it. That is a Blizzard feature, not a YourBot plugin.

Use a deliberate channel for bridged chat and test how messages appear before relying on moderation or analytics there. Account-linking requirements and message handling must not be assumed from ordinary Discord messages.

Prove the Setup With a First-Week Walkthrough

Before inviting the whole roster, run one volunteer through the complete journey:

1. Join: read the rules, verify as Visitor, choose interests, and submit an application.
2. Review: an officer accepts or rejects it; the resulting role grants only the intended access.
3. Raid: sign up, change a role, withdraw, and check standby handling and time-zone display.
4. Dungeon: create a group, fill its slots, test approval or waitlisting, and use the selected voice workflow.
5. Support: open a private officer ticket and verify that another member cannot read it.
6. Communicate: receive a scheduled brief and a selected feed update without duplicate or excessive pings.
7. Review: officers inspect moderation tests and analytics, then disable any unused test schedules or panels.

During the first week, have one officer own each service. After the first raid, ask members what confused them. After a week, review abandoned listings, missed reminders, unanswered applications, and unused channels before adding more features.

For an existing guild, keep the old systems available during testing, but give each automated action one owner. Preserve records before removing another bot; Start Your Server is not a general importer for other providers’ data.

Adapting the Plan for Smaller Guilds and Classic

A friends-and-family guild can merge several discussion channels and postpone giveaways, invite attribution, and detailed analytics. Keep the clear welcome path, event schedule, party formation, and officer contact.

For a progression team, add roster-selection expectations, standby communication, and controlled strategy posting before adding more automation.

For Classic, replace the Retail Mythic+ examples with the dungeon, raid, preparation, and group structures relevant to your edition. Review raid capacity and role composition rather than copying the 20-person example unchanged. The YourBot workflow remains useful; the game-specific template should change.

Frequently Asked Questions

Can Start Your Server configure the whole guild automatically?

It can create the structure and apply supported service settings. You still need to review permissions, create detailed forms and events, add announcement schedules and feed subscriptions, and test the resulting workflows.

Can guild officers run Start Your Server?

The builder is restricted to the Discord server owner. Give officers access to the individual service controls they need through the supported dashboard-access settings; do not assume an in-game guild rank grants dashboard access.

Do we need both Beacon Events and Group Finder?

Use Beacon for recurring guild commitments and Group Finder for party formation. Both can involve scheduled activity. Choose based on roster and joining workflow, and avoid posting two competing signup systems for the same run.

Does verification prove somebody belongs to our WoW guild?

No. Welcome’s verification button grants the configured Discord role. Guild acceptance, character identity, and raid approval require separate checks or an explicitly implemented integration.

Do we need to host a separate bot for every custom feature?

No. Built-in services and YourBot SDK plugins use the managed platform. A custom plugin still needs review, testing, and an appropriate ongoing installation—not merely a generated draft.

Build a Guild Server People Can Actually Use

A strong WoW Discord is not the one with the most channels. It is the one where a newcomer can become a member, a member can find a group, a raid leader can communicate clearly, and an officer can resolve a private issue without confusion.

YourBot provides the shared foundation: Start Your Server for the layout, built-in services for guild operations, and the marketplace, Plugin Builder, and SDK for the specific feature your guild still needs.

Start with your guild’s design, configure the services around real member behavior, and launch only after the complete journey works.