How to Build and Run a Wizard101 Discord Community With YourBot

A Wizard101 Discord should be organized around who can actually play together, what activity they are running, and what progression that activity requires. Wizard101 now spans PC and console, multiple language-server environments, normal four-Wizard combat, six-person social groups, Beastmoon teams, Guilds, and raids with different capacities. Treating all of that as one generic MMO LFG pool creates bad signups before anyone reaches the Spiral.

The most common compatibility mistake is assuming that every Wizard101 player can simply meet in the same realm. Realms are useful meeting points inside a compatible game environment, but they do not bridge platform/server boundaries. Console players can cross-play with other console platforms, while PC and console do not cross-play; European language servers are also separate from one another. A Discord therefore needs to capture the actual game pool before it worries about school, level, world, boss, or realm.

This guide builds a fictional 246-member community called Spiral Wardens. It supports casual questing, dungeon farming, Beastmoon, housing gauntlets, guild recruitment, and organized endgame raids. Forty-four members belong to its associated in-game Guild, but Discord membership and Guild membership remain separate. YourBot handles the Discord-side structure, onboarding, moderation, tickets, LFG, events, temporary voice, announcements, public feeds, analytics, and giveaways. Wizard101 remains the authority for characters, worlds, Guild membership, raid access, inventories, accounts, and game enforcement.

Start With the Right Wizard101 Community Model

Compatibility starts with the game environment

Wizard101 has several boundaries that matter before an LFG can be considered compatible.

• PC and console do not cross-play.
• Xbox, PlayStation, and Nintendo Switch players share the console environment, although console players can disable cross-play and limit themselves to their own console platform.
• European language servers are separate from one another and require separate accounts.
• PC Steam accounts and website-created PC accounts have separate account-login and purchase histories, so support questions should distinguish them even when the community is discussing PC play.
• A Wizard101 realm is a meeting location inside a compatible environment, not a bridge between these pools.

Do not make seven permanent platform channels just because multiple clients exist. Put the play pool on LFG and event records and create permanent pool roles only if your traffic justifies them.

A Group, a battle team, and a raid are not the same size

Wizard101 is a strong example of why Discord signup capacity must be activity-specific.

Normal instanced combat and boss farming are usually designed around up to four Wizards. Wizard101 Groups and Adventure Parties can contain up to six players, which is useful for social coordination and some event queues but does not turn a four-Wizard dungeon into six combat seats. Beastmoon Hunt uses teams of 4–6 Wizards. Guilds can contain up to 50 members. Guild raids also vary: traditional raids are 12-player activities, while 2026's Ghastly Conspiracy became the first 8-player raid.

YourBot Group Finder should model the capacity of the actual activity, not whichever number is largest.

Schools are context, not a fixed MMO trinity

Fire, Ice, Storm, Myth, Life, Death, and Balance create meaningful team differences, but Wizard101 does not require a universal Tank/Healer/DPS composition. A Life Wizard may heal, an Ice Wizard may play defensively, and a Storm Wizard may be built around damage, but those are strategies rather than mandatory queue roles.

Use school as useful context. For difficult farming, Challenge Mode, PvP, or raids, let the organizer describe the strategy or desired responsibilities without pretending every group must contain one rigid class composition.

Progression gates matter

Two Wizards may both be on PC and still be wrong for the same run because one lacks the required world, quest, level, Guild membership, raid unlock, or Challenge Mode access.

A useful listing can include:

• character level
• school
• current/required world
• Standard versus Challenge/Advanced content
• raid/guild access
• specific boss, gauntlet, world, or farming target
• whether the run is teaching, progression, or farm
• whether voice is required

Do not ask YourBot to verify this from Wizard101. Unless you build and maintain a supported integration later, these values are member-supplied.

Current content differs by platform and region

Wizard101's release cadence is not one universal track. Official 2026 update material shows North American PC, console, and European PC environments at different content points. For example, official summer communications placed NA-PC on later Chronicle/Raid updates while console and EU-PC were on earlier content tracks.

