How to Build and Run a Guild Wars 2 Guild Discord Server With YourBot

Build a useful Guild Wars 2 Discord around the activities your guild actually runs, then use YourBot to connect recruitment, event signups, group formation, voice, announcements, and moderation. Start Your Server can create the foundation. The individual service dashboards let you finish the details: who reviews applications, which builds a group needs, where update notes appear, and how members find their next activity.

A Guild Wars 2 server should not simply copy a World of Warcraft raid template. It needs room for multiple guild memberships, flexible combat roles, five-player fractals, ten-player raids, open-world squads, guild missions, and the separate requirements of World vs. World.

This guide follows Wayfarer’s Lantern [LANT], a fictional 120-member NA community with social players, returning adventurers, a raid-training group, and a WvW team. Its names, schedule, permission choices, and example settings are recommendations—not product defaults or a claimed customer deployment.

Start With What Makes Guild Wars 2 Different

A community member is not necessarily an in-game guild member

Guild Wars 2 supports multiple guild memberships; ArenaNet increased the account limit to six in its 2024 studio update. Your Discord may therefore include guildmates, friends from another guild, training participants, and occasional event guests.

Give those people appropriate community access without automatically granting officer privileges, guild resources, or WvW planning access. Publish any representation or attendance expectations before someone applies rather than treating membership elsewhere as misconduct.

Region and map instance matter more than a matching Discord role

ArenaNet’s megaserver explanation distinguishes shared PvE maps from home worlds and preserves the NA/EU region separation. Ask which game region members play in, not merely where they live.

A Discord signup does not place someone on your map. An organizer still needs to share the meeting point, identify the commander, and help the group assemble in the correct in-game instance.

Update the old “raids and strikes” terminology

ArenaNet merged Strike Missions into raids as raid encounters in the February 2026 Raids and Wardrobe update. Its release announcement confirms the change.

Use a name such as #raids-and-encounters, with a channel topic explaining that this includes encounters many returning players still call strikes. Keep the familiar search term where it helps people navigate, without teaching an outdated menu structure.

Build roles describe contributions, not fixed classes

For organized PvE, recruit the functions a group needs rather than assigning every profession to a permanent tank, healer, or damage category. Quickness, Alacrity, healing, damage, and encounter-specific responsibilities are more useful signup information.

Snow Crows’ squad guide explains the common approach of covering Quickness and Alacrity within five-player subgroups. A healer supplying one boon can be paired with a damage-oriented build supplying the other. The examples below use that approach as a starting composition, not a universal rule or an automatic readiness check.

Give Each YourBot Service a Clear Job

YourBot’s ten built-in services can be configured separately. For this guild, assign them these responsibilities:

Enable services because they have a purpose, not because ten switches are available. Review the current platform pricing, AI usage estimate, and any additional marketplace-plugin charges before committing to the setup.

Design Access Before Designing the Channel List

Separate permission-bearing roles from interests and notifications.

Keep WvW Interest distinct from WvW Cleared. Similarly, selecting a Quickness role should not grant Raid Roster access.

Follow Discord’s role and permission guidance. The bot must sit above roles it manages. Channel overrides and the combined permissions from a member’s roles matter; two allowed roles do not automatically create a requirement to hold both.

Build the Foundation With Start Your Server

Create the Discord server, connect it to YourBot, and select it in the dashboard. A guild-branded bot name and avatar can make the resulting messages easier to recognize.

Open Start Your Server using the Discord account that owns the server. Check the building as badge and give that bot the access needed to inspect and manage the intended channels and roles.

Copy-ready guild prompt

Create a Discord server for Wayfarer's Lantern [LANT], a 120-member
Guild Wars 2 community playing in the NA game region.

We welcome social players, returning players, and friends from other guilds.
Our regular activities are fractals, ten-player raid training and reclears,
guild missions, open-world meta events, and an optional WvW team.

Separate Community Member, Recruit, Guild Member, Raid Roster, WvW Cleared,
Officer, Moderator, and Guide roles. Only interests and notification roles
may be self-selected. Clicking verification must not grant guild membership,
raid-team membership, or private WvW access.

