Setup and User Guide

What is GuildMesh?

GuildMesh is a connected World of Warcraft guild and community management platform. It combines a web portal, Discord automation, player and character identity, activities, requests, recruitment, community presentation and Community Connections around the same community data.

1. Getting started

GuildMesh Premium

Premium is a community-wide upgrade, not a personal subscription. It adds member progression, raid attendance history, seasonal roster planning, deeper Warcraft Logs analysis and additional community customisation. Premium features are currently available free during Open Beta; communities can also fund Premium time now, which is banked for use when paid Premium becomes active.

Personal progress and attendance

The Personal Progress Hub is designed for ordinary members as well as officers. Raid progression is built from imported Warcraft Logs reports and reflects boss kills the player actually participated in; attendance history reflects GuildMesh raid attendance records rather than Warcraft Logs participation.

Seasonal raid planning

Members register a character, raid specialisation, character type, usual raid-night availability and optional notes. Organisers can set role targets, add or remove players where permitted, lock signups, compare raid-night coverage and review composition, armour types and raid buffs or utility.

After Action Reports and recordings

1. Import a Warcraft Logs report manually, or use Sync now where your configured AAR role permits it.
2. Review the report summary, boss pulls, player performance, deaths and deaths-by-pull timeline.
3. Generate or edit Raid Leader Feedback using the data already stored in the report.
4. If useful, add an external HTTPS POV recording for the entire raid or attach it to a specific stored pull.
5. Publish approved feedback to Discord. Published messages can include Warcraft Logs, analysis and recording-link buttons where available.

GuildMesh stores the recording URL, POV label and report/pull association. The video itself remains hosted by the external provider.

2. Discord permissions and role order

GuildMesh can only post, manage roles or create channels where Discord allows it. A server-wide permission can still be blocked by a category or individual channel override.

3. Signing in and navigation

1. Open GuildMesh and select Continue with Discord.
2. Authorise the requested Discord identity/server access.
3. Select a community.
4. Use the community switcher when you belong to or administer multiple GuildMesh communities.

The community sidebar keeps the current community visible at the top and groups features into Community, Administration, Activities, Requests and GuildMesh. Administration options are permission-aware, so ordinary members are not shown management pages they cannot use. Favourite communities provide a quick-jump menu, while the current-community control can also return you to the main portal.

4. Server Setup and Access & Roles

Open Management → Server Setup. Each module has its own settings for channels, categories, defaults and Discord integration.

Recommended setup order

1. Enable the module.
2. Select its Discord channels/categories.
3. Save the settings.
4. Open Access & Roles and choose which Discord roles can use the relevant management actions.
5. Create or refresh the module's Discord panel where one is available.
6. Test it with a non-admin account before rolling it out widely.

5. Community dashboard and public guild website

The community Overview remains the everyday working home for members and administrators. The public Community Profile is different: it is designed to work as a small guild website that can advertise the community, surface live GuildMesh activity and give prospective members somewhere useful to look before joining Discord.

Public website tabs

• Home: guild identity, About section, community contact, snapshot information, social links, latest news and upcoming public GuildMesh activities.
• News: published community updates. Authorised community administrators can create and remove articles, pin important posts and optionally publish a news embed to a selected Discord channel.
• Events: public GuildMesh raids, Mythic+, LFG and community/Discord events alongside the community's regular schedule information.
• Roster: a searchable, paginated guild roster. When Battle.net guild data is connected, GuildMesh can use the official roster and enrich rows with class/spec, level, rank, portraits or WoW icons, item level and Raider.IO context where available.
• Recruitment: recruitment status, what the community offers, what it is looking for, schedule information and GuildMesh application links.
• Achievements: guild progression and achievement information from configured integrations plus community-written history/highlights.

Battle.net and Raider.IO guild data

Community administrators can connect a WoW guild by region, realm and guild name. Battle.net is used for official guild identity/roster information; Raider.IO remains useful for guild progression and character enrichment. Data is cached in GuildMesh and refreshed deliberately rather than fetched on every public-page view.

Social and external links

Community profiles can link directly to Discord, a website, YouTube, Twitch, Facebook and X/Twitter, alongside WoW-specific destinations such as the WoW Armory, Raider.IO, Warcraft Logs, WoWProgress and Guilds of WoW. Empty links simply do not appear publicly.

6. Player profiles, Battle.net and Raider.IO

Player profiles are a portable GuildMesh identity used throughout raids, Mythic+, LFG, teams, recruitment, messaging and discovery. Discord remains the GuildMesh sign-in identity; Battle.net and Raider.IO are optional WoW integrations that add verification and richer character information.

Build the profile