That makes dated wording essential. A Discord announcement should say something like NA-PC: Barkingham Chronicle farm night or Console: Aquila Chronicle learning run instead of assuming the entire community has the same update.

As of September 25, 2026, Wizard101 is also in its eighteenth-anniversary period, with September events and promotions rotating through the month. Treat temporary events as dated content. Do not turn them into permanent channels.

The Community We Will Build

Spiral Wardens is a 246-member Wizard101 Discord.

• Primary audience: English-speaking North American PC and console players, with an opt-in area for EU language-server members.
• Associated in-game Guild: 44 current member accounts, leaving room below Wizard101's 50-member Guild cap.
• Mix: new questers, returning players, max-level farmers, Beastmoon players, housing enthusiasts, and an organized raid team.
• Recurring activities: story-help nights, boss/gear farms, Beastmoon groups, Guild raid progression, housing gauntlets, and newcomer teaching runs.
• Staff never claims that Discord roles change Wizard101 Guild permissions or that YourBot can inspect a Wizard's inventory, school, level, quest state, or account.

YourBot's role in the community

1. Create the Foundation With Start Your Server

Use Start Your Server to create a durable structure first. Do not make permanent channels for every world, school, raid, boss, gear set, event, or seasonal activity. Those topics change too often and fragment conversation.

The server owner should run the builder, verify that the bot has the required channel and role permissions, and review the entire proposal before building. Keep the first pass additive: preserving existing channels is safer than asking the builder to clean up years of history in the same operation.

Copy-ready community brief

Design a Wizard101 Discord server called Spiral Wardens.

Community:
- About 250 Discord members.
- English-speaking Wizard101 community with questing, farming, Beastmoon, housing, events, Guild activity, and endgame raids.
- About 44 members are also in the associated Wizard101 Guild, but Discord membership and in-game Guild membership are separate.
- Support newcomers and veteran/max-level players.

Compatibility:
- PC and console are separate play pools and cannot cross-play.
- Console includes Xbox, PlayStation, and Nintendo Switch; console users may disable cross-play.
- European language servers are separate and must not be mixed into incompatible LFGs.
- Realm is a meeting location inside a compatible play pool, not a server-compatibility field.
- PC storefront/account type is useful for support but should not create unnecessary social silos.
- Standard combat and dungeon groups are generally capped at 4 Wizards.
- Groups and Adventure Parties can contain up to 6.
- Beastmoon Hunt teams are 4-6.
- Guild raids are activity-specific: use 8 for Ghastly Conspiracy and 12 only for raids that actually use 12.
- Never use a generic five-player MMO default.

Roles:
Owner, Administrator, Moderator, Event Host, Raid Lead, Guild Officer, Mentor, Member, Newcomer.
Optional self-select interests: Questing, Farming, Beastmoon, PvP, Housing, Guild Raids, Teaching, Events.
Optional school interests: Fire, Ice, Storm, Myth, Life, Death, Balance.
Optional play-pool roles: PC-NA, Console, EU/Language Server.
Staff, Guild Officer, Raid Lead, and trusted roles must never be self-selectable.

Channels:
START HERE: welcome, rules, choose-roles, announcements
COMMONS: general, screenshots, questions, builds-and-decks
FIND A GROUP: lfg-listings, lfg-forum, events
GUILD: guild-info, raid-planning
HELP: faq, open-a-ticket
FEEDS: wizard101-updates
VOICE: join-to-create lobby
STAFF: staff-chat, sentinel-logs, ticket-log, server-log

Safety:
- Never request passwords, 2FA codes, recovery codes, full payment information, session data, or account-sharing access.
- Never ask members to give staff control of a Wizard101 account.
- Character name, school, level, and progression are self-reported unless a verified integration exists.
- Discord moderation is not KingsIsle enforcement.
- Discord roles do not change Wizard101 Guild roles, Guild membership, raid access, or character progression.
- Keep private reports and applications staff-only.

Configure all ten built-in services:
Welcome; Sentinel; Tickets; Group Finder; Beacon Events; Join-to-Create Voice; Announcements; Social Feeds; Analytics; Giveaways.

