Teleport System #

• Overview
• Core Concepts
  • What is the Teleport System?
  • Use Cases
  • Level Streaming Support
• Components
  • Teleport Location Actor
  • Teleport Component (Player Controller)
  • Teleport Interface
• Setting Up Teleport System
  • Placing Teleport Locations
  • Adding Teleport Component
  • Configuring Fade Widgets
• Teleport Location Actor
  • Persistent Level Requirement
  • Teleport Interface Implementation
  • Teleport Validation Checks
• Teleportation Process
  • Teleport Flow Overview
  • Fade-In Phase
  • Level Loading Phase
  • Movement Freeze
  • Fade-Out Phase
• Teleport Validation
  • Can Teleport Interface Function
  • Common Validation Checks
  • Custom Validation Logic
• Integration with Other Systems
  • Fast Travel System
  • Quest System
  • Save/Load System
• Example Implementations
  • Basic Teleport Points
  • Fast Travel System
  • Dungeon Exit Portals
• How To Guides
  • Setting Up Basic Teleportation
  • Creating Fast Travel Points
  • Adding Custom Validation
• OVERVIEW

The Teleport System is a robust teleportation solution that supports level streaming, enabling players to teleport to unloaded areas safely and seamlessly.

Core Features:

• Teleport to unloaded areas (World Partition/Level Streaming support)
• Automatic level loading before teleportation
• Player movement freeze during loading
• Optional fade-in/fade-out transitions
• Validation interface for teleport conditions
• Always-loaded teleport location references (persistent level)
• Safe teleportation with loading guarantees

Common Applications:

• Fast travel systems
• Dungeon entrances/exits
• Portals between areas
• Waypoint systems
• Level transitions
• Respawn points
• Quest teleportation

Why This System?

Standard teleportation breaks when teleporting to unloaded levels. This system:

• Ensures level is loaded before teleporting
• Freezes player movement during loading
• Provides visual feedback with fade transitions
• Validates teleport conditions before initiating
• Maintains references to teleport locations in persistent level

Core concepts #

What is the Teleport System? #

The Teleport System manages safe player teleportation, especially to areas that may not be loaded.

Two Main Components:

• Teleport Location Actor (placed in persistent level):
  • Marks valid teleport destinations
  • Always loaded and accessible
  • Implements validation interface
  • Stores location and associated level
• Teleport Component (on Player Controller):
  • Initiates teleportation
  • Handles fade transitions
  • Manages level loading
  • Freezes/unfreezes player movement

The Problem This Solves:

Standard Teleportation:

1. Call “Teleport to Location”
2. If level not loaded → Player falls through world or crashes
3. No visual feedback during transition
4. Movement enabled immediately (can fall/die during loading)

Teleport System Solution:

1. Check if can teleport (validation)
2. Start fade-in transition
3. Freeze player movement
4. Teleport to location
5. Wait for level to load
6. Once loaded, unfreeze movement
7. Start fade-out transition
8. Player can move in fully loaded level

Use Cases #

The Teleport System can be used in various gameplay scenarios:

Common Applications:

• Fast Travel System: Teleport to discovered landmarks
• Dungeon Entrances/Exits: Transition between overworld and dungeons
• Portal System: Interactive portals between distant locations
• Quest Teleportation: Move players to quest objectives
• Respawn System: Teleport to respawn points on death
• Waypoint System: Player-placed or predefined waypoints
• Cutscene Transitions: Move players for story sequences

The system handles level streaming and validation automatically for all these use cases.

Level Streaming Support #

The Teleport System is designed to work with World Partition and Level Streaming.

The Challenge:

In open world games with level streaming:

• Not all areas are loaded simultaneously
• Teleporting to unloaded area causes errors
• Need to ensure target location is loaded before teleporting

The Solution:

Teleportation Flow with Level Streaming:

1. Player initiates teleport to Location A
2. Teleport Component checks if Location A's level is loaded
3. If not loaded:

 - Start loading level
 - Freeze player movement
 - Show fade-in effect
 - Teleport player to location (while still frozen)
 - Wait for level to finish loading

1. Once level loaded:

 - Unfreeze player movement
 - Show fade-out effect

1. Player can now move in fully loaded area

Why Teleport First, Then Wait?

The player is teleported to the location immediately, but movement is frozen:

• Player is at correct location for level streaming
• Level streaming system knows what to load (area around player)
• Player can't fall or move during loading
• Once loaded, fade-out reveals fully loaded environment