1. Open Your Profile, select your World of Warcraft region, and complete whichever personal fields you want to display, such as headline, about text, preferred roles, playstyle, availability and what you are looking for. Your selected region keeps realm choices, recruitment and relevant player discovery aligned with the part of WoW you play in.
2. Optionally connect Battle.net. GuildMesh discovers characters on the authorised Battle.net account but does not force the full account roster onto the public profile.
3. Select the characters you actually want to import into GuildMesh.
4. Choose a main character, drag characters into your preferred display order, and choose exactly which characters are public. There is no fixed public-character cap.
5. Use Refresh when you want current character data; imported character data is also refreshed automatically on the normal GuildMesh refresh cycle.

What Battle.net adds

Battle.net is used to verify that the linked account owns a selected character. Verified characters receive a clear Battle.net verification state. Disconnecting Battle.net does not need to delete the GuildMesh character records; verification can be removed while the existing profile data remains.

What Raider.IO adds

Where a character is available on Raider.IO, GuildMesh can enrich the character with portrait, active spec, item level, Mythic+ score, progression context and a Raider.IO profile link. Armory and Raider.IO links are shown where they can be constructed or resolved.

Used throughout GuildMesh

The selected GuildMesh character can follow a player into raid signups, raid composition context, Mythic+ keys and regular teams, LFG listings and recruitment applications. This avoids repeatedly typing character information and gives organisers useful context while keeping Battle.net/Raider.IO calls off the normal page-load path.

Integration requirements and privacy

• Discord: required for GuildMesh sign-in and community access. The bot must be installed with the permissions needed by the modules a community enables.
• Battle.net player connection: optional. The player chooses a Battle.net region, authorises GuildMesh through Blizzard OAuth, then chooses which discovered WoW characters to import. Connecting the account does not automatically publish the full roster.
• Battle.net guild connection: optional and configured by an authorised community administrator. It uses Blizzard's public World of Warcraft guild APIs to synchronise supported guild identity, roster, character and achievement information.
• Raider.IO: optional enrichment. GuildMesh uses supported Raider.IO API data for progression context and links back to Raider.IO where its data is displayed.
• Refreshes: third-party game data is cached and refreshed periodically rather than fetched on every normal page view. This keeps GuildMesh responsive and helps avoid retaining stale game data indefinitely.

7. Raids

Raids supports Discord publication, portal/Discord signups, attendance statuses, recurring raids, automatic signup closing and multiple automated reminders.

Create a raid

1. Open Activities → Raids and select Create Raid.
2. Complete the raid details, date and start time.
3. Configure signup requirements and visibility.
4. Choose Discord publication settings.
5. Under Advanced Options, configure automatic signup closing and recurrence where required.
6. Select one or more automatic reminder timings.
7. Select the reminder channel, or leave it set to the raid signup channel.
8. Save the raid and confirm it appears in the publication queue or Discord as expected.

Attendance

Members can respond through GuildMesh or Discord. Available statuses include Attending, Bench, Late, Tentative and Absent. Raid cards keep the same player-profile layout across attendance groups, and signup changes can be recorded in GuildMesh server logs.

Raid Composition Tool

Raid organisers and authorised raid managers can open Manage raid → Composition tool to turn the signup roster into one or more raid teams. Each raid team starts with five groups; groups always hold a maximum of five players. Organisers can reduce a team to one group or expand it to eight, add additional raid teams, and drag players between groups or back to the Available players pool.

What Auto assign considers

• Hard role targets: Tank and Healer targets are treated as composition constraints; DPS fills the remaining raid places.
• Raid utility: the engine attempts to distribute critical utility such as Bloodlust/Heroism, battle resurrection and major class/raid buffs across raid teams.
• Melee and ranged: damage dealers are spread to avoid unnecessarily lopsided teams.
• Team strength: item level and Raider.IO are used as secondary signals to keep multiple raid teams reasonably balanced.
• Warnings: unmet role targets and missing raid buffs/utility are shown clearly so the organiser knows where the roster is short.
• Manual override: organisers can move any player after Auto assign. Bench, Tentative and Late signups remain available for manual placement rather than being automatically selected.

When the composition is ready, Post composition publishes it to the same Discord channel as the raid signup. The organiser can update the existing Discord composition after making changes or remove the composition post when it is no longer required. Composition changes and Discord post actions are recorded in GuildMesh logs.

8. Mythic+

The Mythic+ module supports individual key listings, temporary voice integration and persistent Mythic+ teams. Premium communities can also organise larger Mythic+ Events, such as a weekly Mythic Monday, with scheduled signups, reminders and a dedicated Team Planner. Current activity also brings eligible connected-community and public key listings into the same working area, with the hosting community identified, so members do not need to browse a separate community-activity page.