Create a compact start area, general and new-player help, builds and guides,
raid signups, LFG listings, guild projects, game updates, private applications,
private officer channels, and a separate restricted WvW area.

Create a permanent raid voice room and restricted WvW command voice.
Add a join-to-create lobby for smaller parties. Keep story spoilers out of
public channel names and onboarding messages.

Enable Welcome, Tickets, Sentinel, Beacon Events, Group Finder,
Join-to-Create Voice, Analytics, Announcements, Social Feeds, and Giveaways.
Prepare supported service settings and channel destinations. Keep moderation
in log-only testing initially. Leave detailed event templates, announcement
schedules, feed subscriptions, and giveaway creation for manual review.

Use clear channel names and short first messages explaining each workflow.
If existing channels or roles are present, preserve them. Do not delete,
rename, or overwrite our live setup without a separately reviewed decision.

A compact target layout

START HERE
  #welcome-and-rules
  #choose-activities
  #guild-information
  #apply-or-contact

COMMUNITY
  #general
  #new-player-help
  #builds-and-guides
  #screenshots
  #guild-projects

PLAY TOGETHER
  #weekly-plan
  #raid-signups
  #lfg-listings
  #event-coordination
  Raid Voice
  Create a Party Room

NEWS AND CELEBRATIONS
  #gw2-updates
  #streams-and-videos
  #giveaways

WVW — RESTRICTED
  #wvw-briefing
  #wvw-coordination
  WvW Command

STAFF — RESTRICTED
  #officer-chat
  #application-review
  #ticket-logs
  #mod-log
  #analytics-alerts

These are destinations to adapt, not a requirement to create every channel. Use threads for individual build discussions and event coordination instead of creating a permanent channel for each profession or encounter.

Review the actual design

Inspect Channels, Roles, and Services, not just the chat summary. Use See it as for an unverified newcomer, Community Member, Guild Member, WvW Cleared member, and Officer. Check that public recruitment remains reachable while staff and WvW areas remain restricted.

Review safety findings and the itemized build operations. Keep deletions unchecked. After building, read the report and retain the snapshot. The builder documentation explains that structural undo does not restore deleted messages.

Enabling a service is not the same as finishing its configuration. In particular, Announcements schedules and Social Feeds subscriptions are created manually. The following sections complete the guild’s working setup and also serve as the manual path for an existing Discord server.

1. Welcome: Turn an Arrival Into a Clear Next Step

Open Welcome → Settings. Set the Welcome Channel to your start area and write a short message that answers three questions: where to read the rules, how to find an activity, and how to apply to the guild.

Welcome to Wayfarer's Lantern!

Start with the rules, then choose the activities you enjoy. Returning to
Tyria? Ask in #new-player-help. Joining our Discord does not require joining
our in-game guild; guild applications go through #apply-or-contact.

In Verification Gate, enable verification, select the Verify Channel, and set Verified Role to Community Member. Save the settings first, then use Post / Update message to publish the verification control.

Create role menus for activities and notifications. Allow multiple interests: someone can enjoy fractals, WvW, and decorating without choosing a single identity. Keep combat-build interests separate from the particular build someone signs up to play tonight.

Use Welcome’s existing Buddy System for newcomer support. Select the Guide role as the Buddy Pool Role and nominate a few volunteers who actually want the responsibility. A welcome DM can supplement the public instructions, but must not be the only route because a member may block DMs.

Test: A newcomer acknowledges the rules, receives Community Member, selects two interests, and finds help. They must not receive Guild Member, Raid Roster, or WvW Cleared through any self-service control.

2. Tickets: Separate Applications From Private Support

The Tickets service can handle both structured applications and conversations that need staff attention. Give them different panels and routing.

Guild application

Create a recruitment staff team, then an intake form with a small number of relevant questions:

In Panels → Behavior, choose Channel Mode → Form (review queue — no channel). Set Review Channel to #application-review. In Routing, select the recruitment team and the intake form.

