Multiplay Hosting integration was removed in com.unity.services.multiplayer 2.0.0 and formally documented as removed in 2.1.0. If you are on 1.2.1 you will already see compiler obsolete warnings on Multiplay Hosting APIs — those are the signal to refactor before upgrading to 2.x.
The following are removed entirely and will cause build failures if still in use:
- Multiplay Hosting pool type in the SDK session matchmaking APIs — any calls that referenced the Multiplay Hosting path in
IMultiplayerServicesession flows are gone. - IMultiplaySessionManager and associated server-side APIs — if your server used these to manage Multiplay-hosted sessions, those need to be replaced with the Cloud Code allocation flow.
- GetMatchmakingResults for non-backfill Multiplay Matchmaking — the extension method behaviour for Multiplay-specific matchmaking results is removed.
On the client, if your polling code was pattern-matching on MultiplayAssignment and you've migrated the pool to Cloud Code, switch to IpPortAssignment:
// Before — Multiplay-hosted pool, matching on MultiplayAssignment
if (ticketStatus.Assignment is MultiplayAssignment ma)
ConnectToServer(ma.Ip, ma.Port.Value);
// After — Cloud Code pool returning IpPort
if (ticketStatus.Assignment is IpPortAssignment ip)
ConnectToServer(ip.Ip, ip.Port);The pool's Hosting type setting and what your client expects must stay in sync:
- If you are moving off Multiplay Hosting entirely — switch the pool from Multiplay Hosting (Deprecated) to Cloud Code, and update your client's polling code to handle
IpPortAssignment(or whichever assignment type your allocator returns). Leaving the pool in backward compat mode while the client only handlesIpPortAssignmentwill break assignment delivery. - If you cannot update your client yet — keep the pool set to Multiplay Hosting (Deprecated) so the client continues to receive
MultiplayAssignment. Your allocator module does not change in either case.