DOCUMENTATION
Documentation
Guild Master – Free Guild & Community Manager for MMO Games. Events, attendance, loot and Discord in one place, across every supported game.
What is Guild Master?
A quick look at everything you can do with Guild Master.
For everyone: newcomers, Guild leaders and streamers who want to introduce us.
All of your management in one app
Guild Master takes the whole load of running a Guild and a Community into one app. Run your Guilds, Community and Alliances smoothly in every supported MMO, without juggling spreadsheets, bots and Discord channels.
From events to loot, all in one place
Plan events and sieges with character-based sign-ups, build party compositions, take attendance and track attendance points automatically. Hand out loot fairly by Council, roll or auction.
Built around Discord
Applications, event cards, reminders and loot calls arrive in Discord as messages, so your members answer where they already talk. Role sync, welcome messages and streamer alerts are ready too.
Run it as a team
Define roles and Guild titles, and give each officer permissions only in the games and Guilds they need. The setup assistant guides you from the first steps.
Easy for players too
Manage your characters in every game from one profile, find a Guild that fits you in Discovery, and browse game data in Forge without signing in.
Always growing
New games and features are added regularly. Suggest the game you play, and support Guild Master by sharing it with friends or going Premium. Every feature is free; Premium opens room for more games and Guilds for bigger groups.
Getting started
Find your way from your first sign-in to your first organized Event.
For new members and Community organizers.
Understand the building blocks
Player is your account. A Character is an identity you play in a game; some games use a Family with several character profiles instead.
A Community brings people and games together. A Guild belongs to one Community and one game. An Alliance connects Communities for a particular game without merging their members or permissions.
For example, one Community can organize an Aion 2 Guild and an Albion Online Guild. An Aion 2 Alliance lets that Community coordinate with other Communities in that game.
Join an existing group
- Open Discovery and find your Community or Guild, or open the application or invitation link shared by an organizer.
- Sign in using the Discord account you want to use. Browsing a public profile does not make you a member.
- For a Guild application, select or create a suitable Character and complete the requested questions. A direct Community application does not require a Character.
- Submit and track the result. An application requires acceptance; a Community invitation requires your explicit acceptance.
A Discord server invitation, a Community invitation and a Guild application link serve different purposes. Joining a Discord server alone does not join the application Community.
Open Getting started beside the Dashboard greeting for Character, Guild discovery and pending application shortcuts. It is optional and never interrupts an invitation. Hide it on Dashboard or reopen it from your account menu. A data error is shown separately from an empty account.
Set up your own group
- Sign in and choose Create Guild from Dashboard or My Guilds.
- Use the new Community option, or select an existing Community where you have permission to create Guilds.
- Choose the game and complete the profile. A founder Character is optional. Review the summary before creating the Guild.
- Open the resulting Community and Guild to review access, applications and invitations.
- Connect Discord from Community settings if you want bot features, then create your first Event.
You can also start with a Community from My Communities. A game and a Discord server are not required to create one.
Select the green Setup button at the right end of the row above every page, next to the breadcrumb, or open it from the account menu. The Setup assistant lists the core steps of the Community, Guild or Alliance you are on (or the one you pick) plus your personal steps. Steps complete from your data; confirm Review your preferences with Mark done. More options lists that resource's optional settings: profile images, permissions, Discord channels, Events and loot. Select a row to open its setting, or the small question mark to read the relevant guide. Private profiles, closed applications and disabled integrations are valid choices.
Free features and plan limits
Every feature is free. Members and Events are unlimited on every plan; plans differ only in capacity, such as active games, Guilds per game and other resource limits.
Players never need a plan. A Community that plays one game stays on Free. When it moves to a new game, deactivate the old one and activate the new one; nothing is deleted. Premium is for a Community that runs several games at the same time or needs more Guilds in one game. Premium applies to the Community it is assigned to, and only one of your Free Communities can be active at a time. The Plans page compares Free and Premium rights from the live plan catalog; your Community shows its current usage and limits.
Inactive resources can retain history and allow permitted reading, while new operations may be unavailable. Read the activation or deactivation preview before confirming a change.
Communities
Create a shared home for your people, games and Guilds.
For Community Owners, authorized managers and members.
Create and configure a Community
- Open My Communities and choose the create action.
- Enter the name, address, introduction and language preferences. Review public visibility and the application intake.
- Create the Community. Your account becomes its Owner and an active member.
- Open General settings to maintain its profile. Add presentation images through the available media settings after creation.
A Community is independent of Discord. Its application name and profile are not overwritten by a Discord server rename. FREE ownership and capacity checks apply when creating or activating resources. If your FREE allowance is already in use, the create screen shows which Community uses it and links to Plans instead of opening the form.
Invite, apply and manage membership
A Community invitation grants normal Community membership after the recipient accepts. It does not grant Guild membership, a management role or ownership.
Members can use My Communities → My applications & invitations to enter a code, accept a valid invitation and review their own Community applications. A direct application contains an optional message and waits for an authorized decision.
Managers use Applications to review applications and manage invitations according to their permissions. Invitation expiry and usage limits still apply when the recipient accepts. Rejected applications are not bans.
Organize games, Guilds and access
Use the Community game and Guild management sections to work with its game-specific groups. Creating a Guild in an existing Community requires the corresponding create permission.
Use Community roles to delegate only the required operations and Guild scope. Membership alone does not grant management access. See Roles and permissions.
A private Community makes its Guilds private for visitors without changing their own choice. When the Community becomes public again, each Guild returns to its own choice.
Publish announcements
Announcements are on the Community Overview, right after At a glance. Only members read them there; the public profile shows no announcements. Double-click a row to open it. Notifications for new announcements open the same view.
With the Event management permission, use New announcement, or Edit and Delete in the row menu. The text supports Discord Markdown: bold, italic, underline, strike, # headings, - lists and > quotes. The preview shows the result and warns when Discord needs more than one message.
To also post to Discord, choose a channel in Settings → Discord settings → General channels → Community announcements. Editing replaces the Discord message; deleting removes it from Discord too. Use Send to Discord again after changing the channel. While that channel is on, Roles to ping in the editor lets you pick any server roles, @everyone or @here; only these ping, again on every edit or resend. Mentions typed into the text never ping.
With a connected Discord server, Also create a Discord event adds the announcement to the server's Events list on a voice or Stage channel at the start time you choose; members can mark it Interested there, which is not an RSVP. Guild Master stays the source: edits update the Discord event and deleting the announcement deletes it. If someone changes or deletes it in Discord, the announcement shows Changed in Discord or Deleted in Discord; Sync writes it back.
Ownership and resource changes
Only the current Owner can transfer Community ownership. The selected recipient must be an eligible active member. Confirming completes the transfer directly; it does not wait for a separate acceptance. Discord server ownership is unaffected.
The Owner must transfer ownership before leaving. Leaving a Guild does not mean leaving its Community. Leaving or being removed from a Community can end its scoped Guild memberships and access.
Review capacity and the full impact preview before deactivating or deleting a resource. Deletion belongs in the resource’s Danger Zone; it is not a way to hide a public profile temporarily.
For a Guild, the Owner can open Guild settings → Danger Zone to review deactivation. Permanent deletion remains a separate action. Community controls remain in the Community settings.
Guilds and applications
Build a Guild, accept Character applications and review them.
For applicants, Guild organizers and authorized reviewers.
Create a Guild
- Choose Create Guild from Dashboard or My Guilds. The wizard starts with a new Community option.
- For an existing Community, select one where you can create Guilds. A Community management entry already knows its parent.
- Complete identity and optional logo, game/region and applicable faction/server fields, profile and optional Prime Time.
- Optionally select a suitable founder Character or create one in the wizard. Review and create.
The founder must be your active Character in the game and must not already belong to a Guild. Skipping the founder is allowed. Prime Time describes your schedule; it does not create Events.
Region is optional. If the game has no active regions, the field is hidden. Select a Region before choosing a Server; clearing or changing Region clears Server. A Guild without a Region does not require a Region match when joining.
Apply to a Guild
- Open a Guild accepting applications in Discovery or use its application/invitation link.
- Sign in, then select or create a Character for the Guild’s game. Complete any missing required profile fields.
- Answer the enabled questions, review the summary and submit. Creating the Character alone does not send the application.
- Review the result in that Character’s Applications. You can withdraw your own pending application.
Some Communities require the same Discord account to join their linked server before submission. Use the application screen’s join and check controls. Server membership alone is not an accepted Guild application.
Review applications and invitations
Authorized reviewers open the Guild’s Applications management page, inspect the submitted Character/profile and answers, then Accept or Reject. Read and review permissions are separate; invitation management is another permission.
The saved answers reflect the questions shown to the applicant. Later question changes do not rewrite an existing submission. Acceptance checks the current Character, membership and Community rules again.
A Guild invitation/application code is an entry to the application flow, not an automatic acceptance. Keep its expiry, usage limit and target Guild in mind when sharing it.
Membership and leadership
Guild membership belongs to a character; one account can have several characters. Accepting a Guild application also creates a missing Community membership when allowed.
Define titles such as Guild leader or advisor with Manage titles in Guild → Members and give them with Give title. Guild permissions (settings, members, events, loot, points) can be attached to a title; its holder uses them in that Guild only, and loses them with the title.
A new Guild starts without titles. Whoever creates a Guild holds every Guild permission in it for as long as they keep the Guild creation permission.
Characters and play profiles
Represent the identities and builds you actually play.
For players creating Characters and applying or responding to Events.
Create a Character
- Open My Characters and choose the create action.
- Select the game and complete the fields it asks for. Available classes, specializations and other choices depend on that game.
- Complete the applicable play profile and review before saving.
- Open the Character to maintain its details and start or review applications.
Game requirements and a Community’s Character policy can differ. An existing Character may need additional details before a particular Guild accepts an application.
Understand roots, profiles and Families
A Character can have one or more play profiles when its game supports them. They describe alternative ways to play the same identity; they are not extra Guild members.
Black Desert Online uses a Family as the root, with named Characters inside it as profiles. The Family is the participation unit; selecting a different profile does not create another attendance or points account.
Game-specific identity rules apply to combinations such as class/spec or weapon choices. When you change a parent choice, review any dependent fields that need to be selected again.
Link your in-game character
In games with an official character source (today AION 2), you can link a Character to your character in the game: in the creation wizard's optional In-game character step, in the Character's Profile, or with This is my character on its Forge Armory page.
- Name, class, region, server, faction, item level and combat power then come from the game. They update once a day and when the Armory page is opened, at most every ten minutes; Update now on the Profile reads them on demand.
- While linked, these fields cannot be edited. Party roles and the build link stay yours.
- A linked Character keeps a daily history of its combat power and item level, shown as Power progress on its Armory page.
- Unlink stops the updates and makes the fields editable again; the history stays and continues if you link again.
- If the game no longer finds the character for several days (for example after a server transfer), the Profile asks you to link it again.
- Linked characters appear in the Armory rankings (strongest and this week's climbers) and, while the Guild relation is public, on their public Guild's Armory page (Legion in AION 2) with the Guild's combined power. A character counts once, even if several players linked it.
Anyone can search the Armory without signing in. A character that nobody linked is shown live from the game and is not stored.
Choose the profile for an Event
For a game Event, respond using an eligible Character or Family. If several roots are eligible, each has its own response. Select the profile you will play and any available declared roles.
The Event profile does not change your personal default profile. Class and declared roles are distinct; adding roles does not add participants. A gear check may ask you to confirm the selected profile’s applicable measurements.
Visibility and archiving
Your account Profile contains public visibility preferences. A public Character profile is a limited identity page, not a publication of every game field or private Guild detail.
Archiving is different from permanent deletion. Use the Character’s Danger Zone and read the impact shown before confirming. An archived Character must meet current requirements to return; old memberships and participations should not be assumed to resume automatically.
Roles and permissions
Give managers the access they need within the right Community and Guilds.
For Community Owners, role managers and people missing an action.
Three different kinds of role
- Community panel roles give a member permissions; an assignment applies Community-wide, to one game, or to selected Guilds of one game.
- Guild titles (such as Guild leader or advisor) are the Guild's own; Guild permissions attached to a title are given to its holder in that Guild only.
- Discord roles manage information and server access in Discord.
A Discord role grants no panel permission. Guild Master can mirror selected game/Guild information to Discord roles; it never imports native Discord roles as panel access.
Delegate management
The Community Owner holds every permission. A member with Roles and assignments can give only permissions they hold, in a scope no wider than their own.
- Open Community → Settings → Roles & permissions.
- Create a role and choose its permissions; Community, game and Guild permissions are in separate groups.
- With Assign a panel role, pick the person and the role, then choose where it applies: Community-wide, one game, or selected Guilds of one game. Permissions that do not work in the chosen scope are struck out in the summary.
- Guild managers can give a member a role in their Guild only with Grant permissions in the Guild → Members row.
Don't give broad permissions to cover one missing action. Creating a role assigns nothing.
Respect operation and scope boundaries
Viewing an Event does not grant attendance management. Managing an Event does not grant access to another Community’s private roster or points.
Discord channel delivery, role synchronization, application review and point adjustments can require different permissions. Alliance tasks do not merge the participating Communities’ management access.
Membership or assignment changes take effect in current access checks. If access changes while a form is open, an action can be rejected even though the old screen still shows it.
Resolve missing access
Check your account, active Community membership, the selected Guild and assigned role. Ask the Owner or role manager to verify the specific operation and scope.
If the page reports that its data changed, refresh and review again. Do not assume an old browser tab still reflects current permissions. For Discord role problems, check server configuration separately.
Discord integration
Connect a server, choose delivery channels and synchronize selected roles.
For Community Owners, Discord administrators and authorized integration managers.
Link the Community to Discord
- Open Community → Settings → Discord with the required connection permission.
- Start the connection/setup action and complete Discord’s authorization for the intended server.
- Review the linked server and its health in Guild Master.
- Configure the delivery and role features you actually want to use.
Signing in with Discord or inviting the bot by itself does not link a Community. Application ownership and memberships remain in Guild Master. Unlinking/reconnecting should be reviewed carefully because old channel and role settings are not automatically reused for a new connection. If the server is already linked to another Community, only the Discord server owner can move it: after Discord's authorization Guild Master asks for confirmation, the other Community loses only its connection and its owner is notified.
Check bot access and hierarchy
The current installation flow requests Administrator for the bot. Even with Administrator, Discord role hierarchy still applies: the bot’s highest role must be above roles it manages, and integration-managed roles cannot be managed as ordinary roles.
Use Guild Master’s health/status checks and Discord’s role list when investigating failures. Generated roles start without server permissions; a Discord administrator configures their channel access separately.
Do not replace a missing role by giving a similarly named native role and expecting Guild Master to adopt it. Only its recorded generated roles are synchronized.
Enable role synchronization
Open Community → Settings → Discord → Discord Member Role Sync. The Owner or a member with role synchronization management permission can configure it. This module is independent of Welcome, Goodbye, Role Changes and Streamers.
- Turn on Game roles and/or Guild roles and choose Save. Saving starts the sync; there is no separate first sync.
- Guild Master creates one role per active game of the Community and one per active Guild, and gives each to the members it belongs to. Class, Spec and leadership titles stay in Guild Master.
- Application changes, a daily check and the bot's reconnection keep the roles up to date. Sync now runs it at once.
The roles are informational: Guild Master only manages their name and who holds them. Permissions, channel access, color and position are yours to set in Discord and are never changed. A name changed in Discord returns to the Guild Master name; a role deleted in Discord is created again with a new identity, without its old permissions.
The roles of an inactive game or Guild are left as they are. A deleted Guild's role is removed from Discord. Turning the switches off stops the sync and deletes nothing. Game roles are only given, never removed: people outside Guild Master, former members and anyone who got the role through onboarding keep it. Guild roles are removed from people who no longer belong to the Guild.
Choose channels for messages
The Channel settings card is the central place for delivery. General rows include Community Events and Community applications. Choose a game to configure its Event, party composition, Alliance and Guild-specific rows; the game's Event class display sits at the top of that card. Every channel picker has a search box. The Streamer channel row receives the announcements of all streamers.
Enable the required row, select an eligible channel and choose Save changes. Refresh channels reloads choices without saving your draft. Guild application and Loot & Rewards rows belong to individual Guilds.
Application review can use any text channel where the bot can view the channel, send messages, embed links and read message history; it does not need to be private. Who can see the channel is your server's choice: submitted answers are visible to everyone who can read it. Selecting a delivery channel does not grant review permission to its readers. Guild and Community application rows also have Roles to ping: up to 5 server roles that new application messages ping (never @everyone or @here).
Party composition is sent manually from its own screen. Enabling new application or loot delivery does not backfill all old records.
To have channels created for you, open Community → Settings → Discord → Open channel templates, or choose Create for me in the Setup assistant. Compact puts every channel in one "Guild Master" category shared by all games; By game adds a general category plus one category per game, named after the game, with channels prefixed by the game's slug. The preview shows each channel and the settings it serves; you can switch off any empty or deleted setting. Create channels creates the missing categories and channels once with the server's default permissions and links them. Linked settings are never changed; running it again only fills what is missing, such as a newly added game. Channels are remembered by id, never matched by name, and every channel can still be changed later in the settings, even per Guild.
Choose independent modules
Open Community → Settings → Discord → Automations. Welcome, Goodbye, Role Changes and Streamers each have their own switch, initially off. Role synchronization is configured separately on the Discord page. These modules do not require each other.
The Community Owner can manage them. Other members need automation viewing permission to read settings and automation management permission to save, preview or test them. Linking Discord and managing role synchronization use separate permissions.
Welcome, Goodbye and Role Changes each have their own text channel and plain Markdown template. Save before using Test saved template; a test can send to the saved channel even while the module is off, but never notifies mentions. Check the result in Discord delivery history. Actual user/role mentions attempt to notify; @everyone and @here are unsupported in these three modules.
The rendered message must fit 2,000 characters. Welcome and Goodbye support {user.mention}, {user.username}, {member.displayName}, {guild.name} and {guild.member_count}; channel references and URLs can also be inserted. Starter templates are English and can be edited in any language.
Welcome / Goodbye / Role Changes: A linked server, bot access and member-event availability are required. Initial scans and reconnects are silent: missed changes are not announced in bulk. Replacing the Discord connection does not reuse old channel/role selections.
Settings load automatically when the page opens; there is no separate automation refresh button. Variable selectors show literal keys.
Welcome: greet new Discord members
Enable Welcome in Automations, choose its text channel, edit the template and save. It greets new joins to the linked Discord server, including people without a Guild Master account. It never creates Community membership. Existing members are not greeted during initial scanning.
Display name uses the server nickname, then the global name, then the username.
Goodbye: announce Discord departures
Enable Goodbye independently, choose its own text channel and save its template. It announces departures using the last known display name; a departure is not proof of a kick or ban. Leaving Discord does not end application membership.
Role Changes: report role additions and removals
Enable Role Changes independently and save its channel/template. It observes changes by Discord administrators, other bots and Guild Master. It sends messages only; it does not assign roles or grant panel access.
Additional variables are {actor.mention}, {roles.added} and {roles.removed}. The actor appears only with clear audit evidence; missing actor/empty-list lines are hidden. Role names are plain text. This module is separate from role synchronization.
There is no role filter or separate Activity page; results use Discord delivery history.
Streamers: Twitch and Kick live alerts
Open Community → Streamers, select Twitch or Kick and add a channel URL or username. Configure its message, one notification target and active state. Announcements of all streamers go to one channel: choose the Streamer channel row under Settings → Discord → General channels. Without it, nothing is posted and the delivery history shows that no channel is selected; tracking continues. Then enable Streamers under Settings → Discord → Automations. Both switches must be on; no game or Guild selection is needed. Automation viewing/management permissions apply.
FREE allows 10 Twitch records and separately 10 Kick records per Community, including inactive records. The current PAID entitlement has no product record limit; provider capacity still applies. Paid checkout is not available yet. Returning to FREE preserves records; if one platform exceeds 10 active records, its automatic alerts pause until the excess is deactivated.
Choose No mention, @everyone, @here or one Discord role as the notification target; other inline mentions do not notify. Test saved message never sends mention notifications. Newly added channels already live are announced only with Announce now. Future live starts post a message with a stream card and watch link; the message is not changed when the stream ends. A streamer needs no Guild Master account or separate OAuth connection. Check delivery history if nothing arrives; the selected provider must be available.
The stream card shows, in the platform colour, the title, category, start time and the stream image captured when it went live; the link buttons are under it and your message above it supports Markdown and emoji. Tests use real live metadata when available, otherwise sample data.
Check delivery and direct messages
Open delivery history from Community Discord settings to inspect pending, sent, failed or uncertain deliveries within your permissions. Check the exact channel, bot access and current connection before retrying.
An uncertain delivery may already have sent a message. Read the retry confirmation; repeated retries can duplicate an external message. A Discord failure does not undo a successful application, Event response or other panel change.
Personal notification DMs can be disabled in Profile → Notifications → Discord direct messages. Web notifications continue. Discord must also allow DMs from the bot and share a server with it.
Events and RSVP
Schedule a gathering and let members respond from the panel or Discord.
For members and authorized Event organizers.
Choose the right Event
A game Event targets all or selected Guilds in a Community and uses eligible Characters/Families. It can support game measurements, attendance points and Alliance coordination.
A Community Event without a game targets Community members and uses their accounts. It does not have Character selection, game gear checks, party composition or attendance points.
The combined Dashboard and calendars show both types. A public Guild profile does not make its internal Event details public.
Create and publish
- Open Events in the relevant Community or Guild and choose the create action, if permitted.
- Select the Event type and target Guilds for a game Event; enter the title, description, start time, duration and registration closing time.
- Review any attendance reward and recommended measurements copied from the type. They can be changed for this Event without changing the type default.
- Save a draft or publish when ready. Review a game Event’s repetition settings if you want a recurring series.
- Optionally enable a Discord reminder. A game Event's channel is set in Community → Settings → Game settings → Discord modules; a Community meeting's channel in Discord settings.
Times use your profile time zone. The reminder is optional and separate from the main Event message. An already published Event can become active and complete with its scheduled lifecycle.
Respond and select your profile
Open the Event and choose Attending, Maybe or Not attending. An eligible game Character/Family has its own response; a no-game Event has one response for your account.
For game Events, use Edit event profile to choose the profile you will play and any available declared roles. Maybe/Not attending can include an optional reason. A gear check may ask for selected profile measurements before Attending can be saved.
The registration deadline and current membership are checked when you respond. Changing an Event profile does not change your default Character profile. Roles and alternate profiles do not create extra participation units.
Respond in Discord
Use the current Event message’s response buttons with the same Discord identity as your Guild Master account. If you have multiple eligible Characters, follow the Character/profile selection presented by the bot. If none of your Characters is in a target Guild, the bot's private reply lists each target Guild's application link.
Use Open in panel for the full Event and roster. Discord has message size limits, so a long roster can be shortened in the message while the panel retains the full allowed list.
If a button reports an old message, closed registration or missing membership, open the current panel Event. A bot response is subject to the same membership and timing rules as the panel.
Example: organize your first raid
- Publish a game Event with the intended Guilds and start time.
- Members respond with their Characters and intended play profiles.
- Prepare and explicitly send the party composition if needed.
- Record actual attendance during the Event, using the permitted manual, code or Discord voice workflow.
- After completion, review and confirm each Guild’s attendance scope.
Attending is an intention, not confirmed attendance. Attendance and points are separate operations. See Attendance and points before finalizing.
Attendance and points
Record what happened and understand how balances change.
For participants, attendance managers and authorized points managers.
Separate response from attendance
RSVP says what a participant plans to do. Present, Absent and Unmarked record actual attendance. Setting Attending, moving someone into a party or completing a check-in does not directly award points.
Game attendance belongs to the historical Guild membership represented at the Event. A Family counts once; its profiles do not each earn a reward. A no-game Community Event has account attendance and no attendance points.
Record attendance
Authorized managers use the Event’s participants/attendance table and permitted row or bulk actions. Bulk selection applies to the current manageable page; review the selected scope before applying a change.
During an active Event, an authorized manager can generate a temporary check-in code and share it with participants. Members use Check in with a code in the panel or /checkin <code> in Discord, and choose the Character/Family when they have more than one. Codes expire and can be revoked; an existing manual Absent decision needs manager correction.
Discord Attendance Check in the panel, or /checkin_control <code> in Discord, lists every voice or Stage room of the linked server that holds someone who can attend. Pick people one by one or use Select all per room, then Mark Present; people with more than one chosen character are asked once more which one they played. It only works within the acting Community’s permitted scope, and people who are not selected are not marked Absent.
Confirm or correct attendance
- Wait until the Event is completed, then open the permitted Guild attendance scope. A no-game Event uses its Community scope.
- Review the confirmation preview for the full scope, including records outside the current table filter/page.
- Confirm only after checking Present, Absent and Unmarked counts and any reward totals. Remaining Unmarked records become Absent, and the scope locks.
- To correct a confirmed scope, use the separately authorized reopen action, provide a reason, review the points impact, correct attendance and confirm again.
An Alliance does not grant one Community permission to finalize another’s private Guild attendance.
Read and manage points
A completed game Event awards its configured reward to eligible Present roots when their Guild attendance is confirmed. A zero reward records confirmation without adding points. Reopening reverses the previous awarded amounts before a later confirmation can award again.
Your active Guild balance and recent activity appear on Character Overview; authorized Guild points screens provide the relevant account and history. Joining again creates a new membership account rather than reviving an old balance.
Authorized managers can award or adjust points with a reason and a before/after preview. Viewing balances, changing them and reversing source rewards are separate permissions. Already spent rewards can lead to a negative balance when a source award is reversed.
Understand point decay
Open Guild → Settings → General → Attendance Points to read or manage this Guild’s decay. The Settings button beside each Guild on the Community's Games page opens the same page. Viewing points does not grant permission to save decay changes.
Point decay is a Guild setting, separate from the Community’s display name for points. Its manager chooses a percentage and interval; zero percent stops future decay scheduling.
For example, with 10% weekly decay and no other movements, a positive balance of 100.00 becomes 90.00, then 81.00 at the next due dates. Zero and negative balances are not reduced.
Use How does it work? beside the Guild setting for the exact scheduling and rounding examples. Review the displayed next due date after changing the rate or interval. If overdue decay blocks an operation, refresh after processing rather than repeatedly submitting a new adjustment.
Party composition
Prepare a reusable party layout or organize an Event roster.
For managers with Community party composition permission.
Understand who can use it
Party composition organizes eligible roots into named parties. It is informational: it does not write RSVP, attendance or points, and does not enforce game party sizes or role slot requirements.
The current view is for authorized composition managers. Being an Event organizer, Guild leader or Alliance member does not by itself grant access. In an Alliance Event, each Community manages its own targeted Guild members.
Prepare a fixed layout
Open the Community’s Party Composition section and select the game, or enter from a Guild for its game and initial member filter.
Move active members into parties by drag and drop or the row menu. Rename parties, adjust the order and choose leaders as needed. Each non-empty party has one leader; removing that leader promotes the next member.
Save the layout. A new Event composition can start from this fixed arrangement; editing a fixed layout is not a command to overwrite existing Event compositions.
Arrange an Event roster
Open the game Event’s composition with the required Community permission. If necessary, select the acting Community.
- Place eligible members using drag and drop or Move to party.
- Use Make leader or Remove where needed.
- Resolve highlighted Not attending members before saving. A saved member who later responds Not attending is removed from the composition.
- Choose Save. Review any refresh/conflict feedback if another manager changed the arrangement.
Each root appears in at most one party. Alternative profiles and declared roles do not create extra placements. Completed or canceled Event compositions are read-only.
Send the saved composition to Discord
Configure the game's Party composition channel in Game settings → Discord modules first; each game has its own. Its configuration permission is separate from composition management.
Choose Send to Discord from the composition screen after saving. Save does not send a message. A later Send updates the recorded message; Remove from Discord removes messages while retaining the panel composition.
In an Alliance, each Community sends only its own roster to its own configured channel. Discord delivery failure does not undo the saved party arrangement.
Loot & Rewards
Track drops, participation, decisions and delivery.
For Guild members and authorized loot managers.
Create a drop
Authorized managers use the Guild’s Loot & Rewards area to create a drop from an available item. Choose Council, Roll or Auction explicitly for each new drop and review the fields that method requires.
A drop can progress from Open to Assigned to Delivered, or be Canceled. Roll/Auction can also close without a winner. Guild Master records allocation and delivery; it does not transfer an item inside the game.
The item description is retained with the drop. Editing the item catalog later does not rewrite that recorded description.
Council: record interest and a decision
An eligible active Guild root can choose Interested or withdraw its interest. The manager reviews candidates and assigns the item with a reason.
A Council award is free by default. The manager may choose a positive point cost; the confirmation shows the recipient and resulting balance and requires sufficient available points. Free awards do not require a positive balance.
After giving the item in the game, the manager confirms Delivered. Marking delivery does not charge a second time. Reassignment or cancellation requires a reason and follows the applicable refund/charge preview.
Roll: Need, Greed or Pass
Choose Need, Greed or Pass before the deadline. You can change your answer while the round remains open. Family profiles do not each get another response.
At closure, eligible Need responders roll first; if there are none, eligible Greed responders roll. Pass does not compete. The server rolls 1–100 and rerolls tied highest results among the tied participants.
Roll awards cost no points. If there is no eligible winner, the drop closes without one; a manager may open a new round. The rules do not apply class or main/alt priority automatically.
Auction: bid with available points
The drop shows the highest bid and next minimum. Open Place bid, check your balance and points already reserved in other auctions, and review before submitting. You bid for your own eligible root; accepted bids cannot be withdrawn.
The leading bid reserves points while the auction remains open. Being outbid releases that reservation. At closure, an eligible winner pays their own highest bid once.
Late accepted bids can extend the deadline within its allowed extension budget. If the leading participant is no longer eligible or cannot cover the cost at closure, the result can be Closed without a winner; the system does not automatically charge an earlier bidder.
Read results, history and Discord messages
Use the detail view selector for participants and the decision, roll or bid histories your permissions allow. Different views may require broader read access than your own participation controls.
Discord loot delivery is enabled per Guild in Community → Settings → Game settings → Discord modules. New eligible drops can provide the same participation buttons; private balances and full bid history are not published in the channel message.
If a drop or balance changed while a form was open, refresh and review the current result before retrying. Canceled records cannot be assigned again.
Alliances
Coordinate Communities for a game while keeping ownership and access separate.
For Community Owners and people with Alliance tasks.
Understand the Alliance boundary
An Alliance connects Communities for one game. Its current Host Community’s Owner holds Host ownership responsibilities. Each Community keeps its own membership, Guilds, Discord connection and permissions.
Joining does not move Guilds, create membership in partner Communities or reveal their private rosters. A Community participates in at most one active Alliance for a given game; capacity is checked when participation is accepted.
Create or join
- Open My Alliances → Create a New Alliance.
- Select a Community where you hold Alliance management, then one of its games (a game with at least one Guild) and the name.
- Open the resulting Alliance workspace.
Open My Alliances → Applications and invitations to track participation for a Community you manage. Select the intended Community, then received invitations or sent applications. This remains available when you have no Alliance membership. Your personal Community applications remain under My Communities → My applications & invitations. Alliance workspace Applications is the separate incoming review queue.
Manage applications, announcements and Events
Alliance access comes from two tasks in Community roles, each assigned for selected games or for all current and future games: Alliance management and Alliance content. Each participant Community's Owner holds both for their own Community. There are no separate Alliance roles.
Use Applications to review incoming requests when the Host Community gave you Alliance management. The same people manage outgoing invitations and Invite a Community. Accepting requires current eligibility and capacity.
Alliance content lets any participant's authorized people manage every announcement, Alliance Event and shared check-in code. Announcements have panel detail views. In Alliance Settings → Discord, each Community decides for its own server whether announcements and Alliance Events are sent and to which channel: Alliance Events use the game Event channel by default, or a separate channel you choose, or none. The Host also chooses its application channel there.
For shared Events, target the intended Guilds. Attendance, points and party management remain scoped to each participating Community and its permitted Guilds.
Alliance announcements are on the Alliance Overview and work like Community announcements: Discord Markdown, editing replaces and deleting removes the Discord messages.
Transfer the Host, remove or leave
Alliance management in the Host Community lets you transfer the Host to an existing participant at once from Danger Zone; the new Host's Owner and its Alliance managers take control immediately.
The same people can remove another participant from the Participants table row menu. Removal works like leaving: participation ends and its Guilds leave open alliance Events. Its Owner is notified, and the Community can apply or be invited again at any time.
A Host with other participants must transfer before leaving. Leaving as the sole Host closes the Alliance. Disbanding ends participation and pending invitations.
Read the confirmation and resource impact before leaving or closing an Alliance. Rejoining is a new participation period.
Visibility and notifications
Control public information and understand where updates appear.
For everyone managing a profile or public resource.
Choose what your Player profile shares
Open Profile → Privacy to control the Player profile, shared categories and individual active Character/Community/Guild relationships.
A preference and effective visibility are different. You may choose to share a Guild relationship while its private parent Community prevents publication. The profile settings show the reason; making a preference public cannot override the resource’s privacy.
A Character profile exposes limited identity information rather than every dynamic game field. A private Guild can hide the relationship without hiding the Character’s public identity.
Manage public Community and Guild profiles
Authorized resource profile managers choose public/private visibility and maintain introductions, images and the application intake. Every active resource is listed in Discovery. A private one shows visitors only its showcase (name, images, introduction, languages, play style and summary counts) while member and relation lists stay hidden; it never opens internal management or attendance data.
Applications depend only on the intake switch, so a private resource can still accept them. A private Community makes its Guilds private for visitors without changing their saved choice. Public member lists also respect each person’s effective visibility, so they may not show every member counted in a summary.
Use your notification inbox
The account notification area contains personal updates and eligible platform announcements. Open a notification to reach its current target; access can change after the notification is created.
Use available read/unread controls to keep track of updates. If a target was deleted or is no longer accessible, the notification does not grant access to it.
Manage Discord direct messages
In Profile → Notifications, use Discord direct messages to turn personal bot DMs on or off. The preference starts enabled; turning it off leaves web notifications available.
Delivery also depends on Discord allowing DMs and sharing a server with the bot. A failed DM does not roll back the application, invitation or other successful action that caused it. Check the panel inbox when a DM is missing.
Troubleshooting
Start with the right account, resource, permission and current status.
For members and organizers resolving common problems.
I cannot find or join a Guild
Check that you are signed in with the intended Discord account. Use the exact application or invitation link for a private target. Discovery lists private resources too, but shows only their showcase.
Check whether applications are open, the resource and game are active, your code is still valid and your Character meets the current game/Community requirements. A Character already in a Guild cannot simply be accepted into another one.
If the application asks you to join Discord, use that screen’s invitation/check flow. Discord membership is separate from Community or Guild acceptance. A submitted application can still be pending.
A management action is missing
Open the correct resource and ask its Owner or authorized role manager to check your current membership, explicit permission and Guild scope. Discord roles and leadership titles are not panel access.
An inactive resource can allow permitted history reading while blocking new operations. Check current capacity and activation requirements before assuming it is a permission problem.
If your form reports newer data, reload and review the current values before submitting again. Keep the visible error/request identifier when asking for support; never share passwords or sign-in credentials.
Discord roles or messages are missing
For roles, check the current server connection, that a role switch is on and saved, and the bot’s position above the created roles. A member must exist in the linked Discord server to receive its roles.
For messages, check the exact general/game/Guild channel row, its enable switch, saved channel and bot access. Open delivery history for the recorded failure rather than assuming a panel operation failed.
A recreated role has a new identity; set its Discord permissions again if you use them. If a delivery is marked uncertain, inspect Discord before confirming a retry.
My response, attendance or points look wrong
RSVP is intent. Check the separate attendance result and whether the completed game Event’s Guild scope has been confirmed. A zero reward and a no-game Community Event do not award points.
Check the selected Character/Family and its Guild membership period. A profile change does not create a second participant. Rejoining a Guild creates a new points account; an old Event correction belongs to its old membership period.
Use points history to distinguish Event awards/reversals, manual adjustments, decay, loot charges and refunds. Leading Auction bids reserve available points before a final charge is recorded.
Get help with enough context
Share the affected screen or Event link, the intended action, what happened and a visible request identifier if one is provided. State the Community/Guild and your expected role without sharing private application answers or unnecessary member data.
Use the platform Discord/support link where configured. For account/privacy contact information, see Privacy Policy. Review Change Log for published product changes.