Set Role granted on Accept to Recruit, or leave it blank when you prefer a completely manual handoff. Configure acceptance and rejection messages that explain what happens next.

The full process is application → officer review → decision → Discord role/message → in-game invitation → membership confirmation. Accepting the form does not invite the player into Guild Wars 2 or validate their account automatically.

Private officer contact

Use a separate Private Channel panel for conduct reports, personal concerns, and problems requiring discussion. Route it to the relevant team and keep transcripts in a restricted destination. State realistic volunteer response hours; do not promise round-the-clock coverage.

Test: Submit two applications from different members, confirm neither can see the other’s answers, accept one, and verify that only the intended role is granted. Then open, claim, close, and retrieve a private test ticket.

3. Sentinel: Protect the Community Without Fighting Normal Game Chat

Open Sentinel, select a suitable starter setup, and explicitly identify the moderation roles, log channel, and quarantine configuration. Do not assume a role named Officer will be detected correctly without review.

Begin with the available dry-run or log-only settings while tuning rules for repeated spam, mention floods, suspicious links, and disruptive joins. Test legitimate waypoint codes, build-sharing messages, guide links, event pings, and enthusiastic conversation after a clear.

A rule that sees several similar guild-mission instructions is not necessarily seeing spam. Adjust conditions, cooldowns, and narrow exemptions rather than exempting every member from moderation.

After reviewing detections, enable the intended enforcement actions and test the resulting case and appeal workflow. Keep Discord’s native safety controls configured and assign one system responsibility for each punitive action.

Test: A designated tester triggers a harmless rule, the correct log appears, staff can review the case, and an ordinary build or waypoint message remains usable. Never test destructive moderation on uninformed members.

4. Beacon Events: Build a GW2 Roster, Not a Generic MMO Roster

Use Beacon for planned guild activities where a reusable signup, reminders, and a clear organizer matter.

ArenaNet describes fractals as five-player content and raids as ten-player content. Set the event’s capacity deliberately instead of trusting a generic template.

Create a ten-player training template

Open Beacon’s template editor and choose Start from Scratch. Work through Event Info → Roles → Design → Actions → Finish.

The deadline and reminder values are this guild’s choices. Change them to fit your organizers.

Under Roles, build the required signup options. One straightforward example is:

Heal Alacrity:2, Quickness DPS:2, DPS:6

Alternatively, use two healing-Quickness slots and two Alacrity-DPS slots alongside six damage slots. The leader then distributes those players between two in-game subgroups. Encounter-specific tanking, positioning, or other special jobs still need explicit assignment.

Set Max Participants separately. Editing the signup role tree does not make an inherited generic event capacity correct. The generic Raid Night preset is not a GW2 composition.

Make the event description useful

State the exact encounter or wing, difficulty, learning goal, expected duration, required game access, voice expectations, and the organizer’s contact. Define “training,” “practice,” and “reclear” rather than assuming everyone interprets them identically.

For training, explain what preparation is genuinely necessary and what you will teach. Do not use achievement points or a broad account label as a substitute for a conversation about experience.

Beacon’s reviewed Date & Time field uses the editor’s local browser time before conversion to a Discord timestamp. A traveling officer must not type the guild’s usual wall-clock time without checking the preview. Ask another member to confirm the displayed event time.

Test: Fill the ten places, verify overflow handling, remove a participant, and check the updated signup. Confirm the reminders and deadline. A signup records intent; it is not evidence of attendance or an in-game clear.

Use the game’s own tools where they fit

ArenaNet’s raid-system guide also introduces native Quickplay, which does not assemble groups by combat role. That is a different experience from an officer-led training roster. Use YourBot to organize your community around the mode you intend to play, not to imply that Discord changes the game’s matchmaking.

5. Group Finder: Make Fractal Groups Understandable at a Glance

Group Finder is useful when a member needs a party, a substitute, or a near-term activity. It also supports a future start; the distinction from Beacon is the workflow, not a ban on scheduling.

Open Group Finder settings and choose #lfg-listings as Listing Channel. Set the staff log destination, a sensible active-listing limit, a cooldown, and an expiry. Suggested starting values are two active listings per member, a 60-second cooldown, and two-hour expiry for near-term groups.

