Keep both guilds in their own servers. Link them, agree which server's caller runs the fight, and start a cross-server relay from either side so one caller reaches every party in both. Party leaders on both sides can still talk back.
Don't merge the servers#
The usual fix for an alliance fight is to ask one guild to join the other's server for the night. Half of them can't find the channels, roles are wrong, and the permissions you set up so carefully don't apply. Keep each guild where it is.
Link the two servers#
On the Alliance plan, one server creates a single-use invite code and the other pastes it in. The second server gets Guild Master — 12 speaker channels — at no extra cost. Alliances has the step-by-step.
Decide who calls#
Before the fight, agree which server's caller runs it. The cross-server relay takes the caller from the server that starts it and plays them into the speaker channels of both. Whoever starts it, starts the call.
Both servers set up
Each server needs its own speaker channels and roles, like any normal setup.
Start cross-server
The calling server types
/start-cross-server. Either server can start one;/stop-cross-serverends it.Check both sides
Ask one party on each server to confirm they hear the caller.
Talking back across the alliance#
Party leaders on both servers can use their priority key to reach the caller, exactly as they would at home. The same etiquette applies — see party leaders: set up your priority key.