A World of Warcraft: Forever Discord should help people find companions for the journey, not just fill a raid at level 60. Build it around game region, ruleset, faction, leveling progress, dungeon plans, profession campsites, and the next shared objective. Forever removes traditional realm selection, but that does not make every character compatible with every group. It also changes enough of familiar Azeroth that importing a Retail or Classic guild template unchanged will create misleading instructions.
As of September 25, 2026, Forever is in beta, with launch announced for November 4 and raids opening December 9. This guide builds Wayfarer Compact, a fictional 264-member community preparing a North America, Normal-ruleset, Alliance guild. Its Discord already has room for beta testers, launch planners, Horde friends, roleplayers, crafters, and returning players; it does not pretend those members already belong to a launched Forever guild. The research foundation is the supplied September 17 source archive, supplemented by Blizzard's September 24 beta updates. Launch and content schedule · Beta access and initial scope
YourBot organizes the Discord. It does not grant beta access, move characters between rulesets, invite players into the in-game guild, teleport a party, verify Legacy points, or place campsite objects. The setup below keeps those boundaries clear while making the human coordination useful.
Start With the Right World of Warcraft: Forever Community Model
Separate beta participation from launch plans
Forever is a new version of World of Warcraft built around a reimagined original Azeroth and a level 1–60 journey. Do not put its listings under an undifferentiated WoW label alongside Retail, Classic Era, or seasonal characters. Blizzard describes a distinct, enduring experience rather than another Retail expansion patch. Official overview
Use three statuses: Beta, Launch Planning, and eventually Live. The announced beta runs through October 21. Its opening scope included a level-20 cap, Hall of Thanes at levels 13–18, and Ruins of Lordaeron at 15–20; a later cap increase and additional tests were announced without making every planned dungeon immediately available. Verify the current test scope before scheduling a run. Do not promise beta characters or progress will carry into launch. Beta scope
Hardcore is announced for after launch. Keep it as an interest or future-planning role until Blizzard opens that ruleset, not as a live launch-day group category.
The supplied official landing-page snapshot lists Windows and Mac. Gamepad support is an input option, not a console-release announcement; this guide does not invent Xbox or PlayStation matchmaking. Official Forever page · Input options
Realmless does not mean ruleset-less, factionless, or regionless
Blizzard's launch design replaces traditional realm selection with Normal, PvP, and Roleplaying rulesets, with Hardcore later. Cooperative grouping remains within the appropriate ruleset, and Horde–Alliance grouping is not supported. Character names use two parts and are unique within a region. Record the actual in-game name—not a person's legal surname. Realmless explanation
The useful grouping label becomes:
Forever / Beta / North America / Normal / Alliance
Geographic preferences such as Oceanic evening hours or low-latency hosting belong alongside that label, not in place of the account's game region. The supplied Q&A reports Oceanic hosting while distinguishing realmless from regionless operation. It also describes shared Battlegrounds across rulesets; that does not establish unrestricted cross-ruleset premade grouping. Supplied Q&A reporting
Beta can still expose named test realms. Capture the current test-realm label when needed without rebuilding the permanent Discord around a launch realm-selection system Forever is replacing.
Separate dungeon planning, raid caps, and Battleground teams
Use a five-seat dungeon planning template with one Tank, one Healer, and three DPS. This is the guide's working WoW party configuration; the supplied opening-beta article names the dungeons and level bands but does not itself specify a party cap. Check the current activity in the client rather than presenting the template as independent proof of a Forever-only limit.
The raid and Battleground evidence is more explicit:
| Activity | Planning size | Evidence and status |
|---|---|---|
| Dungeon learning run | 5 | Working party template; confirm the current beta activity. |
| Barrow Deeps | 10 | Blizzard-announced raid size; raids scheduled for December 9. |
| Hyjal Summit | 20 | Blizzard-announced raid size; raids scheduled for December 9. |
| Onyxia's Lair | 40 | Size reported in the supplied raid guide; recheck final release requirements. |
| Darkspear Islands | 15 per side | Blizzard-announced 15v15 Battleground; not proof of a 15-person premade queue. |
Blizzard directly confirms Barrow Deeps, Hyjal Summit, and Darkspear Islands in its What's Next recap. The supplied raid overview provides the Onyxia planning reference. Do not copy Classic attunement chains, assume flexible raid scaling, or import Mythic+ into Forever. The supplied Forever Q&A describes a single dungeon/raid difficulty and no rated PvP at launch. Q&A reporting
Campsites and Legacy make leveling a community activity
A Basic Campfire accepts three crafted objects, not three players. Each player contributes one object, with a shared one-hour object cooldown; upgraded campfires can support five or ten objects. Profession contributions provide utility or buffs, and equivalent class buffs do not stack with their campsite variants. This is a resource-and-contribution plan, not a new party-size system. Camping and professions
Legacy adds a second distinction: points earned are shared across alts, but allocations are made independently on each character. A player's profession-focused alt and adventuring main can therefore need different help. Keep account-level progress separate from character-level choices, and never infer either from Discord activity. Legacy explanation
The Community We Will Build
Wayfarer Compact has 264 fictional Discord members. Its primary launch plan is North America / Normal / Alliance. Beta participation is self-reported. Horde, PvP, and Roleplaying members can share public discussion, but their operational listings remain separately labeled. No live guild size is invented before launch.
Recurring activities begin with leveling partnerships, dungeon introductions, travel groups, gathering outings, camp demonstrations, and beta feedback. Raid preparation comes later, with separate 10-, 20-, and provisionally 40-person plans. Class learning includes the new combinations rather than assuming Alliance-only Paladins or Horde-only Shamans.
YourBot's role in the community
| Service | Community use |
|---|---|
| Welcome | Explain compatibility and route members to leveling, professions, beta, or launch interests. |
| Sentinel | Moderate phishing, fake beta access, account sales, malicious downloads, and harassment. |
| Tickets | Separate guild applications, mentoring, beta troubleshooting, and private reports. |
| Group Finder | Recruit compatible dungeon parties, travel groups, and later raid replacements. |
| Beacon Events | Schedule leveling nights, camp workshops, and future raid attendance. |
| Join-to-Create Voice | Supply temporary party rooms and appropriately restricted planning rooms. |
| Announcements | Publish dated beta scope, launch milestones, and community schedules. |
| Social Feeds | Review official Warcraft videos without pretending they form a complete Forever patch feed. |
| Analytics | Evaluate Discord participation without inventing character or Legacy statistics. |
| Giveaways | Run community drawings with explicitly manual, non-gameplay fulfillment. |
1. Create the Foundation With Start Your Server
The Discord owner should open Start Your Server for the correct server. This owner-only workflow is separate from the service-management permissions granted to other staff. Position the bot above roles it must manage, and grant access to the channels it must configure. Do not move ordinary member or officer roles above trusted administrators merely to fix a permission error. Builder documentation
Use an additive first pass. Existing Retail and Classic channels may contain years of history; a Forever launch is not a reason to delete them. Ask the builder to create a clearly separated area or refine the current structure.
Copy-ready community brief
Design a World of Warcraft: Forever Discord called Wayfarer Compact.
Community:
- About 264 Discord members.
- Planned launch guild: North America / Normal / Alliance.
- Beta testers and launch planners coexist.
- Horde, PvP, and Roleplaying members are welcome socially.
- Do not imply the launch guild or live raid roster already exists.
- Preserve unrelated Retail and Classic areas.
Research cutoff: September 25, 2026.
- Forever beta is active; announced testing runs through October 21.
- Launch is announced for November 4; raids for December 9.
- Hardcore is after launch, not a currently available launch group.
- Beta scope is staged. Do not assume all announced dungeons are open.
Compatibility on every operational listing:
- Game version: World of Warcraft: Forever.
- Environment: Beta / Launch Planning / Live.
- Account game region.
- Ruleset: Normal / PvP / Roleplaying; Hardcore only when available.
- Faction: Alliance / Horde.
- Test-realm label if the current beta client requires one.
- Language, time zone, level range, activity, and gathering location.
- Do not assume cross-ruleset or cross-faction cooperative grouping.
- Do not substitute geographic latency preference for account region.
Group planning:
- Five-seat dungeon template: 1 Tank, 1 Healer, 3 DPS;
verify current beta activity restrictions.
- Barrow Deeps: 10; Hyjal Summit: 20.
- Onyxia: provisionally 40 from the supplied raid reporting;
reverify final release restrictions.
- Darkspear Islands: 15v15 match teams, not a verified premade limit.
- No Retail Mythic+ or multiple raid-difficulty presets.
- Campfire capacities of 3/5/10 count crafted objects, not people.
Staff roles:
Owner, Administrator, Moderator, Guild Officer, Event Host,
Mentor, Camp Coordinator, Raid Lead.
Public roles:
Member, New/Returning, Beta Participant (Self-Reported), Launch Planner,
Normal Interest, PvP Interest, Roleplaying Interest, Hardcore Interest,
Alliance Interest, Horde Interest, Tank, Healer, DPS,
Leveling, Dungeons, Professions/Camping, Legacy, Raids, Beta Updates.
Use a small number of menus; allow multiple character interests.
Do not make staff roles or Guild Member self-selectable.
Interest roles do not prove game access or guild membership.
Channels:
START HERE: welcome, rules, choose-roles, forever-status
COMMON ROOM: general, questions, character-plans
ADVENTURING: lfg-listings, lfg-forum, events, leveling-checkpoints
CRAFT & CAMP: professions-and-camping, supply-requests
GUILD: guild-info, guild-members, raid-planning
UPDATES: forever-updates, forever-news-review (staff-only)
HELP: open-a-ticket
STAFF: staff-chat, moderation-log, ticket-log
Voice:
- Start with a five-person dungeon lobby and a workshop lobby.
- Add raid-sized lobbies when actual demand arrives.
- Do not make camp voice limits equal crafted-object slots.
- Private guild voice needs access permissions, not just a user cap.
Enable all ten services:
Welcome, Sentinel, Tickets, Group Finder, Beacon Events,
Join-to-Create Voice, Announcements, Social Feeds, Analytics, Giveaways.
Product boundaries:
- Existing WoW detection creates Retail-flavored starter templates.
- Replace/relabel those inside the Forever area; preserve Retail users' setup.
- Put game-specific fields not supported by the UI into descriptions.
- A role or label does not enforce in-game compatibility.
- Announcement schedules and feed subscriptions need manual finishing.
- No verified Forever Steam catalog entry: do not invent an App ID.
Safety:
- No Battle.net credentials, authenticators, recovery codes, beta codes,
session tokens, payment details, or remote-access requests.
- No automatic in-game invitations, quest verification, camp placement,
character transfers, guild promotion, or Legacy tracking.
First build:
- Deletions off. Preserve messages and unrelated channels.
- Review Channels, Roles, and Services before applying.
- Preview New Member, Horde Visitor, Guild Member, Mentor, and Moderator.
A compact channel plan
WAYFARER COMPACT
├─ START HERE
│ ├─ #welcome
│ ├─ #rules
│ ├─ #choose-roles
│ └─ #forever-status
├─ COMMON ROOM
│ ├─ #general
│ ├─ #questions
│ └─ #character-plans
├─ ADVENTURING
│ ├─ #lfg-listings
│ ├─ #lfg-forum
│ ├─ #events
│ └─ #leveling-checkpoints
├─ CRAFT & CAMP
│ ├─ #professions-and-camping
│ └─ #supply-requests
├─ GUILD
│ ├─ #guild-info
│ ├─ #guild-members [RESTRICTED]
│ └─ #raid-planning [RESTRICTED]
├─ UPDATES
│ ├─ #forever-updates
│ └─ #forever-news-review [STAFF]
├─ HELP
│ └─ #open-a-ticket
└─ STAFF [RESTRICTED]
├─ #staff-chat
├─ #moderation-log
└─ #ticket-log
Review before applying
Check Channels, Roles, and Services, then preview the server from the proposed member roles. A Horde visitor can read class discussion without receiving the planned Alliance guild's private access. A Mentor can help newcomers without obtaining moderation or officer permissions.
The builder saves a snapshot before applying changes. Treat it as structural recovery assistance, not a backup of deleted conversations: deletion confirmations explicitly warn that messages are permanently removed. Leave deletions unchecked, read the build report, and retry only failed items after fixing permissions. Optional Discord onboarding also leaves the native rules-agreement step for the owner to enable in Discord. Build behavior
Announcements schedules and Social Feed subscriptions require manual finishing steps.
2. Welcome: Identify the Character They Want to Play
Under Services → Welcome, select the existing welcome channel rather than creating duplicate onboarding. Configure a verification panel that grants a limited Member role. A Discord verification button is not Blizzard account verification.
Use Role Menus for environment, ruleset/faction interests, and activities. Multiple selections are appropriate for a player planning several alts; the specific character used in a run still determines compatibility. Keep Guild Member, Mentor, and officer access out of public menus. Configure a separate Mentor pool for newcomers who want help, and leave role restoration off initially so returning members receive a fresh access review. Welcome setup
Suggested greeting:
Welcome to Wayfarer Compact. Choose Beta or Launch Planning, then your ruleset, faction, and interests. For groups, tell us the character you are bringing—not just “I play WoW.” Read #forever-status before treating a planned feature as live. Beta access is checked through Battle.net, never by giving staff your login.
Test: Join as an ordinary new member, select Horde and Beta interests, and confirm that public help works while guild-only and staff channels remain hidden.
3. Sentinel: Protect Beta Access and Community Trust
Enable Sentinel with a private moderation log. Start unfamiliar URL or keyword rules in dry-run/report mode, then review real false positives before applying automatic sanctions.
Prioritize fake beta invitations, account sales, gold-selling spam, impersonation, malicious addon installers, and harassment. A screenshot of a beta email is not proof of entitlement. Blizzard instructs selected players to verify their account's access and install through Battle.net. Official beta instructions
Do not block every mention of “beta,” “addon,” or “gold.” Those words appear in legitimate troubleshooting and profession discussion. Staff should not ask members to disable protections or hand over authentication codes to solve a login problem.
Discord moderation is not game enforcement. A Discord report does not impose or remove a Blizzard sanction.
Test: Use a harmless fake-domain example in a staff-only test channel. Confirm the intended rule logs it and that an official Blizzard link remains usable.
4. Tickets: Separate Recruitment, Mentoring, Bugs, and Reports
In Tickets → Teams, create deliberate staff routes; do not let an automatically discovered generic support team become the audience for every private case. Build four panel buttons with appropriate forms. Ticket setup
| Intake | Ask for | Route |
|---|---|---|
| Guild interest | Environment, game region, ruleset, faction, planned character role, availability. | Guild Officers |
| Leveling or dungeon help | Current level, zone/quest checkpoint, activity, available role, preferred time. | Mentors |
| Beta technical question | Build/date, test-realm label if present, reproduction steps, sanitized error, official-report status. | Beta support staff |
| Private conduct report | Discord message link, member involved, description, relevant evidence. | Moderators |
Use dropdown steps for categorical fields and concise text questions for the rest. Set ticket transcripts and logs to staff-only destinations. Tell members what is retained; closing a ticket is not the same as deleting its transcript.
Accepting an application grants, at most, the Discord access you explicitly configure. It does not create a Blizzard guild invitation. Staff can help prepare an official bug report, but cannot fix a beta character or grant access. Never collect passwords, authenticator codes, purchase information, or full unredacted diagnostic folders.
Test: Submit mentoring and conduct cases from a non-staff account. Confirm the correct teams see them and unrelated mentors cannot inspect the conduct case.
5. Group Finder: Replace Retail Assumptions, Not Just the Number Five
The inspected YourBot code recognizes wow, world of warcraft, and warcraft as WoW. It then creates WoW Mythic+ (5-man) and WoW Raid (20-man) starters, plus a generic Quick Group. There is no separate Forever starter branch in the reviewed revision.
That is a semantic mismatch, not simply a capacity error. Five is useful for dungeon planning, but “Mythic+” is not a Forever activity. Twenty matches announced Hyjal Summit, not every raid. Review starters through /group-admin templates; on a mixed-game Discord, preserve actual Retail templates and create clearly named Forever alternatives.
Select existing channels in Group Finder Settings. If a forum channel is selected and forum-thread creation is enabled, listings go to the forum rather than also posting to the text listing channel. Choose the behavior intentionally. Group Finder documentation
Create the first template
Template Name: Forever — Dungeon Learning
Game: World of Warcraft: Forever
Default Party Size: 5
Default Expiry: 2 hours
Slots: Tank 1 / Healer 1 / DPS 3
Description:
State environment, account game region, ruleset, faction,
current test-realm label when applicable, dungeon, level range,
quest checkpoint, meeting place, travel plan, and voice preference.
This is a five-seat planning template; verify current activity access.
No Mythic+ key, score, or Retail raid-difficulty requirement.
Native fields can cover region, role slots, voice, and start time. Put Forever-specific ruleset, faction, environment, and travel information in the description where the interface has no dedicated field. Do not claim those labels automatically reject an incompatible character.
Additional templates
| Template | Target size | Required context |
|---|---|---|
| Leveling partnership | 2 | Region, ruleset, faction, level/quest checkpoint, pace. |
| Dungeon learning | 5 | Activity access, roles, meeting point, quest preparation. |
| Gathering and camp outing | 5 suggested | Route, needed professions, object contributions; not a camp attendance cap. |
| Barrow Deeps planning | 10 | Future release status, requirements to verify, learning goal. |
| Hyjal Summit planning | 20 | Future release status, roster needs, loot agreement. |
| Onyxia planning | 40 provisional | Supplied reporting, final cap/access recheck before publication. |
Raid templates can be saved now without pretending a raid is playable. The current listing start-time window is up to 14 days: do not publish a December 9 run as a live September listing. Use a planning thread or appropriately labeled calendar event until recruitment is timely. Listing limits
Example beta listing
Title: [BETA] Hall of Thanes — first visit
Game: World of Warcraft: Forever
Game region: North America
Ruleset: Normal
Faction: Alliance
Test realm: enter the current client label
Build checked: September 25, 2026
Level reference: opening beta guide lists 13–18; confirm current access
Target: 5 including the playing mentor
Current roster: Tank 1 / Healer 1 / DPS 1 of 3
Goal: quests, exploration, mechanics; not speed farming
Gathering point: agree before departure
Travel: allow time to reach the entrance
Voice: listening or text callouts welcome
Loot: explain item-upgrade rules before entering
Confirm full character names and compatibility before the leader forms the in-game party. Closing a Discord roster does not summon anyone or validate quests.
Test: Fill the five-seat template and confirm the next applicant waits. Try a mismatched faction description and verify the leader catches it—the template is not a game-side compatibility checker.
6. Beacon Events: Schedule the Journey Before Raid Night
Use Beacon for attendance at a particular time: a leveling evening, camp demonstration, route-learning session, or later raid. Keep roster recruitment in Group Finder and the scheduled commitment in Beacon instead of maintaining two competing attendance lists.
A useful current beta event is:
Event: Beta Roads & Camp Workshop
Date: September 26, 2026 — 8:00 PM America/New_York
Environment: Forever Beta
Compatibility: North America / Normal / Alliance
Discord attendance target: 10
Game organization: two intended five-person groups
Prerequisites: beta entitlement; current build and available zone confirmed
Plan: gather, practice a route, demonstrate profession camp objects
Camp plan: three Basic Campfire object slots, not three attendees
Reminder: 30 minutes before
Fallback: mechanics discussion if testing becomes unavailable
The event time is a community choice, not a Blizzard opening time. Use the dashboard timezone and verify what members see. Beacon supports signup composition and reminders; check those on the individual event rather than assuming a later default change updates existing events. Beacon setup
For December, create a Hyjal Summit launch-planning event with 20 playing places only after the group chooses its own raid date. Assign tanks/healers based on tested encounter needs; the starter's 2/4/14 split is not evidence of a required Forever composition. A playing teacher uses one of the roster slots.
Test: Overfill the workshop's chosen attendance target, inspect the waitlist, and confirm the description distinguishes attendance, parties, and campsite objects.
7. Join-to-Create Voice: Rooms for Parties, Not Every Quest
In Voice Channels → Lobbies, create a dungeon lobby leading to a temporary category with a default limit of five. Add a separate workshop lobby with a larger discussion limit. Enable the intended empty-room cleanup and ownership-transfer behavior. Add 10-, 20-, or 40-person raid lobbies only when the community actually needs them. Voice configuration
Saved owner preferences can affect subsequent rooms, so test with a fresh ordinary account. A user limit controls capacity, not confidentiality: guild planning rooms also need restricted channel access. Discord administrators may bypass ordinary member restrictions, making an admin-only test misleading.
Let learners listen or use text when the event allows it. Camp objects do not require matching Discord voice slots, and a temporary room does not form the WoW group.
Test: Create a fresh five-person room, verify ordinary-member capacity, transfer ownership, and empty it. Separately check that an unrelated member cannot enter private guild planning.
8. Announcements: Date Every Beta Claim
Create schedules manually and use opt-in roles. Put the persistent status summary in #forever-status; use Announcements for changed facts and upcoming community sessions rather than repeating every source post.
WORLD OF WARCRAFT: FOREVER — checked September 25, 2026
NOW: Beta. Content opens in stages; check current test instructions.
BETA END: October 21 is the announced last full testing day.
LAUNCH: November 4.
RAIDS: December 9.
HARDCORE: After launch; no live availability assumed here.
September 24 beta changes:
Campfire behavior and class talents received updates.
Older build notes may no longer match the client.
Before LFG: confirm game region + ruleset + faction + environment.
Blizzard's September 24 notes allow more activities and resting poses while acquiring campfire benefits, and rename Druid Mangle to Primal Bite. Those are dated beta changes, not reasons to rewrite every permanent channel. September 24 development notes
The supplied launch articles disagree on the Pacific timezone label for the November 4 hour. Publish the confirmed date here and recheck Blizzard's final countdown before scheduling a minute-precise launch notification. Avoid a second Announcement ping when Beacon already supplies the event reminder.
Test: Schedule a staff-only notice for five minutes ahead, inspect the timezone and mention target, and then remove the test schedule.
9. Social Feeds: Use a Verified Warcraft Source, Not an Invented Steam Entry
The inspected curated catalog contains neither a WoW: Forever entry nor a verified Forever Steam source. Do not borrow another Blizzard game's App ID or paste an ordinary HTML news page into an RSS field.
An available supplementary source is the official World of Warcraft YouTube channel, linked from Blizzard's own site. YourBot's YouTube source accepts channel URLs and resolves the channel when saved. Social Feeds documentation
Source: YouTube
Channel URL: https://www.youtube.com/user/WorldofWarcraft
Display Name: Warcraft Videos — Forever Review
Destination: #forever-news-review
Include keyword: Forever
Ping role: None
Start in the private review channel. Check that the resolved channel is Blizzard's, preview a post, and inspect whether the keyword filter is too broad or misses videos without “Forever” in their searchable text. It is filtering, not an understanding of which WoW version a video covers.
Use verified Forever articles and pinned Blizzard beta topics for manual public updates. This video subscription is not an exhaustive patch-note feed. The Social Feeds documentation also says previously posted items are not updated when the source is edited; a maintained beta forum topic therefore needs a separate human recheck and correction workflow. No clean Forever-specific first-party RSS feed was verified for this guide.
Test: Resolve the channel, preview delivery, and review matching/nonmatching items before allowing any public posting. Leave the subscription unfinished if channel validation fails.
10. Analytics: Measure Participation Without Inventing Character Data
Configure Analytics for the public community areas you actually want to evaluate. Review channel/role exclusions, keep presence tracking optional, and leave content-republishing features such as a starboard off unless separately approved. Do not assume an exclusion deletes historical records or is a substitute for retention controls. Analytics documentation
Useful questions include whether newcomers return, whether leveling discussion stays active, which event times attract participants, and whether dungeon rooms are used. Compare those observations with Group Finder and Beacon records; message volume alone cannot explain a group's success.
YourBot's Discord metrics do not reveal character level, threat management, dungeon clears, professions, Legacy allocations, or guild membership. Do not award “raid ready” because somebody posts frequently, or publish a ranking of quiet versus vocal guildmates.
Test: Generate activity in an intended public channel, inspect the report, and verify that restricted reporting exclusions behave as configured. Review retention separately.
11. Giveaways: Community Rewards Without Access Claims
Configure the giveaway destination and authorized host role, then start with a reward staff can fulfill directly: choosing the next camp workshop topic, a community-art commission, or a cosmetic Discord role. Specify entry conditions and fulfillment before opening it.
Do not advertise beta entitlement, launch friend codes, in-game gold, profession levels, or Legacy points as things YourBot generates. The archive distinguishes beta account access from the separate launch Invite-A-Friend program; they are not interchangeable. Beta access · Upgrade and invitation information
Test: Run a staff-only drawing for “Choose our next leveling workshop,” verify winner/reroll behavior, and check the host cannot accidentally promise an in-game grant.
Make Leveling Cohorts Useful Without Turning Them Into Attendance Contracts
Forever's 1–60 journey deserves more structure than “everyone meet at max level.” Create voluntary cohorts with a shared checkpoint, a realistic pace, and an explicit policy for playing ahead. A player with two evenings available should not have to abandon friends who can play daily.
A useful post is:
Cohort: North Road
Compatibility: Forever / North America / Normal / Alliance
Environment: Launch Planning
Pace: two evenings weekly; exploration and professions welcome
Checkpoint: agreed quest turn-ins and route, recorded after each session
Playing ahead: allowed; keep a catch-up character or join mentor sessions
Next meeting: set through Beacon when the schedule is agreed
Dungeon recruitment: Group Finder, not this persistent note
Record what the group actually needs: who has reached the meeting area, who needs a connecting quest, and whether someone is saving a character for the shared session. Avoid publishing precise leveling promises from conflicting beta tables. For example, the supplied dungeon guide disagrees with itself on City of Dalaran and Krol'dok Stronghold level ranges. Those ranges should not become automated rejection rules.
Travel belongs in every dungeon brief. The supplied original developer interview reports that Forever Meeting Stones provide group-finding assistance rather than automatic summoning. State a meeting location and allow travel time; do not copy a Retail instant-entry expectation. Original interview
Blizzard also emphasizes threat, crowd control, and selective area damage. Ask which tools members actually have at their current level rather than demanding a max-level build from a beginner. A route-learning run can teach marked targets, recovery after a bad pull, and respectful pacing without becoming a damage competition. Combat philosophy
Turn Campsites, Professions, and Legacy Into Shared Preparation
Campsites create a practical question: what can this group contribute that it does not already have? The first profession objects become available early, and advanced blueprints add reasons to return to dungeons. A supply request can connect crafters and adventurers without becoming a full marketplace. Professions and camping
Use a planning note such as:
Camp: Before the dungeon route
Environment/build: Beta, current checked build
Fire: Basic — three crafted-object slots
Contributor A: Blacksmith object; compare with party's existing buff
Contributor B: Tailoring object; compare with existing buff
Contributor C: useful missing utility, confirmed by its crafter
Check: materials, skill requirement, object cooldown, safe location
Not assumed: persistent camp, permanent storage, or automatic placement
Do not spend all three slots recreating equivalent buffs the party already provides. The final choice belongs to the group in the current client. A temporary workshop can demonstrate more professions over time without implying ten people can each contribute an object to one Basic Campfire simultaneously.
For Legacy, distinguish earned account progress from this character's allocation. Blizzard identifies Professions, Adventure, and Resourcefulness trees. A shared earned total does not mean every alt has the same build, and the announced Hardcore interaction is deliberately asymmetric. Keep Hardcore records separate when that mode arrives rather than promising ordinary-character achievements automatically empower a new Hardcore character. Legacy rules
A Discord checklist can help members plan a profession milestone or next adventure. It cannot verify their points or determine whether a beta allocation remains legal after an update.
Maintain a Forever Knowledge Base, Not a Recycled Classic Rulebook
Use a simple label on guides: Official / Interview Reporting / Beta Observation / Community Plan, followed by the source, build or publication date, and last review. This lets a reader distinguish an announced system from a guild preference.
Race and class assumptions are an immediate example. Blizzard explicitly adds Gnome Priest, Human Hunter, Dwarf Shaman, Orc Mage, Troll Warlock, and Undead Paladin. Do not reject a Horde Paladin application or insist an Alliance group cannot include a Shaman. Skyborne faction selection also does not bypass the prohibition on cross-faction grouping. Race and class changes
Avoid attaching a permanent rotation to an onboarding role. The September 24 class changes already make some September 17 terminology stale. That patch also introduces partial-class testing for the built-in Cooldown Manager; it is not evidence that every class or addon function is ready. Dated beta changes
Loot explanations need the same care. Blizzard says eligible group members receive appearances from looted bind-on-pickup Uncommon and Rare gear, while Epic raid appearances remain tied to the individual receiving the item. Discuss upgrades and loot rules before a run rather than encouraging everyone to roll for an appearance they would already receive. The supplied Q&A reports GDKP is not allowed; do not recommend gold-bidding raids as the guild's organizing model. Appearance rules · Q&A reporting
Finally, use beta reports before blaming a Discord configuration. Blizzard's September 24 known-issues list warns that changing party composition can move players to a different world instance. Record the build and situation, regroup safely, and consult current official guidance. That is not proof that YourBot broke the party. Known issues
Add a Forever Journey & Camp Ledger Only When You Need It
Wayfarer Compact can start with the ten built-ins. A leveling checkpoint can live in a thread; a supply request can live in #supply-requests. Search the Marketplace before building a new plugin.
A custom tool becomes worthwhile when several recurring cohorts and many alts make those notes difficult to keep current. Forever Journey & Camp Ledger answers: which character is continuing this journey, where did the group stop, and which useful camp contributions are available?
It does not replace Group Finder's recruitment, Beacon's attendance/reminders, Tickets' private cases, or Announcements' broadcasts.
Copy-ready Plugin Builder specification
Plugin: Forever Journey & Camp Ledger
Purpose:
Keep persistent, manually maintained leveling checkpoints and campsite
preparation for World of Warcraft: Forever characters and cohorts.
Version 1 is a Discord-local planning tool, not a game integration.
No external network access. No Battle.net OAuth/API, addon bridge,
combat-log parsing, character lookup, game automation, or telemetry.
No background reminder job; Beacon owns scheduled reminders.
Never collect:
Battle.net passwords, authenticator/recovery codes, beta/friend keys,
session tokens, payment details, launcher files, or remote-access secrets.
Roles:
- Administrator: configure policy and authorized roles.
- Mentor: review only cohorts/records they are explicitly assigned.
- Camp Coordinator: manage assigned cohort camp plans.
- Member: maintain own characters and assigned public tasks.
- Guild Officer: only the guild-unit scope explicitly granted.
No title implies access to every member's private notes.
Character record:
- discord_guild_id and owner_discord_user_id
- full_in_game_character_name, or a planning alias before creation
- game_version: World of Warcraft: Forever
- environment: Beta | Launch Planning | Live
- account_game_region: member-entered, no geographic guessing
- ruleset: Normal | PvP | Roleplaying | Hardcore-Planned | Other/Review
- faction: Alliance | Horde
- beta_test_realm_label: optional
- language and preferred play window
- class, preferred role, secondary role
- self_reported_level and level_checked_at
- professions and self_reported_skill_notes
- known_camp_objects/blueprints: manually entered
- current_zone, quest_checkpoint, next_goal
- visibility: owner-only | selected cohort
- source_build_note and last_reviewed_at
- status: planned | active | paused | archived
Legacy notes:
- Optional earned-progress snapshot owned by the Discord member.
- Separate allocation notes on each character.
- Never deduct an alt's allocation from another character's note.
- Do not infer automatic Hardcore inheritance.
- Store a policy/source date rather than permanently hardcoding beta caps.
- Clearly label all values self-reported, not verified game data.
Cohort record:
- name, owner, invited members, assigned mentors
- environment, account region, ruleset, faction
- intended level range and shared quest/route checkpoint
- playing-ahead/catch-up agreement
- latest session summary and next preparation goals
- optional link to an existing Beacon event or Group Finder listing
- no duplicate signup, waitlist, or reminder system
Compatibility:
- Validate selected character records, not broad Discord interest roles.
- Reject a cooperative cohort with mixed environments, game regions,
rulesets, or factions under the currently documented policy.
- Beta test-realm mismatch requires review when applicable.
- Hardcore-Planned cannot be marked Live until policy is deliberately updated.
- A Battleground interest record is not evidence of premade compatibility.
- Matching stored values is a planning check, not game-side verification.
Camp plan:
- cohort, location note, build/source date
- fire type and object-slot budget; start with Basic = 3
- upgraded 5/10 slots only when the group confirms access
- contributors and manually selected objects
- required materials and assigned preparation tasks
- one object contribution per participant under current rules
- warn on duplicate/nonstacking buff categories
- record cooldown readiness as self-reported
- object capacity must never become a participant/voice limit
- no in-game placement, buff timer, material deduction, or inventory query
Knowledge notes:
- short finding, source URL/reference, publication/build date
- evidence_type: Official | Interview Reporting | Beta Observation | Plan
- last_reviewed_at
- stale warning derived when a page or command is opened
- no automatic scraping or source synchronization
Member interface:
My Characters, My Cohorts, Shared Checkpoints, Assigned Camp Tasks.
Show environment and compatibility above every action.
Do not reveal owner-only characters through search or autocomplete.
Mentor/coordinator interface:
Assigned Cohorts, Checkpoint Review, Camp Preparation, Stale Notes.
Private coaching notes separate from shared goals.
Proposed commands (new plugin commands, not existing built-ins):
/forever-character create|edit|mine|archive
/forever-cohort create|invite|checkpoint
/forever-camp plan|assign|review
/forever-notes review
Authorization and lifecycle:
- Authorize every read/write server-side using current Discord membership,
current configured roles, record ownership, and explicit cohort access.
- Scope all keys, searches, relations, and audit records by discord_guild_id.
- Reject caller-supplied guild IDs that disagree with authenticated context.
- Role removal, cohort removal, or leaving the Discord server must remove relevant
access on the next request; do not trust old cached page permissions.
- Direct-record links and command handlers use the same authorization.
- No bulk export in version 1; deny unimplemented export requests.
- Provide owner deletion and a disclosed retention policy.
- Audit grants, edits, archives, and policy changes without storing secrets.
Acceptance tests:
1. A member creates two alts with different roles and Legacy notes.
2. Another member cannot read an owner-only character by direct ID.
3. A Normal Alliance cohort rejects a PvP or Horde character.
4. A Beta record cannot silently become a Live character.
5. A fifth dungeon participant does not imply five Basic camp objects.
6. Two contributions by the same participant are rejected under current policy.
7. Nonstacking buff suggestions warn without claiming game verification.
8. Removing Mentor/cohort access blocks the next direct-record request.
9. Discord Server A cannot search, link, or edit Server B records.
10. Export requests fail closed; archived records leave active searches.
11. Stale notes are identified on read without background jobs.
12. No flow requests credentials or contacts a game service.
Review, test, and continue through the SDK
Review the generated plan before authorizing implementation. Inspect storage, commands, capabilities, record visibility, and the distinction between an account-level note and character-level data. No external-network capability should be necessary.
Test in a development Discord as an ordinary member, invited cohort member, Mentor, Camp Coordinator, and a user whose elevated access has been removed. Test direct links as carefully as the dashboard buttons. Passing manifest validation does not prove the access model is safe or the game facts are correct.
For continued development in Visual Studio Code, follow the current SDK workflow:
pip install yourbot-sdk
yourbot new forever_journey
cd forever_journey
yourbot dev --watch
yourbot validate
yourbot doctor
Use the Developer Portal's supported upload or repository workflow for the actual implementation; review the package structure and capability requests before installation. Marketplace publication is optional. The SDK documentation notes limitations on scheduled jobs for pooled marketplace execution, which is another reason to leave timed reminders with Beacon instead of promising custom background polling. SDK and deployment guidance
Run a Complete First-Week Member Journey
These are acceptance checks for the administrator to perform, not claims that an authenticated Discord or game session was executed for this guide.
| Scenario | Successful result |
|---|---|
| New beta participant | Can find status and compatible LFG without receiving officer or verified-game-access status. |
| Different faction/ruleset | Shares public discussion but is not silently added to an incompatible cooperative roster. |
| Dungeon learner | Finds a five-seat planning template, level/context notes, travel instructions, and a playing mentor inside the count. |
| Camp workshop | Ten attendees understand that a Basic fire has three object slots, not ten contributions. |
| Raid interest | December content remains planning; Onyxia's reported cap and final access requirements are flagged for review. |
| News correction | Staff can distinguish a September 17 snapshot from a September 24 change and correct public wording. |
| Private ticket | Only the intended staff team sees the case and its transcript destination. |
| Temporary voice | Capacity, access, ownership transfer, and empty-room cleanup work for ordinary members. |
| Optional ledger | Character ownership and cohort permissions hold after role revocation and direct-link access. |
Frequently Asked Questions
Is World of Warcraft: Forever live yet?
It is in beta at this guide's September 25, 2026 cutoff. Blizzard announces November 4 launch and December 9 raid availability. Do not describe launch raids as current beta reclears. Schedule
Does realmless mean everyone can group together?
No. Cooperative grouping still depends on the applicable game region, ruleset, and faction. Shared Battleground reporting does not establish universal cross-ruleset premade access. Blizzard explanation · Q&A reporting
Should I select YourBot's WoW Mythic+ template?
Not for Forever. The inspected WoW starter contains Retail-style Mythic+ terminology. Create a Forever dungeon template and separate raid plans instead; preserve those starters only where they serve actual Retail members.
Are campfires three-, five-, or ten-player groups?
No. Those capacities describe crafted objects at campfires. They do not set group attendance or Discord voice size. Campfire rules
Are Undead Paladins and Dwarf Shamans actually part of Forever?
Yes. Both are among Blizzard's announced new race/class combinations. Do not reuse the old faction-exclusive Paladin/Shaman assumption. Class changes
Will YourBot track my character, quests, and Legacy points?
Not through the built-in services described here. The optional ledger stores member-entered coordination notes, not Blizzard account data or authoritative progression.
Can Social Feeds automatically provide every Forever beta update?
No verified complete Forever feed is established here. The Warcraft YouTube subscription is supplementary; maintain manual checks of official Forever news and edited beta topics. Feed limitations
Build the Discord Around the People Taking the Same Road
Forever's Discord should make the next shared journey easier: matching compatible characters, reaching a dungeon together, preparing useful campsite contributions, and helping someone catch up without erasing their sense of discovery. Raid organization matters, but it should not consume a community still learning the road to 60.
Use Start Your Server to establish that foundation, then finish and test each service. Keep beta findings dated, guild access deliberate, and gameplay claims tied to the correct source. Add Plugin Builder only when persistent cohort and campsite planning outgrows ordinary threads—not because every community needs another system to maintain.