Wizard101-specific rules:
- Group Finder templates must be created manually for Wizard101.
- Use the real capacity for each activity.
- Every LFG must include the compatible play pool before realm or activity details.
- Announcements and Social Feed subscriptions may require manual finishing steps.
- Analytics measures Discord/community behavior, not in-game performance.
- Giveaways do not automatically transfer Wizard101 rewards.

First pass:
- Preserve existing server structure.
- Keep deletions off.
- Preview Member, Moderator, Raid Lead, and Newcomer perspectives.
- Review Channels, Roles, Permissions, and Services before building.
- Report any failed or skipped permissions instead of working around them.

A compact channel plan

SPIRAL WARDENS
├─ START HERE
│  ├─ #welcome
│  ├─ #rules
│  ├─ #choose-roles
│  └─ #announcements
├─ THE COMMONS
│  ├─ #general
│  ├─ #questions
│  ├─ #screenshots
│  └─ #builds-and-decks
├─ FIND A GROUP
│  ├─ #lfg-listings
│  ├─ #lfg-forum
│  └─ #events
├─ GUILD
│  ├─ #guild-info
│  └─ #raid-planning
├─ HELP
│  ├─ #faq
│  └─ #open-a-ticket
├─ FEEDS
│  └─ #wizard101-updates
├─ VOICE
│  └─ 🔊 Join to Create
└─ STAFF
   ├─ #staff-chat
   ├─ #sentinel-logs
   ├─ #ticket-log
   └─ #server-log

Review before applying

Use the Channels, Roles, and Services review views. Preview the server as a Newcomer, normal Member, Raid Lead, and Moderator. Confirm that newcomers can see the rules and verification path but cannot see staff or private Guild planning.

Keep deletions disabled on the first build. Read the build report and fix permission failures before making cleanup decisions. A successful partial build is not the same as a fully correct design.

Announcements schedules and Social Feed subscriptions require manual finishing steps. The builder can enable those services, but the actual recurring schedules and specific feeds still need to be created.

2. Welcome: Sort by Compatibility Before School

A useful Wizard101 onboarding flow should answer where can this person play? before asking what school they prefer.

Give new arrivals a limited Newcomer or Unverified role until they accept the rules. Then grant Member. Do not make Guild Officer, Raid Lead, Moderator, Administrator, or other trusted roles self-selectable.

Useful opt-in roles include:

• PC-NA
• Console
• EU/language-server roles only if the server actively supports those communities
• Questing
• Farming
• Beastmoon
• Guild Raids
• PvP
• Housing
• Teaching / Mentor Interest

School roles are useful as interests, not proof of roster composition. A member may have several Wizards and several schools, so allow multiple school interests rather than forcing one identity.

A concise greeting can say:

Welcome to Spiral Wardens. Choose the Wizard101 play pool and activities you actually use, then browse Group Finder for compatible runs. PC and console do not cross-play, and some EU language servers are separate. Never share your password, recovery codes, payment details, or account access with anyone here.

Do not collect exact age, billing information, account passwords, or parent-account data during normal onboarding.

Test: Join with a test Discord account, complete verification, choose PC-NA plus Questing, and confirm that the account receives only those intended roles and cannot see staff channels.

3. Sentinel: Protect Wizards From Account and Code Scams

Wizard101's own community rules prohibit account sharing and third-party trading of account items/access. Its help material also warns that KingsIsle will not ask players to trade Treasure Cards in exchange for codes. Those risks should shape Sentinel more than generic MMO profanity filtering.

Start with protections for:

• credential phishing and fake login pages
• fake Crowns, bundle, membership, or promotional-code offers
• requests to share account credentials
• third-party account/item sale advertisements
• suspicious shortened or freshly registered links
• impersonation of KingsIsle staff, community staff, or known creators
• malicious attachments and executable downloads
• spam, mass mentions, raids, and repeated invite abuse
• harassment or targeted abuse

For new or aggressive rules, begin in dry-run/log mode. Review false positives before enabling automatic deletion, timeout, or escalation.

