A shared launch starts with a few clear agreements, not a large roster spreadsheet. Write down where you intend to play, when you can meet, who confirms the final plan and what happens when someone arrives late. This checklist is for several days of coordination; the group-post template is for a single session.
Official information checked September 30, 2026. Blizzard's Forever announcement gives November 4, 2026 as the launch date. Confirm the latest regional timing with Blizzard before committing to a calendar invitation. A community plan does not establish a local launch hour.
Agree on region, character ruleset and faction
Start with region, faction, language, preferred activities and the hours people can reliably play. Ask which choices are essential and which are flexible. A group of friends may prefer staying together over a particular ruleset; another may care more about its usual playstyle. Make that tradeoff explicit instead of assuming everyone agrees.
Our community welcomes both factions and PvE, PvP and RP interests. Those interests are not the same as a character ruleset. Read playing with friends together before creating characters; it links Blizzard's grouping restrictions and distinguishes future Hardcore plans from launch choices.
Name a decision maker and an update location
Choose who will check official ruleset information and announce the final decision. Mark the ruleset Unconfirmed until everyone agrees. Keep one readable plan with a last-reviewed date and a public contact handle. A Trader market identifier is not a realm choice for your characters.
Do not scatter conflicting versions through several channels. Pin or link the maintained plan, explain changes, and ask players to acknowledge decisions that affect them. There is no need to collect real names, account credentials or personal work schedules.
Make room for ordinary life
Separate launch-night availability from a sustainable weekly schedule. Decide when the group stops, whether people can join later, and what happens if someone misses a day. A player with work or family commitments should not have to promise an unrealistic first week just to belong.
Agree on pace, breaks, spoilers and voice expectations. Identify roles people would like to try, but do not present speculative balance or an untested composition as settled advice. For a long-term roster, use the guild-selection checklist to discuss attendance and expectations.
Fill in the shared plan
This is a blank worksheet, not a scheduled community event. Complete it with consenting participants. Downloading it does not publish a listing, reserve a place or create a Discord event.
Plan owner and public contact:
Last reviewed (date):
Region / faction / language:
Character ruleset: Normal / PvP / Roleplaying / Hardcore planned / Unconfirmed
Official source and date checked:
Who confirms the final ruleset and faction:
Usual hours and named time zone:
First shared session (date / time / UTC):
Hard finish and breaks:
Who can join later or miss launch night:
Pace, goals and spoiler preferences:
Roles we want to try (not guaranteed slots):
Voice / text preferences:
Shared meeting and update location:
Access checks each player handles privately:
Backup plan if login or the chosen ruleset is unavailable:
When to stop waiting and reschedule:
Next check-in date:
Rehearse the practical details
Before the first session, ask each player to check their own access and installation through official services. Confirm the intended contact point works on mobile as well as desktop. Put the calendar date and a named time zone beside the start time, then check its UTC equivalent for that date.
If the group agrees to a fixed local-evening schedule, say so. Do not silently convert it into a fixed UTC schedule when clocks change. Our session guide includes the time-zone check.
Have a fallback that does not split the group
Agree how long to wait for access or a delayed participant and who can decide to postpone. Do not promise a transfer or cross-region grouping to repair a mismatched plan. Confirm compatibility before investing time in characters, and recheck official information when a test build changes.
A reasonable fallback can simply be another date and a short conversation to keep everyone informed. Announce a cancellation in every place where the session was advertised. Today an ordinary Discord edit does not automatically change a website listing.
Turn the plan into real activity
When details are confirmed, advertise one achievable session through looking for group, or maintain a complete guild listing for a recurring roster. Both use the community's review process. A Discord-only welcome conversation belongs in Discord or an announcement, not a falsely labelled dungeon or raid.
After the first session, ask what worked and what needs changing. A factual recap with consenting participants is more useful than claiming a successful launch before it happens. You can use this plan with your own guild or friends; joining KFC is not required.
Written by WoW Forever Discord Team. About our organizers · Suggest an article correction in Discord