Roblox adds TeleportAsync testing inside Studio
Roblox now supports TeleportAsync testing inside Studio without publishing. Update Studio and check server-ID differences before validating travel between places.
Roblox’s November 5, 2026 announcement adds TeleportAsync support to Studio’s Test and Team Test modes. Developers building travel between places can now debug teleports without publishing or joining live servers. Roblox says developers must update to the latest Studio version to use the feature.
Debug across places
A teleport opens the destination place in a new test server. According to Roblox, server inspection, breakpoints and the device simulator remain available there. Assistant and Studio MCP agents can also run playtests across teleports and inspect destination output. Supported flows do not require changes to production code.
Our recommendation is to use this workflow for checking party arrivals and transferred loadouts before live testing. It removes the publishing step from that debugging loop, but Studio’s server behavior still needs careful interpretation.
Check the testing limits
Roblox limits testing to TeleportAsync and destinations within the starting experience, sharing its game.GameId. Deprecated Teleport, TeleportPartyAsync and TeleportToPlaceAsync methods are unsupported; Roblox provides a migration guide. TeleportService:GetPlayerPlaceInstanceAsync also remains unsupported. VIP teleports fail in testing because Team Test servers have no owner.
In local Test, game.PrivateServerId and game.JobId stay empty, including for private-server teleports. Every Team Test server is private, so game.PrivateServerId is nonempty even for public teleports. Roblox also warns that ReservedServerId can differ from the destination’s game.PrivateServerId in Team Test, although they match in production. Reuse the requested ReservedServerId when sending additional players to that reserved server.
We’d start by testing a lobby-to-match flow this week in both modes. Confirm the group arrives together, inspect its transferred data and check destination breakpoints. Review any branch that treats a nonempty game.PrivateServerId as proof of a private teleport; Team Test cannot reproduce that distinction.