You do not need an in-game alliance to run a joint raid night. You need a shared clock, a shared lockout state, and a shared fallback plan. The rest is logistics.
This runbook is for guild officers on European servers who want to co-host a raid with another guild without merging rosters, without a formal charter, and without pretending the time zones do not exist. It assumes 20–200+ member guilds, mixed languages, and the usual volunteer-leadership constraints: people have jobs, families, and unreliable Tuesday evenings.
I am not going to pretend there is a single tool that solves this. There is not. What follows is a mechanism-first approach: name the constraint, pick the tool, state the failure mode.
Step 1: Fix the clock before you fix the roster
GMT, CET, and EET are not three time zones in the way people casually use the terms. They are three offsets that shift independently around daylight saving transitions. The UK switches on the last Sunday in March and the last Sunday in October. Most of the EU switches on the last Sunday in March and the last Sunday in October as well, but not all — and the gap weeks matter.
For a joint raid night, the only clock that matters is the one written in the event description. Pick one and never deviate:
- Server time if both guilds are on the same server or same logical data centre.
- UTC if they are not.
Do not write “20:00 CET” in one place and “19:00 GMT” in another. Write “19:00 UTC” and let each guild convert once, in their own channel, with their own local label. The failure mode here is predictable: someone shows up an hour late during the transition weeks and blames the other guild. That is not a personality problem. That is a documentation problem.
Final Fantasy XIV publishes its own event times in multiple offsets simultaneously — for example, the FFXV collaboration event runs “Thursday, 24 September 2026 at 8:00 (GMT) / 9:00 (BST) / 18:00 (AEST)” — which is a useful model. Copy that pattern. List every offset your roster actually uses, in the same line, in the same order, every time.
Step 2: Check whether the content is even cross-guild compatible
This is where most joint raid nights die before they start. The content has to be accessible to both rosters at the same time, on the same lockout, with the same prerequisites.
In Final Fantasy XIV, cross-world party recruitment has historically been limited to players on the same logical data centre. Square Enix announced at Fan Festival 2026 in Berlin that same-region player matching will expand matchmaking and party recruitment to cover all players on the same physical data centre, starting with the Japan data centre on 13 October 2026, with rollout to other data centres to follow. Until that reaches your data centre, a joint raid night between Chaos and Light is not a scheduling problem — it is a platform limitation. Verify the current state on the Lodestone before you promise anything.
In Lost Ark, the Western release has undergone server merges — the 2026 Server Merge Details page describes consolidation across both regions in two phases beginning 26 August, with a revised merge date of 9 September noted in a later team update. Server merges change which guilds can share a roster and which cannot. If you are planning a joint night across two servers that are about to merge, wait. If they are not merging, confirm the cross-server raid rules for the specific raid tier before you build a signup sheet.
In World of Warcraft, cross-realm raiding has been possible for years for most current content, but the exact rules vary by difficulty and by whether the group is premade or queued. I cannot verify the current patch-specific rules from the sources retrieved for this article, so treat this as a check-before-you-commit item, not a settled fact.
In Elder Scrolls Online and Guild Wars 2, the relevant constraints are different again. ESO’s megaserver structure means “server” is less of a barrier than campaign or alliance membership. For GW2, I cannot verify the current cross-server raid access rules from the sources retrieved for this article, so treat this as a check-before-you-commit item, not a settled fact. The point is procedural: confirm the access rule for your game, your region, and your current patch before you confirm the date.
Step 3: Pick the coordination surface, and name its failure mode
There is no cross-game alliance chat. Every joint raid night runs on a stack of external tools plus whatever in-game surface the game provides. Here is the honest inventory:
| Surface | What it does well | Failure mode |
|---|---|---|
| Discord (shared channel) | Real-time coordination, voice, persistent history | Notification fatigue; people mute the channel and miss the ping |
| In-game calendar (WoW, FFXIV) | Visible to people who do not use Discord | Does not sync across guilds; each guild sees its own copy |
| Google Sheets / shared doc | Single source of truth for signups and roles | Link rot; people edit the wrong tab; no push notification |
| In-game community finder (FFXIV) | Cross-world visibility within a data centre | Not a scheduling tool; no recurring event support |
| Raid-Helper or similar | Signup, role assignment, reminders | Requires both guilds to adopt it; one holdout breaks the chain |
The mechanism that works is boring: one shared document as the source of truth, one Discord channel as the notification layer, one in-game calendar entry as the backup. The failure mode is always the same — someone updates the document and does not ping the channel, or pings the channel and does not update the document. Assign one person per guild to own the sync. Not a committee. One person.
Step 4: Build the runbook itself
Here is a copy-paste template. Fill it in, pin it, and do not let it drift.
JOINT RAID NIGHT — [GAME] — [DATE] — [UTC TIME]
Guild A: [name, server, region]
Guild B: [name, server, region]
Content: [raid name, difficulty, patch]
Lockout state: [fresh / partially cleared / specific boss]
Prerequisites: [item level, attunement, quest, etc.]
Signup deadline: [UTC time, 48h before start]
Signup sheet: [link]
Voice channel: [link]
In-game calendar: [created by whom, on which guild]
Raid leader: [name, guild]
Loot rules: [need/greed, council, DKP, etc.]
Language: [primary language for callouts]
Fallback language: [secondary, if primary fails]
Start time conversions:
UTC: [time]
GMT/BST: [time]
CET/CEST: [time]
EET/EEST: [time]
Fallback plan if [Guild B] cannot access the instance:
[alternative content or reschedule rule]
Post-raid debrief: [UTC time, same channel]
The fallback plan is not optional. If the cross-server access rule turns out to be different from what you assumed, you need a second activity ready. A joint night that collapses into “well, we tried” costs you more attendance than a night that pivots to something smaller but still happens.
Step 5: Run the night, then run the debrief
The raid itself is the easy part. The debrief is where retention is won or lost.
Thirty minutes after the raid ends, in the same voice channel, ask three questions:
- Did the start time work for you? If not, what would have worked better?
- Was the language mix a problem for callouts? If so, where exactly?
- Would you do this again with the same guild? Why or why not?
Write the answers down. Not in your head. In the shared document. The next joint night starts from those answers, not from scratch.
The failure mode here is the silent debrief — everyone says “good run” and logs off, and you learn nothing. If nobody answers question 3 honestly, you have not run a debrief. You have run a victory lap.
What this runbook does not solve
It does not solve personality conflicts. It does not solve a guild that consistently shows up late. It does not solve the fact that some games simply do not support cross-guild instanced content at the difficulty you want.
What it does solve is the class of problems that look like personality conflicts but are actually documentation failures: time zone confusion, lockout mismatches, signup drift, and the slow erosion of trust that happens when people show up and nothing works.
Fix the mechanism first. The rest gets easier.
FAQ
Do we need a formal alliance or charter?
No. A shared document and a named point of contact per guild is enough for a single joint night. A charter becomes useful when you are running recurring events across three or more guilds, because that is when decision rights start to matter.
What if one guild uses Discord and the other does not?
Pick one surface and require both guilds to use it for this event. If that is not possible, use the in-game calendar as the primary and accept that reminders will be weaker. Do not run two parallel coordination channels. That is how information forks.
How far in advance should we schedule?
Two weeks minimum for a first joint night. One week for a repeat. The signup deadline should be 48 hours before start so you have time to adjust roles or cancel without wasting people’s evenings.
What if the cross-server rules change mid-planning?
Check the official patch notes and the relevant game’s news page in the week before the event. If the rule changes, use the fallback plan. Do not try to negotiate with the platform.
Is this worth doing for a 20-member guild?
Yes, if the alternative is cancelling raid nights because you cannot fill a roster. A joint night with a similarly sized guild is often more reliable than pugging, because both sides have a reason to show up.