Skip to main content

Discord Bots and Agents

Automation helps RaidGuild coordinate access, preserve knowledge, and run shared workflows. A bot’s permissions depend on the space in which it appears; never assume every agent can read or write everywhere.

Guild.XYZ​

Guild.XYZ validates wallet-based requirements used for Discord roles and access. Members and cohort graduates / apprentices may be asked to connect their wallet and synchronize the roles available to them.

Follow the current verification prompt in Discord rather than a channel link copied from an older handbook version. If access does not update, use the support path identified in Castle Walls.

Dungeon Master and RaidGuild Guard​

Dungeon Master has been sunset and should not be used as the system of record for new Raids. Older handbook pages or records may still refer to it. Portal now holds durable project context, while the CRM holds leads, opportunities, ownership, commercial status, and next actions.

Confirm current RaidGuild Guard commands and permissions with its maintainers before documenting or relying on a workflow.

Prism / Queen Raida​

Prism is RaidGuild’s organizational agent system and often appears in Discord as Queen Raida. It is designed to help turn community activity into durable memory and reusable workflows across Discord, chat, and apps.

  • Access is scoped per channel and workflow.
  • Some contexts are read-only; others may permit writing or actions.
  • Stewards can have agent profiles tailored to their category and responsibilities.
  • Common uses include meeting notes, content support, operational automation, code generation, and knowledge retrieval with source references.

Read the full Prism / Queen Raida guide for boundaries, intended uses, and knowledge sources.

Raid Agent​

The Prism Raid Agent supports the Raid lifecycle through a dedicated Discord channel. That channel is the primary Cleric interface for creating and maintaining CRM and Portal records, as well as the central place for previews, reconciliation notices, conflicts, and exceptions requiring human review. Clerics may still use the CRM or Portal UI directly, but routine operation should not depend on it.

The agent may read permitted internal Raid channels during its scheduled workflow, but it is not intended to act as a conversational bot in every Raid. It does not currently operate in client-shared Camps. Read the Raid Lifecycle for the review model and current boundaries.

Ask Raida