Use experience labels such as Learning, Practice, Clear, Reclear, Chill. Keep these separate from fractal tier or challenge-mode requirements.

Adapt the actual GW2 starter

The GW2 Group (5) starter is a generic five-player template with no predefined role slots. Copy or edit it into templates with a clear purpose:

For a raid vacancy, update the existing event or clearly advertise the missing position; do not create a fresh ten-seat party when nine players are already assembled.

For higher fractals, ask players to check the current in-game Agony Resistance requirement for the selected scale against the build they will use. Listing text is not an automatic gear inspection. Explicitly name challenge mode when intended; “daily fractals” alone is ambiguous.

In the listing, choose the game, activity, NA/EU region, party size, expiry, and joining method. Open confirms a place directly; Request asks the leader to decide. This differs from Require Listing Approval, which concerns staff approval of the listing itself.

Start with local distribution and review any web or sharing surfaces before expanding discovery. Never place private WvW routes, access credentials, or sensitive officer information in a listing.

Test: Create a five-place group, confirm how the leader’s own place is counted, fill the required roles, test leaving and replacement, and close the finished group. Check that an abandoned listing expires.

Make Guild Missions and Open-World Nights Easy to Join

Use Beacon templates for activities that do not need an instanced raid composition. A guild-mission event can use a simple Attending option, an organizer, a meeting point, and a short preparation note.

Guild missions are their own in-game guild system. An officer must check the available mission and required permissions in the game. Discord attendance does not complete an objective or award guild rewards.

For an open-world meta, world-boss outing, or hero-point run, put these details in the event description: game region, map, meeting waypoint, commander, gathering time, activity start, and required map or movement access. Explain whether the group can accommodate someone missing a mount or mastery before they travel.

Treat gathering time and event start as separate. Have someone help late arrivals check the correct map copy. A confirmed Discord place cannot reserve capacity inside a full game map.

Use the in-game squad for subgroup management and ready checks. A large squad should not be squeezed into a small-party listing merely to keep every activity in the same interface.

Plan WvW Separately From PvE

WvW needs a private operational path, not just another public interest channel.

ArenaNet’s WvW Matchmaking guide explains team assignment, the selected WvW guild, registration, and the additional steps for new or inactive players. Direct members to the current guide and in-game timer rather than copying a deadline that will age out of your rules.

Before a rally, ask each participant to confirm their selected WvW guild, current team, and eligibility to join the intended group. Selecting WvW Interest in Discord does none of those things.

An officer grants WvW Cleared after the guild’s checks. Restrict briefing text, operational announcements, and command voice to the approved group. Review access after relevant team changes instead of assuming an old role remains appropriate forever.

Use the commander’s current WvW build guidance rather than reusing the PvE boon roster. Put sensitive meeting details and tactical instructions in restricted Discord channels and in-game communication—not public event descriptions, cross-server listings, or stream feeds.

Keep a basic in-game communication fallback. Neither a bot nor a voice-room label guarantees someone reaches the right team, map, or queue.

6. Join-to-Create Voice: Separate Parties From Command Channels

Open Join-to-Create Voice Channels and connect the lobby and destination category. For small parties, start with:

Where your dashboard exposes Control panel for room owners, it provides an optional panel alongside /voice info. Otherwise, use the room’s native Discord controls. Review the ownership-transfer options your version offers, and grant broader permission-editing powers only when you intend them.

Keep a separate Raid Voice room for planned ten-player content and a staff-controlled WvW Command room. Do not use a broadly accessible party lobby as the entry point to private WvW communications.

YourBot needs permission to create/manage rooms and move members; members need the corresponding visibility and connection access. The voice setup guide is a useful companion.

Test: Create a party room, join with a second member, check owner controls, leave in both orders, and verify cleanup after the final departure. Then test WvW voice with an unrelated Community Member. When a group or event already has an automatically created room, use that room rather than creating a second one through the lobby.

7. Announcements: Publish a Weekly Plan Without Duplicate Pings