A Discord moderator can act on Discord behavior. They cannot restore a Wizard101 account, reverse a trade, alter a Guild roster, or issue a KingsIsle penalty.

Discord moderation is not game enforcement.

Test: Use a harmless staff-only test phrase that matches one controlled rule, confirm Sentinel logs/cases it correctly, and verify that the rule performs only the action staff intended.

4. Tickets: Route Guild, Raid, and Safety Questions Privately

Spiral Wardens benefits from four focused intake paths.

Member Report

• Discord member or character name being reported
• Discord / Wizard101 / both
• message link or screenshot if safe to share
• short description
• immediate safety issue? yes/no

Guild Application

• Discord display name
• Wizard character name
• play pool
• school(s)
• approximate level/progression
• usual play times
• interests: raids / farming / social / events
• acknowledgment that Discord acceptance does not automatically add the character to the in-game Guild

Raid / Teaching Request

• raid, dungeon, boss, or world
• play pool
• character level and school
• current unlock/progression state
• first clear / learning / farm
• preferred times
• voice availability

Server Help

• role/access issue
• event/LFG problem
• bot/service issue
• other Discord-side question

Never request passwords, one-time codes, recovery codes, full payment information, or remote access. There is rarely a reason for community staff to request a Wizard101 login username either; character name and relevant gameplay context are usually enough.

Accepting a Guild ticket does not invite someone in-game. Accepting a raid request does not grant raid access or unlock a world.

Test: Open one Guild Application and one Member Report using a test account. Verify that the application reaches the correct Guild staff, the report remains private, and neither route exposes the ticket to ordinary members.

5. Group Finder: Match the Play Pool, Then the Activity

Read-only inspection of YourBot's current develop revision shows that Wizard101 is not in Group Finder's automatic game-detection keyword list. The setup wizard can still create the channels and infrastructure, but Spiral Wardens should create explicit Wizard101 templates manually.

Do not keep the generic five-player Quick Group as the model for Wizard101. Five is wrong for the game's most common combat groups.

Create the first template

Template Name: Wizard101 Questing / Boss Farm
Game: Wizard101
Default Party Size: 4
Default Expiry: 2 hours
Description: Four-Wizard questing, dungeon, boss, or gear farm. Always state play pool, target, progression requirement, school/level context, and meeting realm.

Additional templates

Only expose a raid template to the communities for which that raid is actually available. Wizard101's PC, console, and EU content tracks can differ.

Example live listing

Title: Darkmoor / Challenge Farm — 2 more
Game: Wizard101
Play Pool: PC-NA
Activity: Boss / gear farm
Target Size: 4
Current Players: 2/4
Meeting Realm: Wu
Target: Darkmoor
Mode: Standard farm
Character Context: Level 180 preferred; bring the Wizard you intend to farm on
Schools Currently Present: Life, Storm
Needed: No hard school requirement; tell us your school when joining
Experience: Chill farm — mechanics explained if needed
Voice: Optional
Session: ~90 minutes
Notes: Joining this Discord listing does not place you in the in-game group. Meet in the stated realm after the leader confirms the party.

A realm can be changed easily and should not be treated like a server region. The play pool is the compatibility gate.

Group Finder's current listing model can carry platform, region, difficulty, voice, start time, approval mode, role slots, waitlists, and forum threads. Use those fields to keep the title short and the compatibility information structured.

Test: Post one four-Wizard farm, fill all four seats, confirm the fifth interested member goes to the waitlist instead of becoming a fake fifth combat seat, and then close the listing.

6. Beacon Events: Reserve Planned Attendance for Raids and Community Nights

Use Beacon for activities that happen at a scheduled time and benefit from RSVP discipline.

A useful Ghastly Conspiracy event could look like:

Event: Ghastly Conspiracy Learning Run
Play Pool: Console
Date/Time: Saturday 8:00 PM server time
Capacity: 8 playing Wizards
Waitlist: Enabled
Requirements: Correct Guild/raid access, appropriate progression, voice strongly recommended
Hosts: 1 Raid Lead + 1 backup coordinator
Teaching: Yes
Estimated Duration: 2 hours
Notes: A playing mentor occupies one of the 8 raid seats.

