Hi Creators,
We’re launching server ID targeting for teleports, giving you more granular control over where your players go. Until now, teleports to reserved servers had fragmented paths, and VIP server teleports had undefined behavior, automatically inferred in some cases and forgotten in others.
This update simplifies the Teleports API, while offering you more granularity in the server you wish to teleport to. Two new properties on TeleportOptions, ReservedServerId and VipServerId, let you target a server type, by the game.PrivateServerId of the target server.
What you need to know:
TeleportOptionsgainsReservedServerIdandVipServerId, both plain GUID strings.- You can teleport players to VIP servers, including group teleports, to any place in your experience.
- Existing access codes and fields won’t break and will still be functional, but will now show deprecation messages.
Target a Private Server Directly
ReservedServerId sends players to a reserved server, and VipServerId sends them to a VIP server. Follow these steps:
-
For a new reserved server, you can use any random GUID - we recommend using
HttpService:GenerateGUID(false). For an existing reserved server, store the existing GUID and reuse it, or find this on an existing Reserved Server’sgame.PrivateServerId. For a VIP server, you can find this when they join fromgame.PrivateServerId. -
Set
ReservedServerIdorVipServerIdon aTeleportOptionsinstance. -
Pass the options to
TeleportService:TeleportAsync().
-- Teleport to a new Reserved Server
local TeleportService = game:GetService("TeleportService")
local HttpService = game:GetService("HttpService")
local options = Instance.new("TeleportOptions")
options.ReservedServerId = HttpService:GenerateGUID(false)
TeleportService:TeleportAsync(placeId, {player}, options)
A successful private server teleport returns a TeleportAsyncResult with PrivateServerId, which matches the ReservedServerId or VipServerId you passed in. Set at most one targeting field, because passing more than one raises a Luau error. You also no longer need to store PrivateServerId to ReservedServerAccessCode mappings, so you can teleport to known Reserved servers on the fly. For the full breakdown, read the TeleportService documentation.
Keep Players in Their VIP Servers Across Every Place
We now support explicitly targeting teleports to VIP servers. On a player’s join to a VIP server, grab the game.PrivateServerId. You can then set this in VipServerId in TeleportOptions and pass this into TeleportAsync() to initiate a teleport to that server. Players may create new VIP servers, close old ones, join a friend’s VIP server instead of their own, etc. – so make sure to handle TeleportInitFailed in these cases. We recommend that you associate this information with players in TeleportData to pipe it through teleports.
This now means that all places within your Universe are able to have VIP servers, not just the root place. This should greatly simplify the process of keeping players who purchase VIP servers in a fully private experience.
If a player is not allowed to join the server, TeleportInitFailed is raised.
Example: Teleport From VIP → Reserved → VIP
-- On the VIP server: detect it, and keep ID when teleporting players out
local TeleportService = game:GetService("TeleportService")
local Players = game:GetService("Players")
local function isVipServer()
return game.PrivateServerId ~= "" and game.PrivateServerOwnerId ~= 0
end
if isVipServer() then
local options = Instance.new("TeleportOptions")
options:SetTeleportData({ vipServerId = game.PrivateServerId })
options.ReservedServerId = HttpService:GenerateGUID(false)
TeleportService:TeleportAsync(otherPlaceId, Players:GetPlayers(), options)
end
-- On any other server in the experience: teleport the player back to a VIP server
local TeleportService = game:GetService("TeleportService")
local Players = game:GetService("Players")
local player = Players:GetPlayers()[1]
local vipServerId = player:GetJoinData().TeleportData.vipServerId
local options = Instance.new("TeleportOptions")
options.VipServerId = vipServerId
TeleportService:TeleportAsync(yetAnotherPlaceId, {player}, options)
Deprecations
Next week, we’ll be deprecating ShouldReserveServer and ReservedServerAccessCode fields in TeleportOptions, and TeleportService methods ReserveServer(), ReserveServerAsync(), and TeleportToPrivateServer(). These will continue to function but should not be used for new work. Reserving a server before initiating the teleport has no effect, and is equivalent to passing a random GUID to ReservedServerId in TeleportOptions. Previously created access codes will remain valid indefinitely.
Known Issues
If a VIP server is joined via link, they may see that they lose authentication if teleported away from the root place. This can be resolved by advising players to update Roblox.
Edit: VIP servers joined via link code are known to fail for VIP teleports to non-root places with Secure Teleports enabled for the Universe. We are working on a fix for this, thanks for the patience! Teleports to the root place with VipServerId set should not be affected.
What’s Coming Next
Teleports back to the root place will default to a VIP server for players that have used the VIP feature this session. We will also add a boolean field in TeleportOptions which will allow you to opt-out of automatic VIP teleports. This will grant you the overrides to force certain teleports to be to public servers, where they would have been automatically upgraded to VIP.
Resources
- TeleportService | Documentation - Roblox Creator Hub
- TeleportOptions | Documentation - Roblox Creator Hub
- Teleport between places | Documentation - Roblox Creator Hub
- Teleport to private servers | Documentation - Roblox Creator Hub
We’re planning more improvements to private servers in the upcoming months, and would appreciate questions and feedback. Thank you!
FAQs
Will my existing code break?
No. Existing flows for reserving servers are still functional, and base64 access codes are accepted indefinitely. New calls to ReserveServerAsync will eventually generate a random GUID. ReservedServerAccessCode will accept both base64 access codes and GUID strings to remain backwards compatible.
What happens if a player can’t join the VIP server I chose?
TeleportInitFailed callback is fired, and the player is presented with an error modal saying the server is restricted.
Can I teleport a group to a VIP server?
Yes. Pass multiple players with the same VipServerId. Each player is checked independently at connect time, so players without access fail individually with TeleportInitFailed while the rest teleport normally.
What if the new properties don’t work on my server?
Your server may be running an older version. The teleport fails with a message indicating Access Code V2 isn’t enabled. Restarting the server should bring up the server version to the latest.
How will VIP authentication work?
VIP servers can be shared with others through a “Friends Allowed” toggle, an allowlist, or joins via a Link code. As long as one of these is valid at the moment of the teleport, it will succeed. Be aware that VIP server owners may change this at any point and remove a player’s authentication, so TeleportInitFailed should be handled in this case.