Start Your Server can enable Announcements, but an officer creates the actual schedules.

Open Announcements → New Announcement, choose #weekly-plan, and set Timezone explicitly—for example, America/New_York. Pick a weekly recurrence and the intended day and time. The internal label helps staff identify the schedule; the Message field is what members receive.

This week with Wayfarer's Lantern

Fractal introduction: use the Learning template in #lfg-listings.
Saturday raid training: check #raid-signups for the encounter and preparation.
Sunday guild missions: gathering details are in the event post.
Guild hall project: check #guild-projects before contributing materials.

WvW members: read the restricted briefing and check your in-game assignment.

An officer updates that message. A repeating schedule does not automatically compile the latest roster, calculate game resets, or summarize another service’s records.

Let Beacon own its event reminders. Use Announcements for the broader plan and deliberate notices. Avoid a recurring mass ping for information that belongs to an opt-in role.

Test: Schedule a short test in a restricted channel and confirm the content, time zone, recurrence, and allowed mentions before moving it to the public destination.

8. Social Feeds: Subscribe to the Actual GW2 Update Notes

YourBot has a dedicated Guild Wars 2 source in Social Feeds → Add a Feed → Game Patch Catalog. It reads the official Game Update Notes forum, not an arbitrary marketing-news page.

Select the catalog entry and set the destination to #gw2-updates. Start without a ping role. The reviewed adapter uses the official forum RSS feed and a default polling interval of 1,800 seconds, so describe it as periodic checking—not immediate push delivery.

The subscription editor also provides a message template and include/exclude keyword filters. Leave filters empty initially, then narrow them only after checking which useful posts they would suppress. Exclusion keywords take precedence when both sets match.

This public update feed does not need a member’s ArenaNet API key. It also does not verify guild membership, track a character, monitor WvW assignment, or guarantee that every edit to an existing forum topic generates another notification.

Add selected Twitch or YouTube sources separately to #streams-and-videos. Do not expose private raid discussion or WvW plans through recordings or notifications without the relevant participants’ agreement.

Test: Review the saved source, channel, polling setting, and first delivered item. Confirm that ordinary news does not ping the entire guild.

9. Analytics: Measure the Discord, Not a Player’s Loyalty

Open Analytics and review Exclude Bots, display time zone, data retention, and channel exclusions.

For this guild, exclude private application review, sensitive staff discussion, ticket channels, and operational logs from routine community measurements. Review exclusions when new private channels are created; do not assume excluding one old ticket covers future tickets.

After collecting a reasonable baseline, review whether newcomers use the help area, whether party voice rooms are useful, and which discussion channels regularly bring people back. Use alerts to prompt an investigation, not to punish quiet members.

Someone who plays every guild mission may rarely type in Discord. Likewise, time in a voice channel does not prove raid attendance, boon coverage, damage, Agony Resistance, or successful clears. Keep any in-game attendance record separate and clearly identify who confirms it.

Role rewards, when used, should be cosmetic community recognition. Do not grant Officer, Guild Member, or WvW Cleared from message volume.

Test: Compare a short known activity in an included channel with one in an excluded channel. Check dashboard access before sharing reports.

10. Giveaways: Celebrate Without Turning Membership Into a Transaction

Treat Giveaways as an optional social tool, not a raid-loot system or a requirement to remain in the guild.

Create a celebration in #giveaways, describe the actual prize and eligibility, select a duration or start/end dates, and set the number of winners. Verify the time zone shown by the date picker.

For a straightforward guild event, keep booster and role-weight bonuses at zero so eligible participants are not given different odds without an explicit reason. Explain any membership-age restriction before opening entries.

A Discord draw does not deliver gold, items, or unlocks inside GW2. The host must confirm the prize is transferable and arrange fulfillment through an appropriate game or platform workflow. Do not sell entries or tie a drawing to raid selection.

Test: Run a clearly labeled staff-only practice draw, verify eligibility and the winner announcement, and document who fulfills the real prize.

Add a Guild Hall Project Board With Plugin Builder

