Nex Parkour Rooms System

The problem

Building 3D platformers in Three.js often results in messy collision logic, unreliable respawn states, and players bypassing challenges. Implementing animated platforms that sync with game state and server persistence is time-consuming to get right from scratch.

What it does

• Generates a multi-room parkour system with static, moving, disappearing, and rotating platforms.
• Provides a runtime manager for checkpoint tracking, death/respawn cycles, and void detection.
• Includes a dynamic build system to place, move, or delete platforms at runtime.
• Manages entrance gates and portals to prevent players from entering main areas before completion.
• Handles server-side completion sync via a standardized messaging contract.

Frameworks & tools

Three.js, WebGL, and TypeScript. Works with multiplayer frameworks like Colyseus via the server sync module.

Why this beats prompting it yourself

This skill provides a production-hardened state machine for death and respawn cycles that won't leak DOM nodes or corrupt player state. It ensures collision boxes are correctly mapped to scene.userData and enforces forward-only checkpoint logic that prevents common progression exploits.

Use cases

• Creating an initiation gate or onboarding challenge for a VR or 3D room.
• Adding high-difficulty jump puzzles with specific checkpoint requirements.
• Building a runtime level editor for platformer mini-games.
• Implementing escalating difficulty rooms with custom labels and dimensions.

Known limitations

This system provides the parkour logic and geometry but does not include the player controller. You must provide your own FPS or third-person controls and hook them into the manager teleport function.