Do not create 8 players + mentor if the mentor is actually entering the raid. That is nine people for an eight-player activity. A non-playing observer helping in Discord is different, but make that explicit.

For a 12-player raid, use 12. For Beastmoon, use the current team capacity. For a normal four-Wizard farm, four may be enough even if twenty people want to attend; create multiple waves instead of pretending they are one party.

Beacon RSVP does not automatically register a player in Wizard101, create a Group, unlock a raid, reserve an in-game instance, or grant loot.

Test: Create a staff-only eight-seat test event, fill it, add a ninth RSVP to the waitlist, remove one player, and confirm the replacement flow is clear before using the pattern for a real raid.

7. Join-to-Create Voice: Match Voice Capacity to the Real Team

A single unlimited voice lobby quickly becomes messy in a game where normal combat, Beastmoon, and raids have different communication needs.

Create a general Join to Create lobby under a temporary voice category. Let the room creator control the room when appropriate and delete empty rooms automatically.

Useful patterns:

• normal questing/farm room: default limit 4
• Beastmoon room: 6 when running a full event team
• Ghastly Conspiracy room: 8
• traditional 12-player raid room: 12
• social/housing room: no tight limit if it is not representing one game team

If one lobby cannot express those sizes cleanly, use separate Quest / Farm Voice and Raid / Event Voice lobbies or let organizers change the limit.

Discord voice does not create a Wizard101 Group or Adventure Party. Members still need to meet in the correct game environment and form the in-game party.

Test: Join the lobby, confirm a temporary room appears, transfer ownership to another test member, leave both accounts, and verify the room deletes when empty.

8. Announcements: Date Everything That Can Expire

Wizard101 has weekly events, seasonal promotions, rotating Beastmoon activities, update-track differences, and scheduled community runs. That makes undated announcement channels dangerous.

Use Announcements for:

• weekly This Week in Spiral Wardens
• Guild raid schedule
• platform-specific patch/update notices
• Beastmoon or Deckathalon reminders
• temporary event deadlines
• scheduled teaching/farming blocks
• server maintenance or rules changes

Use opt-in roles such as @Guild Raids, @Beastmoon, or @Events instead of pinging everyone.

A current September 2026 notice might say:

Wizard101 — September event reminder

• Current anniversary activities are temporary and should be treated as dated content.
• Check your game environment before organizing a run; NA-PC, Console, and EU-PC can be on different update tracks.
• This week's Spiral Wardens raid RSVP is in #events.
• Use Group Finder for unscheduled farms so #announcements stays readable.

Do not schedule an announced future feature as if it were already live. Avoid duplicating a Beacon ping with an Announcement ping for the same event unless each serves a different purpose.

Test: Schedule a staff-only announcement five minutes ahead, include an opt-in role, and confirm the message posts once with the expected mention behavior.

9. Social Feeds: Add Wizard101 Manually and Label the Source Scope

Read-only inspection of mmo_maid/plugins/social/game_catalog.py at the current develop revision shows no curated Wizard101 entry.

Wizard101 is available on Steam with App ID 799960, so a PC-oriented community can use YourBot's generic Steam source:

Source: Steam
Steam App ID: 799960
Display Name: Wizard101 — Steam / PC News
Destination: #wizard101-updates
Digest: Off or hourly, depending on volume
Ping Role: None by default

The inspected Steam adapter uses the public ISteamNews endpoint, filters to publisher community announcements, and has a 900-second default interval. That makes it useful for publisher-posted Steam news, but it is not a guarantee that every console, EU, support, social, or hotfix post will appear.

Because Wizard101's platform/update tracks can differ, a broad community should consider an additional verified official Wizard101 YouTube channel feed or verified RSS/Atom source if admins want more cross-platform communication. YourBot supports YouTube channel URLs/handles and generic RSS/Atom feeds. Paste the official source URL from Wizard101's own site rather than guessing an account name.

Label feeds by scope. Wizard101 — Steam / PC News is more honest than All Wizard101 News.