List a key

1. Open Activities → Mythic+ or use the configured Discord Mythic+ panel.
2. Enter the dungeon/key details and the roles/spaces required.
3. Publish the listing.
4. Manage signups through Discord or GuildMesh.

Premium Mythic+ Events

Mythic+ Events are designed for larger organised evenings where many players sign up first and the organiser builds the actual five-player key groups afterwards. Creating and managing these events requires community Premium and the configured Mythic+ Events permission; ordinary members can still view and sign up to eligible community, connected or public events created by a Premium community.

1. Open Activities → Mythic+ Events and select Organise event.
2. Enter the event title, description, date/time, signup channel and visibility. Optional advanced settings include scheduled Discord publication, signup closing, reminders and recurring publication.
3. Publish the signup immediately or allow GuildMesh to publish it at the scheduled time. Members choose a character and a role that character's class can actually perform.
4. Open Team Planner when signups are ready. Before Auto assign, groups remain empty and players can be dragged manually.
5. Select Auto assign to build as many useful five-player groups as possible, targeting one Tank, one Healer and three DPS per group. GuildMesh considers Raider.IO, item level, Bloodlust and battle resurrection when balancing otherwise valid groups.
6. Where the signup mix cannot complete a group, Team Planner marks the required PUG Tank, PUG Healer or PUG DPS slots. DPS gaps are preferred over Tank/Healer gaps where the available roster allows it.
7. If only one player remains after forming viable groups, they move into the Matchmaking Queue. Organisers can drag queued players into groups, including swapping an appropriate DPS from a full group back into the Queue.
8. If an assigned player is no longer Attending, GuildMesh moves them to the Queue and promotes the best-fitting attending player of the same role where one is available.
9. Drag players between groups to override the automatic result, then select Post Teams to publish the final groups to Discord.

Quick Voice Channel

The Mythic+ Discord panel can include a Quick Voice Channel button. This creates a temporary voice channel without requiring a key listing first. Created channels appear in GuildMesh Voice Channels and can be controlled from Discord or the portal.

Regular Mythic+ Teams

Create a persistent team profile, advertise open Tank/Healer/DPS positions, search for players, accept join requests and recruit across the guild, connected communities or publicly where enabled.

Team activity and statistics

Team profiles show current roster members, Raider.IO information and GuildMesh key activity statistics based on current team members.

9. Looking for Group

LFG is separate from Mythic+ and is intended for general activities such as dungeons, Timewalking, delves, quests, achievements and other group content. Eligible connected-community and public listings are surfaced alongside local activity with their host community identified.

1. Open Activities → Looking for Group or use the Discord LFG panel.
2. Select the activity and group requirements.
3. Publish the listing to Discord.
4. Manage participants from Discord or GuildMesh.
5. Use Quick Voice Channel if the group needs temporary comms.

10. Events

Events acts as the community calendar and works alongside Discord Scheduled Events. Use it for community/social activities that do not need the specialist Raid, Mythic+ or LFG workflows.

Events created in GuildMesh can be reflected in Discord, and Discord Scheduled Events can appear in the portal where supported.

11. Guild Invite Requests

Guild Invite Requests gives members a structured way to request an in-game World of Warcraft guild invite. When a requester presses I'm online, GuildMesh can ping the configured invite roles so officers know the player is currently available to receive the invite.

Members

Use the configured Discord panel or GuildMesh form and provide the requested character, realm and faction information.

Officers

• Mark a request Attempted when an invite has been attempted.
• Mark it Completed when the invite is successful.
• Close/delete requests that no longer need action.
• Use the generated /ginvite Character-Realm information where shown.

12. Crafting Requests

Crafting Requests connects members to relevant crafters without needing to ping every crafter in the community.

Administrator setup

1. Enable Crafting Requests.
2. Select its Discord panel/request channel.
3. Map professions to Discord roles, for example Inscription → @Inscription.
4. Save the settings and create/refresh the panel.

Submitting a request

Select the profession, requested quality and details. Where useful, include an item screenshot/image URL. GuildMesh can then notify only the mapped profession role.

Crafters can claim and complete requests, while members can track the request state in GuildMesh.

13. Support Tickets

Support Tickets creates private Discord ticket channels while keeping a GuildMesh history for the requester and authorised responders.

Setup

• Select the Discord ticket panel channel.
• Select an optional ticket category, or leave it blank where top-level ticket channels are preferred.
• Select responder roles.
• Create/refresh the ticket panel.

Managing tickets

Responders can claim/release tickets, reply in Discord and close tickets. Ticket transcripts are retained in GuildMesh for audit purposes from the point message capture is active.

