teleport-map-unlock

Design fast travel, waypoint unlocking, and map reveal systems for open-world games.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/Firzus/agent-skills --skill teleport-map-unlock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teleport-map-unlock
Source: https://github.com/Firzus/agent-skills/tree/main/skills/game/teleport-map-unlock
Command: npx skills add https://github.com/Firzus/agent-skills --skill teleport-map-unlock

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps design and implement reliable fast travel, waypoint unlocking, and map reveal systems for open-world games without falling through the world, desyncing map state, or creating camera and spawn bugs.

Core Features & Use Cases

  • Map Unlock Architecture: Defines how terrain reveal, fog-of-war, and point-of-interest discovery should work together from a single source of truth.
  • Waypoint Registry Design: Specifies stable waypoint IDs, spawn points, facing direction, multi-layer map support, and lifecycle rules for permanent and temporary travel points.
  • Teleport Safety Pipeline: Covers validation, input locking, streaming residency checks, safe placement, physics reset, camera warp handling, and recovery fallbacks.
  • Design Guidance: Helps choose between free, gated, consumable, or progression-based fast travel models and calibrate density, restrictions, and reveal methods.
  • Failure Analysis: Documents common bugs such as fall-through spawns, camera whiplash, save corruption, layer mismatches, and teleport exploits.

Quick Start

Use this skill to design a fast travel system for my open-world game, including unlock rules, waypoint data, teleport sequencing, and safety checks.

Frequently Asked Questions about teleport-map-unlock

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a fast travel system for an open-world game without players falling through the world?

A reliable fast travel system requires atomic validation, streaming residency checks, and safe spawn placement to prevent fall-through spawns. You must lock player input during teleport sequencing and apply physics resets upon arrival to ensure stable terrain loading.

What is the best way to manage fog of war and map reveal state alongside waypoint unlocking?

Fog of war and map reveal should operate from a single source of truth alongside point-of-interest discovery. This unified map unlock architecture ensures terrain reveal, waypoint registries, and fast travel policies remain synchronized without desyncing map state.

How do I structure waypoint data for multi-layer maps and temporary fast travel points?

Waypoint registry design requires stable waypoint IDs, specific spawn points, facing direction data, and explicit lifecycle rules. Defining these parameters supports both permanent and temporary fast travel points across multi-layer map environments.

Why does my teleport pipeline cause camera whiplash and player desync?

Teleport pipelines cause camera whiplash and desync when they lack proper camera warp handling and fallback logic. Implementing input locking, physics resets, and recovery fallbacks during the teleport sequence prevents these common map state corruption issues.

How do I choose between free, gated, and progression-based fast travel models?

Choosing a fast travel model requires design guidance to calibrate waypoint density, travel restrictions, and map reveal methods. You must evaluate free, gated, consumable, or progression-based policies to balance open-world exploration with player convenience.