Persistent Level Requirement:

Teleport Location actors must be in persistent level because:

• Persistent level is always loaded
• Teleport locations are always accessible as references
• Can query teleport locations without loading their target levels
• Ensures reliable references throughout game session

---

Components #

Teleport Location Actor #

BP_TeleportLocation (or similar) marks a valid teleport destination.

Must Be Placed in Persistent Level:

• Persistent level is always loaded
• Guarantees teleport location reference is always valid
• Can be queried from anywhere without loading levels

Key Properties:

• Location: Transform where player will be teleported
• Associated Level: Which streaming level or world partition area this location is in
• Display Name: Name for UI (e.g., “Town Square”, “Dark Forest”)
• Teleport Icon: Icon for fast travel UI
• Validation Settings: Requirements for teleportation

Interface Implementation:

Implements BPI_Teleport interface with:

• Can Teleport: Returns true/false if teleportation is allowed
• Get Teleport Transform: Returns target location and rotation
• On Teleport Complete: Called when player successfully teleports

Visual Representation:

In editor, shows:

• Teleport destination marker
• Arrow indicating player forward direction
• Debug name text
• Associated level information

Teleport Component (Player Controller) #

Teleport Component (on Player Controller) handles the teleportation process.

Component Location:

Add to BP_PlayerController to give player teleportation capability.

Key Functions:

• Teleport To Location: Initiates teleportation to specific teleport location
• Start Fade In: Begins fade-in transition
• Start Fade Out: Begins fade-out transition
• Freeze Player Movement: Disables player input and movement
• Unfreeze Player Movement: Re-enables player input and movement

Configuration:

• Fade Widget Class: Optional widget for fade-in/fade-out effects
• Fade Duration: How long fade transitions take
• Use Fade Effects: Enable/disable fade transitions
• Level Loading Timeout: Maximum wait time for level loading

State Tracking:

• Is Currently Teleporting (boolean)
• Current Fade Phase (None, Fading In, Waiting For Load, Fading Out)
• Target Teleport Location (reference)

Teleport Interface #

BPI_Teleport interface defines functions for teleport validation and callbacks.

Interface Functions:

Can Teleport:

Function: Can Teleport

Inputs: Player Controller (who is teleporting)

Outputs: Boolean (can teleport?), String (failure reason)

Purpose: Validate if teleportation to this location is allowed

Get Teleport Transform:

Function: Get Teleport Transform

Inputs: None

Outputs: Transform (location and rotation)

Purpose: Get exact location and rotation for player teleportation

On Teleport Complete:

Function: On Teleport Complete

Inputs: Player Controller (who teleported)

Outputs: None

Purpose: Callback when player successfully teleports to this location

Implementing the Interface:

Teleport Location actors implement this interface to:

• Define validation logic (Can Teleport)
• Specify teleport destination (Get Teleport Transform)
• React to successful teleportation (On Teleport Complete)

Can Teleport:

1. Check if player has discovered this location
2. Check if location is unlocked
3. Check if location is occupied
4. Check if player has required items
5. Return true if all checks pass, false otherwise

---

Setting up teleport system #

Placing Teleport Locations #

Teleport locations must be placed in the persistent level.

Setup Steps:

Step 1: Ensure Persistent Level Exists #

• In World Settings, verify persistent level setup
• For World Partition projects, persistent level is default level
• For Level Streaming projects, ensure you have a persistent level

Step 2: Place Teleport Location Actor #

• Open persistent level
• Place BP_TeleportLocation in world
• Position at desired teleport destination
• Rotate arrow to face desired player forward direction

Step 3: Configure Teleport Location #

• Select teleport location actor
• Set Display Name (e.g., “Town Square”)
• Set Associated Level (which streaming level this is in)
• Configure validation settings (if needed)
• Set icon for UI (if using fast travel)

Step 4: Test Reference #

• In another blueprint, try to get reference to teleport location
• Verify reference is valid even when level not loaded
• Confirms persistent level placement is correct

Adding Teleport Component #

Add the Teleport Component to the Player Controller.

Setup Steps:

Step 1: Open Player Controller #

• Open BP_PlayerController
• Go to Components panel

Step 2: Add Teleport Component #

• Click Add Component
• Search for “Teleport Component”
• Add to Player Controller

Step 3: Configure Component #

• Select Teleport Component
• Set Fade Widget Class (or leave None for no fade)
• Set Fade Duration (default: 1.0 seconds)
• Set Use Fade Effects (true/false)
• Set Level Loading Timeout (default: 30 seconds)

