Roblox adds explicit VIP and reserved server teleport targeting
Roblox now supports explicit reserved and VIP server targeting through TeleportAsync(). Test private-server travel and prepare new code for the announced deprecations.
Roblox has added ReservedServerId and VipServerId to TeleportOptions for released games, according to its October 28, 2026 announcement. Developers can now explicitly target reserved or VIP servers through TeleportAsync(). The change affects private-server travel across places, including group teleports to VIP servers anywhere within an experience.
Preserve the private destination
Roblox says both properties take GUID strings. Read game.PrivateServerId to identify an existing destination; for a new reserved server, Roblox recommends HttpService:GenerateGUID(false). Set at most one targeting field, since multiple targeting fields cause a Luau error. A successful private-server teleport returns the matching PrivateServerId in TeleportAsyncResult.
Our recommendation is to use this explicit destination handling for trips from a VIP lobby into a reserved match and back. Roblox recommends carrying the VIP server ID with each player through TeleportData. This removes the need to maintain mappings between reserved-server IDs and access codes.
Test access and migration
We'd start by testing that round trip this week with a group whose members have different access permissions. Roblox checks each player separately when connecting: unauthorized players trigger TeleportInitFailed, while authorized players can continue. Handle that callback because owners can revoke access. If link-based VIP joins lose authentication after teleporting away, Roblox advises updating the client. Older servers may reject the properties with an Access Code V2 message; restarting should update them.
Roblox schedules deprecation for next week for TeleportOptions.ShouldReserveServer, TeleportOptions.ReservedServerAccessCode, and TeleportService methods ReserveServer(), ReserveServerAsync(), and TeleportToPrivateServer(). These remain functional but should not be used for new work. Previously issued access codes stay valid indefinitely. Our recommendation is to audit teleport wrappers before adding new flows, rather than treating this as an immediate compatibility break.