Roblox Studio Adds Native Teleport Testing Without Publishing

What Changed

Roblox has shipped a long-requested workflow improvement: TeleportAsync now executes inside Studio's Test and Team Test modes. Until this update, verifying a teleport meant publishing every place involved, joining a live server, adding print statements, republishing, and repeating. Now a developer presses Play, the teleport fires, and the destination place spins up as a new test server — all without leaving Studio.

The feature landed in the Studio build dated November 5, 2026. Creators must update to the latest Studio version to use it.

Supported Flows

The announcement lists several end-to-end scenarios that now work locally:

• Lobby to match — Send a group from a lobby place into a match place and confirm they arrive together.
• Data passing — Verify that loadouts, party info, or round settings sent via TeleportOptions arrive intact.
• Reserved servers — Teleport players to a reserved server, then send additional players to the same instance using ReservedServerId.
• Hub worlds — Move between a hub and its minigame or level places, and back again.

All teleport types supported by TeleportAsync function identically to production; no code changes are required.

Tooling Carries Over

Studio's debugging suite follows the player across the teleport boundary:

• Server inspection — View the destination server's state after arrival.
• Debugger — Breakpoints remain active in the destination place.
• Device simulator — Test teleports on simulated mobile and console form factors.

MCP Server Automation

The Studio MCP server (used by assistants such as Claude or Cursor) can now drive playtests that cross place boundaries. An agent can start a playtest, trigger a teleport, read the destination server's output, and apply fixes — again without publishing or joining a live server. Example prompts from the announcement:

• "Playtest the lobby, teleport into the match, and check the server output for errors."
• "Teleport a player to the arena place and confirm their loadout came through."

Assistant-driven playtests in Studio gain the same cross-teleport capability.

Limitations to Know

Several constraints apply while testing:

• TeleportAsync only — Deprecated methods (Teleport, TeleportPartyAsync, TeleportToPlaceAsync) are not supported. Teams still on those APIs should follow the migration guide.
• PrivateServerId behavior — In local Test mode, game.PrivateServerId and game.JobId are always empty, even for "private" teleports. In Team Test, all servers are private, so PrivateServerId is never empty, even for public teleports. Code that checks game.PrivateServerId ~= "" to detect privacy will misbehave in test.
• ReservedServerId mismatch — In production, the destination server's PrivateServerId matches the requested ReservedServerId. In Team Test they can differ. Reuse the same ReservedServerId when testing repeated entry to a reserved server rather than reading back PrivateServerId.
• VIP teleports fail — Team Test servers have no owner, so VipServerId teleports are rejected.
• Same-experience restriction — Testing only permits teleports to places sharing the same game.GameId.
• GetPlayerPlaceInstanceAsync unsupported — This method remains unavailable in test modes.

What's Next

The Studio team is soliciting feedback on bugs and future improvements. Given the RDC timeline mentioned in community discussion ("early next year"), this release arrives ahead of the previously communicated schedule.