Step 4: Test Teleportation #

• Create test event (e.g., on key press)
• Call Teleport To Location with reference to teleport location
• Test in-game
• Verify fade, loading, and teleportation work correctly

---

Teleport location actor #

Persistent Level Requirement #

Teleport Location actors must always be in the persistent level.

Why Persistent Level?

Problem with Streaming Levels:

Scenario: Teleport location in Streaming Level A

1. Player is in Level B
2. Level A is unloaded (to save memory)
3. Player tries to access fast travel menu
4. Fast travel menu needs list of teleport locations
5. Teleport location reference is INVALID (level not loaded)
6. Fast travel menu breaks or shows missing locations

Solution with Persistent Level:

Scenario: Teleport location in Persistent Level

1. Player is in Level B
2. Level A is unloaded
3. Player opens fast travel menu
4. Fast travel menu queries teleport locations
5. Teleport location reference is VALID (persistent level always loaded)
6. Fast travel menu shows all locations
7. Player selects location in Level A
8. Teleport system loads Level A and teleports player

How to Verify Persistent Level Placement:

• Select teleport location actor
• Check Levels window
• Verify actor is in persistent level (usually bolded or marked)
• If in streaming level, move to persistent level

Data vs Actor Placement:

• Teleport Location Actor: In persistent level (always loaded)
• Target Location: Can be in any streaming level
• Associated Level: Property that stores which streaming level the target is in

This separation ensures references work while supporting any level layout.

Teleport Interface Implementation #

Teleport Location actors implement BPI_Teleport interface for validation and callbacks.

Can Teleport Function:

Default implementation:

Can Teleport (Player Controller):

1. Return true (always allow teleportation)
2. Return empty string (no failure reason)

Custom implementations can add checks:

Can Teleport (Player Controller):

1. Check if player has discovered this location:

 - Get save game
 - Check if location is in discovered locations list
 - If not discovered, return false, "Location not discovered"

1. Check if location is unlocked:

 - Check quest flags or conditions
 - If locked, return false, "Location locked"

1. Check if location is occupied:

 - Get all characters at location
 - If location occupied by enemy, return false, "Location occupied"

1. All checks passed:

 - Return true, ""

Get Teleport Transform Function:

Returns where player should be teleported:

Get Teleport Transform:

1. Get actor transform (location and rotation)
2. Return transform

Can be customized:

Get Teleport Transform:

1. Check for open spawn point (if multiple spawn points)
2. Return first available spawn point transform
3. Or return specific location based on conditions

On Teleport Complete Function:

Called after successful teleportation:

On Teleport Complete (Player Controller):

1. Mark location as discovered (if not already)
2. Trigger events (achievements, analytics, etc.)
3. Play arrival effects (particles, sounds)
4. Update quest state
5. Save game

Teleport Validation Checks #

Common validation checks implemented in Can Teleport function.

Discovery Check (Fast Travel):

Has Player Discovered Location?

1. Get save game component
2. Check discovered locations array
3. If location ID is in array:

 - Return true (discovered)

1. If not:

 - Return false, "You haven't discovered this location yet"

Unlock Check (Quest/Progression):

Is Location Unlocked?

1. Get quest system
2. Check if required quest is complete
3. Or check if player has required item
4. If unlocked:

 - Return true

1. If locked:

 - Return false, "Complete [Quest Name] to unlock this location"

Occupation Check (Safety):

Is Location Safe?

1. Get all actors in radius of teleport location
2. For each actor:

 - Is actor hostile enemy?
 - Is affiliated check (if using Team Affiliation System)

1. If hostile enemies present:

 - Return false, "Location is occupied by enemies"

1. If safe:

 - Return true

Cooldown Check (Game Balance):

Is Teleport On Cooldown?

1. Get last teleport time from player data
2. Calculate time since last teleport
3. If time < cooldown duration:

 - Return false, "Fast travel is on cooldown"

1. If cooldown expired:

 - Return true

Resource Check (Cost):

Does Player Have Resources?

1. Trigger Event Manager “Has Item” (if using Event Manager)
2. Check if player has required gold/items
3. If has resources:

 - Return true

1. If insufficient resources:

 - Return false, "Insufficient gold for fast travel"

Combining Multiple Checks:

Can Teleport:

1. Discovery Check → If false, return false
2. Unlock Check → If false, return false
3. Occupation Check → If false, return false
4. Cooldown Check → If false, return false
5. Resource Check → If false, return false
6. All checks passed → Return true

Each check provides specific failure reason for UI feedback.

---

Teleportation process #

Teleport Flow Overview #

Complete flow of teleportation from initiation to completion.

Full Teleportation Sequence:

1. Initiation:

 - Player triggers teleport (UI button, portal interaction, etc.)
 - Call "Teleport To Location" on Teleport Component
 - Pass reference to Teleport Location actor

1. Validation:

 - Call "Can Teleport" on Teleport Location (via interface)
 - If false, show error message and cancel
 - If true, proceed

1. Fade-In Phase:

 - Create fade widget (if configured)
 - Call "Play Fade In" on widget
 - Wait for fade-in animation to complete

1. Movement Freeze:

 - Disable player input
 - Disable character movement
 - Player cannot move or act

1. Teleportation:

 - Teleport player character to teleport location transform
 - Player is now at destination (but frozen)

1. Level Loading Phase:

 - Check if target level is loaded
 - If not loaded, trigger level loading
 - Wait for level to fully load
 - Player remains frozen during loading

1. Level Loaded:

 - Level is fully loaded and streamed in
 - Environment is ready for gameplay

1. Fade-Out Phase:

 - Call "Play Fade Out" on widget
 - Wait for fade-out animation to complete

1. Movement Unfreeze:

 - Re-enable player input
 - Re-enable character movement
 - Player can now move and act

1. Completion:

 - Call "On Teleport Complete" on Teleport Location (via interface)
 - Remove fade widget
 - Teleportation complete

Why This Order?

Teleport first, then wait for loading:

• Player position determines what level streaming system loads
• Player is at correct location for streaming priority
• Frozen state prevents falling through unloaded geometry
• Fade-out only happens when environment is fully loaded and ready

Fade-In Phase #

Visual transition before teleportation begins.

Fade-In Process:

1. Check if fade effects are enabled
2. If enabled:

 - Create fade widget instance
 - Add to viewport
 - Call "Play Fade In" event on widget
 - Wait for fade duration (e.g., 1 second)

1. If disabled:

 - Skip fade-in phase

Fade-In Widget Animation:

Start: Opacity 0 (transparent, can see world)

 ↓
 Animate over 1 second
 ↓

End: Opacity 1 (solid black, world hidden)

Purpose:

• Hide the moment of teleportation
• Provide visual feedback that something is happening
• Smooth transition between areas
• Professional presentation

Custom Fade Effects:

You can customize fade widget to:

• Use custom colors or images
• Add loading spinner
• Show location name text
• Play sound effects
• Animate additional elements

Level Loading Phase #

Ensures target level is loaded before revealing environment.

Level Loading Process:

1. Player is teleported to destination (but frozen)
2. Get target level from Teleport Location (Associated Level property)
3. Check if level is loaded:

 - Use "Is Level Loaded" function
 - Check World Partition streaming state

1. If level not loaded:

 - Trigger level load:
 - Call "Load Stream Level" (for level streaming)
 - Or rely on World Partition streaming (for World Partition)
 - Start loading timer

1. Wait for level to load:

 - Check every tick if level is loaded
 - Or use level streaming delegates

1. Once loaded:

 - Proceed to fade-out phase

1. If timeout reached (e.g., 30 seconds):

 - Cancel teleport
 - Unfreeze player
 - Show error message
 - Teleport player back to origin (optional)

Loading Indicators:

While waiting for level load:

• Fade widget is still solid (hiding world)
• Optional loading spinner can be shown
• Optional loading text: “Loading area…”
• Player is frozen at destination

World Partition vs Level Streaming:

World Partition:

• Teleport player to location
• World Partition automatically streams cells around player
• Wait for streaming to complete
• More automatic handling

Level Streaming:

• Explicitly load target streaming level
• Wait for “On Level Loaded” delegate
• More manual control

Both are supported by the teleport system.

Movement Freeze #

Player movement and input are frozen during teleportation and loading.

Freeze Process:

Freeze Player Movement:

1. Get player character
2. Disable input:

 - Disable Player Input(Player Controller)

1. Disable movement:

 - Set Character Movement to "Flying" mode (to prevent falling)
 - Or disable movement component entirely

1. Set flag: Is Currently Teleporting = true
2. Optional: Hide player character mesh (immersion)

Why Freeze Movement?

Critical for safety:

• Prevents falling: If level isn't loaded, geometry doesn't exist
• Prevents movement during loading: Player can't walk off edges during streaming
• Prevents input spam: Player can't cancel teleport or trigger other actions
• Professional presentation: Smooth transition without player interference

Freeze Duration:

Freeze starts: Before teleportation

 ↓
 During teleportation
 ↓
 During level loading (can be several seconds)
 ↓

Freeze ends: After fade-out completes and level fully loaded

Unfreeze Process:

Unfreeze Player Movement:

1. Get player character
2. Enable input:

 - Enable Player Input(Player Controller)

1. Enable movement:

 - Set Character Movement to "Walking" mode
 - Or re-enable movement component

1. Set flag: Is Currently Teleporting = false
2. Optional: Show player character mesh

Fade-Out Phase #

Visual transition after level is loaded, revealing new environment.

---

Teleport validation #

Can Teleport Interface Function #

The Can Teleport function determines if teleportation is allowed.

Function Details:

Interface: BPI_Teleport

Function: Can Teleport

Inputs:

• Player Controller (Actor): Who is trying to teleport

Outputs:

• Can Teleport (Boolean): true if allowed, false if not
• Failure Reason (String): If false, why teleportation is not allowed

Implementation in Teleport Location:

Basic implementation (always allow):

Can Teleport:

1. Return true
2. Return “” (empty failure reason)

Advanced implementation (with checks):

Can Teleport:

1. Run validation checks (discovery, unlock, occupation, etc.)
2. If any check fails:

 - Return false
 - Return specific failure reason ("Location not discovered", etc.)

1. If all checks pass:

 - Return true
 - Return "" (empty string)

Usage in Teleport System:

Teleport To Location (Teleport Location):

1. Call “Can Teleport” on Teleport Location via interface
2. Pass Player Controller reference
3. Receive boolean and failure reason
4. If false:

 - Show error message to player (use failure reason)
 - Cancel teleportation
 - Return

1. If true:

 - Proceed with teleportation

Common Validation Checks #

Typical checks implemented in Can Teleport function.

Fast Travel Discovery:

Check Discovery:

1. Get player save data
2. Check “Discovered Locations” array
3. If location ID is in array:

 - Pass check

1. If not in array:

 - Fail: "You haven't discovered this location yet"

Usage: Prevent teleporting to undiscovered locations

Quest Unlock:

Check Quest Unlock:

1. Get quest system
2. Check if required quest is complete
3. If quest complete:

 - Pass check

1. If quest not complete:

 - Fail: "Complete [Quest Name] to unlock"

Usage: Gate teleport locations behind quest progression

Enemy Occupation:

Check Occupation:

1. Overlap sphere at teleport location
2. Get all overlapping characters
3. For each character:

 - Check if enemy (using Team Affiliation System)
 - If enemy found:
 - Fail: "Location occupied by enemies"

1. If no enemies:

 - Pass check

Usage: Prevent teleporting into danger

Level Requirement:

Check Level:

1. Get player level from Attribute Manager
2. Compare to required level for this location
3. If player level >= required level:

 - Pass check

1. If player level < required level:

 - Fail: "Requires level [X]"

Usage: Gate high-level areas

Item Requirement:

Check Item:

1. Trigger Event Manager “Has Item” (or direct inventory check)
2. Check if player has required item (key, pass, etc.)
3. If has item:

 - Pass check

1. If doesn't have item:

 - Fail: "Requires [Item Name]"

Usage: Require specific items for access

Custom Validation Logic #

You can implement any custom logic in Can Teleport.

Can Teleport:

1. Get current in-game time
2. If location is “Night Market”:

 - If time is between 18:00 and 06:00 (night):
 - Pass check
 - If time is daytime:
 - Fail: "The Night Market is only accessible at night"

1. Proceed with other checks

Can Teleport:

1. Get current weather
2. If location is “Mountain Peak”:

 - If weather is "Blizzard":
 - Fail: "Cannot teleport during blizzard conditions"
 - If weather is safe:
 - Pass check

Can Teleport:

1. Get player reputation with faction
2. If location is “Empire Capital”:

 - If reputation with Empire < 0 (hostile):
 - Fail: "The Empire has banished you from the capital"
 - If reputation >= 0:
 - Pass check

Can Teleport:

1. Get number of players in party
2. If location is “Solo Dungeon”:

 - If party size > 1:
 - Fail: "This dungeon is for solo players only"
 - If party size = 1:
 - Pass check