Members can view their own current and previous tickets. Full server ticket history remains restricted to authorised responders/admins.

14. Recruitment

Communities can advertise that they are recruiting and appear in the GuildMesh Recruitment Directory. Public community profiles can provide recruitment information, Discord links and application options where configured.

Recruitment Applications are separate from Guild Invite Requests: recruitment is about joining the community; Guild Invite Requests are for an in-game invite after membership is appropriate.

15. Giveaways

Authorised organisers can run Discord giveaways through GuildMesh.

• Create the prize, description, closing time and number of winners.
• Publish the giveaway to Discord.
• End it to choose winner(s) or reroll where supported.
• Organisers can delete an active giveaway without ending it when required.
• Previous giveaways and winners remain visible in GuildMesh history for transparency.

16. Temporary Voice Channels

Temporary voice channels can be created directly or from Mythic+/LFG Discord panels.

The channel creator and authorised administrators can rename the channel, remove connected users, set or change the player limit, lock/unlock and delete the channel. The same channel appears in the GuildMesh Voice Channels page.

17. Scheduled Messages

Scheduled Messages is for general recurring or timed Discord messages. It is separate from Raid-specific automatic reminders.

Configure the destination channel, message, repeat schedule and supported mentions/emoji. Use the send-now control when you need an immediate post.

18. Welcome & Leave

Welcome and Leave messages are independently configurable.

Welcome options

• Enable/disable welcome messages.
• Select the welcome channel and customise the text.
• Reference useful Discord channels in the message.
• Automatically assign selected roles to new members.
• Optionally delete the welcome post after a configured period.
• Configure optional welcome DMs where available.

Leave options

• Enable/disable leave announcements independently.
• Select a separate leave channel.
• Customise the leave message and optional DM.

The Welcome page also shows recent joins and links to GuildMesh player profiles where available.

19. Server Logs

GuildMesh can record Discord and GuildMesh activity for authorised administrators and log viewers.

Configure logging

Only server administrators can enable/disable logging and choose which event types are recorded. Detailed settings allow categories such as moderation, messages, channels, roles, members, voice, invites, emoji/stickers, server changes and GuildMesh activity.

View logs

The Logs page is the searchable history. Log Viewer roles can be given read-only access without granting permission to alter logging settings. Entries use readable Discord user/channel names in the main summary where available, while IDs remain available in the detailed metadata. Log cards are collapsed by default and can be opened for fuller information about what happened, who performed the action, the affected channel/target and timestamps. Administrators can choose how many logs to show per page and move through the history using pagination.

20. Community Connections and activity discovery

GuildMesh can connect communities without forcing every connected community into one shared group.

Community Connections

Authorised administrators can search for communities, propose a connection, accept/decline proposals and end connections where appropriate. Community Connections now sits in the GuildMesh section of the community sidebar.

Connected and public activity inside modules

Within a community, eligible connected-community and public raids, Mythic+ keys and LFG listings are surfaced directly in their respective activity modules. Listings identify the hosting community and link to its profile where appropriate. This keeps the normal raid/key/group workflow in one place instead of requiring separate Community Activities navigation.

Portal Public Activities

The main portal retains a Public Activities page for discovering activities deliberately opened beyond connected communities, including for GuildMesh users who are not members of the hosting Discord. Check activity requirements, region and eligibility before joining.

21. Notifications and Messages

The top bar provides quick access to notifications and direct messages. The full Notifications page keeps notification history and can be filtered by category or unread status. Where Discord notifications are enabled for the account, GuildMesh can also send a brief Discord DM for new portal messages and supported notifications, with a link back to GuildMesh.

GuildMesh messaging is subject to the recipient's messaging preference. Use it for relevant player/community contact.

22. Troubleshooting

GuildMesh cannot post to a channel

Check the channel still exists and that GuildMesh can view it, send messages and embed links. Check category/channel permission overrides.

A Discord panel is missing a new button

Open Server Setup and use the module's Create/Refresh Panel control.

A temporary channel cannot be created

Check the configured category and GuildMesh's Manage Channels, View Channel, Connect and Move Members permissions.

An administration page is hidden

Confirm the account has the required Discord server permission or a GuildMesh role configured under Access & Roles.

Discord and GuildMesh show different information

Refresh both, then use the module's refresh/repost control where available. Report persistent mismatches with the community name, module/listing and approximate time.

A scheduled action has not fired

Check whether the displayed time is UTC or local time before assuming it is overdue. Include both scheduled and local times when reporting scheduler issues.

23. Support and Beta feedback

For setup help, bug reports and feature suggestions, join the GuildMesh Discord Server.

Beta feedback directly shapes GuildMesh. Small usability issues are worth reporting as well as major bugs.