Start Your Server can turn Social Feeds on, but the actual subscription is a manual finishing step.

Test: Create the subscription, use Social Feeds' test/preview controls, confirm it posts to the intended channel without an unwanted role ping, and verify the source label is clear.

10. Analytics: Measure the Discord, Not the Wizard

Analytics is useful for questions such as:

• How many newcomers finish onboarding?
• Which LFG templates actually get used?
• Do four-Wizard farm listings fill?
• Are Guild raid RSVPs converting into active Discord participation?
• Which voice periods are busiest?
• Is #builds-and-decks healthy or mostly inactive?
• Do members return after their first week?

Exclude staff-only and sensitive ticket areas where appropriate.

Analytics does not know a member's Wizard101 level, school, deck, gear, damage, resist, PvP rating, inventory, quest completion, Guild rank, raid clear history, Crown balance, or account status just because they use Discord.

If Discord presence/game activity tracking is enabled, that can add Discord-side presence context, but it still does not become a Wizard101 character database.

Do not turn message count, voice hours, or LFG completions into a score for who is "best" at Wizard101.

Test: Generate a small amount of test activity in a normal channel and an LFG, then confirm the expected areas appear while excluded/private areas remain out of the view you intend staff to use.

11. Giveaways: Keep Discord Drawings Separate From Wizard101 Transactions

Use Giveaways for legitimate community prizes where staff understands how fulfillment works.

Safe examples include:

• choosing the next community event theme
• a temporary cosmetic Discord role
• a community-created art commission
• a staff-provided legitimate game code where its origin and redemption rules are known

Be particularly careful with "Crowns", account access, Treasure Card-for-code deals, item sales, or third-party trades. Wizard101's own guidance warns about account sharing and third-party trading, and YourBot does not authenticate or transfer Wizard101 assets.

Never ask a winner for a password, recovery code, payment credential, or account session information.

A giveaway result is a Discord result. YourBot does not automatically grant membership, Crowns, a pet, gear, a mount, Treasure Cards, or Guild access.

Test: Run a staff-only giveaway for a harmless Choose next Friday's farm prize with two staff test entries and confirm the draw, reroll, and audit flow.

Keep PC, Console, and Language Servers From Colliding

Spiral Wardens should use one community where possible, but compatibility must be explicit.

A simple role model is:

• PC-NA
• Console
• EU language-server roles only for active populations the Discord actually serves

Do not create separate general chats for Xbox, PlayStation, and Switch unless the community has a demonstrated reason. Console cross-play normally connects those platforms, though a member who disables cross-play may need a same-console group.

For EU players, the language server is a real compatibility boundary. A German-server member cannot join an English-language-server run merely because both members are physically in Europe.

For events and LFGs, use the play pool as a structured field. For casual discussion, let everyone share the same community spaces.

Treat Level, School, World, and Combat Rules as Session Context

Wizard101 has seven schools and extensive progression, but permanent role sprawl is not the answer.

Do not make 180 level roles or a channel for every world. Use:

• broad progression interests if truly useful
• optional school roles
• LFG description fields
• templates for repeated activities
• forum threads for one-off strategy
• a persistent profile plugin only when the community actually needs searchable long-term data

For an ordinary boss farm, school composition may barely matter. For a raid, Challenge Mode encounter, PvP team, or specific farming strategy, the organizer may need precise spell, school, or role expectations.

Keep those expectations on the run where they can change.

Use Guild Structure for Guild Work, Not for the Whole Discord

Wizard101 Guilds are an in-game system with their own membership, leadership, house, permissions, and activities. They currently support up to 50 member accounts, and recent Guild improvements reduced the number of players required to create a Guild from 12 to 8.

Spiral Wardens therefore keeps two truths separate:

1. The Discord can have hundreds of members.
2. The associated Wizard101 Guild has its own limited roster.

Guild Member, Guild Officer, and Raid Lead Discord roles are administrative conveniences. They do not modify the Wizard101 Guild.

