roblox-teleport

Official sources:

• https://create.roblox.com/docs/en-us/reference/engine/classes/TeleportService
• https://create.roblox.com/docs/en-us/projects/teleport
• https://create.roblox.com/docs/en-us/reference/engine/classes/TeleportOptions
• https://create.roblox.com/docs/en-us/reference/engine/classes/TeleportAsyncResult
• https://create.roblox.com/docs/projects/teleport (multi-place architecture)

TeleportService moves players between places and servers. The modern entry point is TeleportAsync (server-only); the older Teleport (client), TeleportPartyAsync, TeleportToPlaceInstance, TeleportToPrivateServer, and TeleportToSpawnByName methods are deprecated. Use TeleportAsync() instead. For client-initiated teleports, fire a RemoteEvent to the server and let the server call TeleportAsync(); do not call Teleport() from the client for new work, even if the place is configured as "Fully Open." See the migrate to secure teleports guide.

Cross-reference:

• roblox-datastores/SKILL.md: handoff pattern for player data across teleports.
• roblox-networking/SKILL.md: server authority, rate limiting, and the security model around teleport requests.
• roblox-core/SKILL.md: services and script contexts.

Multi-place architecture

A universe (experience) can contain multiple places. Each place has its own PlaceId; the universe has a UniverseId (exposed as game.GameId). The primary place is the one players join from the Roblox app's main entry point.