> For the complete documentation index, see [llms.txt](https://pmc-docs.gitbook.io/pmc-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pmc-docs.gitbook.io/pmc-docs/pmc-nodes/teleport.md).
# Teleport
\
\ Description
> This function facilitates the snapping process during a teleportation event. It does not move the Pawn by itself; instead, it prepares the physics component to "snap" to a new location by bypassing network interpolation, ensuring the transition is instantaneous on all clients without visual "sliding."
***
Technical Logic & Networking
> * Movement Reset: Upon execution, the function calls `Stop Physical Movement` to clear existing velocity, ensuring the object doesn't carry old momentum to the new location.
> * Network Snapping: It sets a `Pending Teleport` flag to True. This internal flag tells the PMC replication system to send a specific network signal (Flag).
> * No Interpolation: On the client side, this signal forces the object to "snap" immediately to the target position instead of smoothly interpolating between the old and new coordinates.
> * Auto-Cleanup: The system automatically resets the `Pending Teleport` state to False immediately after the snap is processed to resume normal movement logic.
🛑 Note: This Teleport function is specifically designed to work with the PMC In-Built Client Authoritative system. It utilizes internal flags to handle network snapping and bypass interpolation. If you are using Custom Replication mode, you may need to handle the snapping logic according to your specific network architecture.
**Example:**