For Guild raids, make access requirements clear. Older Wizard101 raids were built around 12 players; Ghastly Conspiracy is an 8-player raid. Never create one permanent Raid = 12 rule and assume future raids will follow it.

Add a Spiral Readiness Registry Only When You Need It

Spiral Wardens can launch with the ten built-in services. Group Finder handles today's run, Beacon handles scheduled attendance, Tickets handle applications, and Announcements handle plans.

A custom plugin becomes useful if staff repeatedly asks the same persistent question:

Which of our members have a Wizard that is actually ready for this activity?

Before building, check the Marketplace for a maintained plugin that already solves the problem. If nothing appropriate exists, create Spiral Readiness Registry with Plugin Builder.

The registry is not an account verifier. It stores self-reported community profiles that members can update and staff can search.

Copy-ready Plugin Builder specification

Plugin Name: Spiral Readiness Registry

Purpose:
Create a per-Discord-server directory of self-reported Wizard101 character profiles so members and event staff can find suitable Wizards for future activities without duplicating Group Finder, Beacon Events, Tickets, or Announcements.

Core principle:
This plugin stores community-provided planning data only. It does not connect to KingsIsle, log into Wizard101, verify characters, inspect inventories, read game memory, automate the game client, or modify Guild membership.

Version 1 network policy:
No external network access.
Do not request or store Wizard101 credentials, session data, 2FA/recovery codes, billing details, or email addresses.

Admin roles:
- Administrator
- Moderator
- Raid Lead
- Guild Officer

Member capabilities:
Members can create, edit, view, and archive their own Wizard profiles.
Members cannot edit or delete another member's profile.
Members can choose whether a profile is visible to all server members or only event/guild staff.

Profile fields:
- Discord user ID
- Wizard nickname/character name
- play_pool: PC-NA | Console | specific EU language server | Other
- console_crossplay_note: optional
- school: Fire | Ice | Storm | Myth | Life | Death | Balance
- level: integer
- current_story_world: short text
- guild_member: yes/no
- activity_interests: questing, farming, Beastmoon, PvP, housing, raids, teaching
- raid_readiness: list of self-reported raid names/unlocks
- magic_weaving_rank: optional self-reported text/number
- preferred_voice: required_ok | optional | no_voice
- availability_note: short text
- strategy_notes: short text
- last_reviewed_at
- status: active | needs_update | archived

Staff-only fields:
- staff_note
- reviewed_by
- reviewed_at
- moderation_flag

Do not store:
- password
- login username unless product review proves a real need; default to no
- email address
- payment information
- recovery code
- 2FA code
- account session/token data
- exact home location
- government identity
- private support correspondence

Suggested commands:
- /wizprofile create
- /wizprofile edit
- /wizprofile mine
- /wizprofile view
- /wizprofile archive
- /wizroster search
- /wizroster stale
- /wizroster mark-reviewed

Search filters:
- play pool
- school
- minimum level
- guild member
- activity interest
- named raid readiness
- voice preference
- status

Dashboard:
Member view:
- My Wizard profiles
- edit/archive controls
- visibility setting
- stale profile warning

Staff view:
- searchable roster
- filter chips
- stale profiles
- raid-readiness view
- audit history
- staff-only notes

Permissions:
- Authorization must be checked server-side on every read and write.
- A normal member may mutate only records tied to their own Discord user ID.
- Staff-only fields require configured staff roles.
- Direct record URLs must enforce the same authorization as list pages.
- Revoking a staff role must remove staff access immediately on the next request.
- Exports, if added later, must be staff-only and audited.

Storage:
- Isolate all records by Discord server ID.
- A plugin installed on Server A must never read Server B.
- Keep an audit record for profile edits, staff reviews, archive actions, and visibility changes.
- Provide deletion/archive behavior for members leaving the community.

Important non-capabilities:
- Do not verify Wizard101 account ownership.
- Do not scrape or call Wizard101 in version 1.
- Do not infer level, gear, school, progression, or raid access.
- Do not create Wizard101 groups.
- Do not change Wizard101 Guild membership or permissions.
- Do not replace Group Finder.
- Do not replace Beacon Events.
- Do not replace Tickets.
- Do not replace Announcements.
- Do not rank members by skill or Discord activity.