Can Teleport:

1. Check if player is in combat
2. If in combat:

 - Fail: "Cannot fast travel while in combat"

1. If not in combat:

 - Pass check

Best Practices:

• Provide clear, specific failure reasons
• Check multiple conditions in priority order
• Return as soon as first check fails (early exit)
• Consider player experience (don't make restrictions frustrating)
• Test edge cases

---

Integration with other systems #

The Teleport System can integrate with other gameplay systems through the validation interface and callbacks.

Fast Travel System:

Use the Teleport System as the foundation for fast travel. Query all Teleport Location actors, check availability with “Can Teleport”, and display discovered locations in a UI menu.

Quest System:

Quest objectives can reference Teleport Locations to move players to quest areas. Use “Can Teleport” to validate quest state before teleporting.

Save/Load System:

Store discovered location IDs in save data. On load, restore discovered state and optionally teleport player to last known location or respawn point.

Event Manager:

Trigger events on teleport completion (location discovered, achievement unlocked, etc.) and use Event Manager for cost validation (gold, items, etc.).

Attribute Manager:

Validate player level or other attributes in “Can Teleport” function to gate high-level areas.

The validation interface and callbacks provide integration points for any custom system.

---

Example implementations #

The Teleport System can be implemented in various ways depending on your game's needs.

Basic Teleport Points:

Create portal actors with trigger volumes that reference Teleport Location actors. When the player overlaps the trigger, call “Teleport To Location” on the Player Controller's Teleport Component. This works for dungeon entrances, area transitions, or any two-way portal system.

Fast Travel System:

Build a UI menu that queries all Teleport Location actors and displays discovered locations to the player. Use the “Can Teleport” interface function to validate discovery status and other requirements. You can implement discovery triggers at landmarks and store discovered location IDs in save data.

Dungeon Exit Portals:

Create exit portals that teleport players back to the overworld. You can store the player's entry point in player data to teleport them back to where they entered, or use fixed teleport locations for consistent exits.

---

How to guides #

Setting Up Basic Teleportation #

Step-by-step guide to set up basic teleportation between two locations.

Step 1: Add Teleport Component to Player Controller #

• Open BP_PlayerController
• Add Teleport Component
• Configure:
  • Fade Widget Class: WBP_TeleportFade (or None)
  • Fade Duration: 1.0
  • Use Fade Effects: True

Step 2: Create Teleport Location Actors #

• Open Persistent Level (critical!)
• Place BP_TeleportLocation at Location A
• Configure Location A:
  • Display Name: “Town Square”
  • Associated Level: “Town_Level
• Place BP_TeleportLocation at Location B
• Configure Location B:
  • Display Name: “Forest Camp”
  • Associated Level: “Forest_Level

Step 3: Create Portal/Trigger #

• Create or open portal blueprint (e.g., BP_TeleportPortal)
• Add trigger volume (sphere, box, etc.)
• Add reference to target Teleport Location:
  • Variable: Target Location (Teleport Location reference)
  • Make Instance Editable

Step 4: Implement Teleport Logic #

BP_TeleportPortal – Event Graph:

On Component Begin Overlap:

1. Check if overlapping actor is player character
2. If yes:

 - Get Player Controller from player character
 - Get Teleport Component from Player Controller
 - Call "Teleport To Location" (Target Location)

Step 5: Place Portals and Set References #

• Place portal in Town_Level
• Set Target Location to Location B (Forest Camp)
• Place return portal in Forest_Level
• Set Target Location to Location A (Town Square)

Step 6: Test #

• Play game
• Walk into portal in town
• Verify:
  • Fade-in effect plays
  • Player teleports to forest
  • Forest level loads (if not already loaded)
  • Fade-out reveals forest
  • Player can move
• Walk into return portal
• Verify return teleport works

Troubleshooting:

• If reference is invalid: Check that Teleport Locations are in persistent level
• If level doesn't load: Check Associated Level property is set correctly
• If player falls: Verify level loading wait is working

Best Practices:

• Check conditions in priority order (most restrictive first)
• Provide clear, helpful failure messages
• Test each check individually
• Consider edge cases
• Balance gameplay vs player convenience
• —

END OF DOCUMENTATION

• Level Streaming Documentation
• World Partition Documentation
• Event Manager Documentation (for integration)
• Quest System Documentation (for quest-based teleportation)
• Save/Load System Documentation (for discovery persistence)