Guild hall planning is a strong example of a workflow worth specializing after the standard services work.

ArenaNet’s guild hall overview describes contributions to the guild treasury for upgrades. Keep the authoritative in-game state separate from a Discord promise to contribute. A member saying “I can bring these materials” is not the same as the materials having arrived.

First check the marketplace for a suitable maintained plugin. Otherwise, use Plugin Builder to propose a Guild Hall Project Board. This is a suggested custom build, not an existing built-in integration.

Build a Guild Hall Project Board for our Guild Wars 2 Discord.

Officers create projects with a title, purpose, required items, target
quantities, collection instructions, and optional deadline. Members can
pledge quantities, edit their own pledges, or withdraw them.

Track pledged and officer-confirmed received quantities separately.
Only the configured Project Officer role may confirm receipt, correct a
receipt, or close a project. Record who made each change and when.

Provide a public summary showing targets, confirmed progress, and remaining
needs. Keep member-specific contribution details and staff notes restricted
to the configured staff role. Do not rank members by donations.

Add an admin dashboard for projects, items, pledges, confirmations, and
corrections. Store everything separately for each Discord server. Handle
repeated button clicks without duplicate receipts and report missing roles
or channels clearly.

Version one must use manual officer confirmation. Do not request game
passwords or API keys, transfer items or gold, modify the guild treasury,
or claim that pledges are verified in-game deposits. Request only the
Discord and storage capabilities needed for this workflow.

Review the proposed commands, data model, and dashboard before generating the full version. Inspect the source and requested capabilities, run validation, and test an uploaded or committed development version on a managed test server.

Use synthetic pledges first. Test withdrawal, duplicate confirmation, staff corrections, an unauthorized user, and a deleted destination channel. Confirm that the public summary never exposes private notes.

A developer can refine the same plugin through the YourBot SDK. For longer-term distribution, follow the Dev Portal’s version, installation-plan, and publication workflow rather than treating a temporary development install as a permanent release.

A future ArenaNet API integration would be a separate project with explicit permissions, secure key handling, failure behavior, and data-review requirements. ArenaNet’s API guidance explains that keys expose selected gameplay information to third-party applications. They do not belong in public messages, application answers, or ordinary support tickets.

Launch Through Real Member Journeys

Before announcing the server, test the whole journey rather than only whether each settings page saves.

During the first week, run one small activity of each type you intend to keep. Ask participants what was confusing. Remove unnecessary channels and notifications before adding more automation.

For an established guild, preserve existing roles, upcoming events, transcripts, and useful records. Move one workflow at a time and disable duplicate reminders, role grants, and moderation actions. Keep a specialist game-data tool when it still provides something YourBot has not been configured to replace.

Frequently Asked Questions

Can I use this setup without Start Your Server?

Yes. Create the channels and roles manually, enable the relevant services from YourBot’s Plugins page, and follow each service section. The builder shortens the foundation work; it is not a prerequisite for the guild workflows.

Does YourBot verify GW2 accounts or builds automatically?

The setup in this guide does not. Community access, guild membership, combat readiness, and WvW team assignment are different checks. Any automatic verification requires a specifically supported integration, its permissions, and testing.

Should I keep separate raid, fractal, and WvW roles?

Use separate interests and operational access where they solve a real need. A player may want all three activities, but only officers should grant access that represents a checked roster or a private team.

Does YourBot replace Guild Wars 2’s LFG and squad tools?

No. It organizes your Discord community before and around play. Game invitations, instance access, subgroup assignment, ready checks, combat, and rewards remain in the game.

Build the Community Around the Next Thing Members Want to Do

YourBot gives a GW2 guild one place to organize the Discord side of playing together. Start Your Server creates a reviewed foundation. Welcome and Tickets guide arrivals. Beacon and Group Finder organize activities. Voice, Announcements, Social Feeds, Sentinel, Analytics, and optional Giveaways support the community around them.

Start with a usable week: one welcoming introduction, one well-described group, one reliable event, and one clear route to an officer. Then use the marketplace or Plugin Builder for the workflow that genuinely makes your guild different.