Acceptance tests:
1. Member creates two Wizards on the same Discord account.
2. Another member can view only profiles whose visibility permits it.
3. A member cannot edit another user's Wizard.
4. Raid Lead can search PC-NA, level >= 170, Guild member, Ghastly readiness.
5. Revoking Raid Lead removes staff-only search/note access.
6. Direct-record access cannot bypass authorization.
7. Server A cannot access Server B records.
8. Archived profiles disappear from default active search.
9. No workflow ever asks for Wizard101 credentials.

Review, test, and continue through the SDK

Review the generated plan before building. Check the source, manifest, requested capabilities, storage choices, commands, and dashboard permissions. A validator passing does not prove that the authorization model is correct.

Test the plugin as:

• ordinary member
• member with multiple Wizard profiles
• Raid Lead
• Guild Officer
• moderator
• user whose staff role was revoked

Test direct record access, exports if any exist, archived records, and cross-server isolation.

For local continuation, use the current YourBot SDK workflow in Visual Studio Code: scaffold with yourbot new, exercise the project with yourbot dev or yourbot dev --watch, run yourbot validate, and use yourbot doctor when environment or manifest problems are suspected. Keep Marketplace publication optional; a private community workflow does not need to become a public product.

Run a Complete First-Week Member Journey

If members repeatedly misunderstand a workflow, fix it before adding more automation. A smaller Discord that consistently routes people to compatible groups is better than a complex one full of unused channels and stale roles.

Frequently Asked Questions

Can PC Wizard101 players play with console players?

No. Current Wizard101 console documentation says console platforms can cross-play with one another, but console does not cross-play with PC.

Should Xbox, PlayStation, and Nintendo Switch each get separate LFG channels?

Usually no. Console players share the console environment. Put console platform or cross-play status on the listing only when it affects compatibility.

How many people should a normal Wizard101 LFG use?

For most questing, dungeon, boss, and farming combat, use four. Groups and Adventure Parties can hold up to six, but that does not make every combat activity a six-player instance.

How many players are in a Wizard101 raid?

It depends on the raid. Traditional Guild raids use 12 players, while Ghastly Conspiracy is the first 8-player raid. Use a raid-specific template.

Does YourBot automatically detect Wizard101 in Group Finder?

Not in the read-only develop revision inspected for this guide. Run setup for the infrastructure, then create explicit Wizard101 templates manually.

Is Wizard101 in YourBot's Social Feeds game catalog?

Not in the inspected curated catalog. Wizard101's Steam App ID is 799960, so admins can add it manually through the generic Steam source. A broader community can also add verified official YouTube or RSS/Atom sources where appropriate.

Can YourBot verify a Wizard's school, level, gear, Guild rank, or raid clears?

Not through the built-in services. Treat those as self-reported unless you later deploy a properly supported integration. Discord roles and the optional custom profile plugin do not change anything in Wizard101.

Do we need the custom Spiral Readiness Registry to launch?

No. Launch with the built-ins first. Add the registry only when persistent roster/readiness information has become a recurring operational problem.

Build Around the Spiral's Real Boundaries

A strong Wizard101 Discord does not need hundreds of channels. It needs accurate compatibility information.

Start Your Server can establish the durable foundation: onboarding, roles, permissions, LFG areas, event space, help routes, feeds, voice, and staff operations. Welcome and Sentinel protect the front door. Group Finder handles four-Wizard farms, six-person social/event groups, Beastmoon, and raid-specific capacities without flattening them into one template. Beacon schedules serious runs. Temporary voice gives those groups a place to coordinate without leaving dead channels behind.

The rest stays where it belongs. Wizard101 decides character progression, schools, worlds, realms, Guild membership, raid access, rewards, and account enforcement. YourBot organizes the Discord around those facts.

Once that foundation is working, use Start Your Server to refine the server structure and Plugin Builder only for a persistent workflow—such as the Spiral Readiness Registry—that the built-in services do not already solve.