What your guild can do in Discord

Guild Manager connects Discord to your guild's roster, activities, and loot history. Members can respond to activity posts, upload gear screenshots, and check rewards in Discord. Officers configure the guild's rules and review detailed history in the dashboard.

Commands depend on your linked guild, enabled systems, and permissions. Start with /help for the commands available in your server.

Commands

In Discord or in the dashboard?

Take voice attendance

1. Enable voice attendance in the activity's attendance settings.
2. Run /track-activity activity:[select] use-configured-channels:true for the activity's saved attendance channels, or choose a category or channel-prefix for this run. Without a selection option, the command uses your current voice channel. Add preview:true to check coverage without recording attendance.
3. Check the command's result. Participation rules still apply; being in voice does not bypass eligibility.

This takes a snapshot. It does not continuously monitor the channel. Read the voice attendance guide for channel selection, scheduled snapshots, no-shows, and optional Shotcaller attendance.

Upload a T&L character screenshot

1. Link your character to the guild.
2. Run /gear update, select the character and class, and attach the screenshot.
3. Check the extracted gear score and attributes against the image. You can correct values in the dashboard.

OCR is already part of this workflow. It is not a future feature. T&L extraction covers gear score and visible attributes such as Strength, Dexterity, Wisdom, Perception, and Fortitude. This guide does not promise recognition of every equipment slot. Other games use their own configured gear fields and OCR support. Aion 2 skips screenshots: link a character to its Armory profile and Guild Manager reads Combat Power and item level from there.

Officer workflows that run inside Discord

A bot that posts events and syncs roles is easy to find. Guild Order, for example, includes a Discord bot in every plan from $3.99 a month (guildorder.com/pricing, checked 2026-10-07). The workflows below go further: an officer finishes the job in Discord, and the result lands in the same guild record and audit log as the web app.

Every command checks the officer's Guild Manager permissions, not their Discord roles. The systems behind these workflows, such as auctions, reward metrics, and recruitment, have to be turned on for your guild, and most are part of Core. See pricing.

Run a loot auction from start to handover

• Commands: /auction start, /auction bulk, /auction close, /auction award, /auction reverse, /auction relist, /auction reopen, /auction handover, /auction cancel.
• Who can run them: Create Auctions for start, bulk, and relist. Manage Auctions for close, award, reverse, reopen, and handover. Cancel Auctions for cancel.
• What it does: start opens an auction after you review its rules, and bulk creates up to 100 separate auctions from one list. award gives an unsold item to a character, for free or for a point charge. reverse undoes a pending award and refunds its charge. relist opens a fresh auction with no old bids, while reopen restores the old bids and refunds the previous winner. handover confirms delivery and makes the award final.
• Rules it enforces: award, reverse, relist, reopen, and cancel each need a written reason, and the award reason is visible to guild members. Points tied up in live bids are protected: /rewards subtract, no-show deductions, and deleted transactions are refused if they would leave a member with less than they have committed. Every officer auction action shows a confirmation first, and an item that has been handed over can't be awarded again or reopened.
• What gets written back: the auction, its bids, and point charges or refunds update in the web app. The audit log records auction creation, closing, awards, reversals, handovers, and cancellations.

Collect loot council interest

• Where: the Show interest button on a published loot council post.
• Who can use it: members with an active character in the guild, while the council session is open.
• What it does: the member picks an eligible character and can add a note or attachments that only council reviewers see. They can edit or withdraw their interest later from the same post.
• What gets written back: the interest appears on the council session in the web app. Council voting and the final award happen on the web.

Take voice attendance and mark no-shows

• Command: /track-activity activity:[select], with mark-no-shows:true to mark members who said yes but are not in voice, and finalize-attendance:true for a final check that flags members who checked in and left early. Add preview:true to check channel coverage first.
• Who can run it: Manage Activities or Modify Activities.
• What gets written back: attendance on the activity, plus any rewards or no-show deductions your guild's rules set. The audit log records attendance marks and no-show deductions. Alliance activities shared with your guild appear in the same activity list.

Adjust points

• Commands: /rewards add and /rewards subtract, each with a member, a reward metric, an amount, and a required note.
• Who can run them: Manage Reward Metrics.
• What gets written back: a transaction with the note on the member's history, marked as coming from Discord, and a reward adjustment entry in the audit log. Metrics that don't allow manual changes, and changes outside a metric's limits, are refused.

Review applications and leave

• Applications: applicants run /apply and fill in the guild's form in Discord when it fits there; longer forms open on the website. Officers with Manage Applications, or Review Assigned Applications for their assigned applicants, approve or reject from the application post. Rejecting asks for a reason.
• Leave of absence: officers with Approve Leave of Absence run /loa approve, /loa reject, /loa list, and /loa view.
• What gets written back: the application or leave status in the web app, with approvals and decisions recorded in the audit log.

Request gear and record donations

• Gear checks: /gear request user:[member] asks a member to update their gear and sends them a notification. It needs Request Gear Checks, View Member Gear, View All Gear, or Manage Members. Members answer with /gear update and up to five screenshots in games that read gear from screenshots.
• Donations: members run /donate with a screenshot of what they gave. When the items are detected, the donation is approved automatically; otherwise an officer reviews it in the web app.

Coordinate an alliance

Alliance activities can post to the host guild's Discord, to every member guild's Discord, or to one shared channel. Alliance leaders pick the mode in alliance settings, and member guilds can choose their own channel or opt out when the alliance allows it.

Soft reserves: publish and remind

/reservations publish posts a raid's reservation link in the channel, and /reservations remind posts a reminder without pinging anyone. /reservations status lets the organizer check the raid privately. The command appears once raid reservations are released for your game.

Set up an alliance

Core supports up to four owned guilds and an alliance of up to eight participating guilds. These are separate limits. Open your guild's Alliance settings and choose Create alliance. The guided setup asks for the alliance name, lets you choose what your guild shares, and shows the capacity before creation. Invite the other guilds after creating the alliance.

Bring applicants from Armory into your roster

Make your guild discoverable in Armory, enable recruitment, and review your application questions. A visitor opens your guild profile and chooses Apply. You can also share the guild's application link directly.

Officers review submissions in Applications. Approval adds or reuses the member's guild membership. Discord role changes depend on the guild's configured role-sync rules and the applicant's linked Discord account.

When moving from sheets or an event bot, start with one activity and your current recruitment form. Link characters, check one signup and attendance result, and verify your reward rules before adopting the workflow for the whole guild. This is a setup checklist, not an automated import from another bot.

See pricing for plan limits and the changelog for shipped updates.