Escape the Worlds Obby

Escape the Worlds Obby is a Roblox obby and adventure experience built around progressing through stages and unlocking multiple worlds. I served as the lead scripter and handled the project's core systems from initial implementation through live maintenance.

The experience has received more than 532,000 visits. My responsibilities included stage progression, world access, player data, ProfileService integration, gameplay logic, bug fixing, and production stability.

Escape the Worlds Obby is available on Roblox and has accumulated more than 532,000 visits.

I was responsible for the core scripting architecture rather than one isolated feature. This meant establishing how progression was stored, how stages were completed, how worlds were unlocked, and how player state was restored across sessions.

• -Complete stage progression logic
• -Multi-world unlock and navigation systems
• -ProfileService-backed player persistence
• -Core gameplay implementation
• -Player stat and progression tracking
• -Live bug fixing and system maintenance
• -Production stability improvements

The primary gameplay loop required reliable tracking of each player's current stage. When a player reached a valid checkpoint, the server updated their progression and persisted it so they could resume later.

Progression validation happened on the server. The client could display checkpoints and progression feedback, but it could not decide which stages a player had legitimately completed.

The game's content was divided across multiple worlds. I designed the world progression system so access could depend on completed stages, saved progression, or other eligibility requirements.

The architecture separated world configuration from the underlying progression logic. This made it easier to add new worlds and stages without rewriting the systems responsible for tracking player access.

• -Configurable world requirements
• -Persistent world unlocks
• -Reliable transitions between worlds
• -Expandable stage and world definitions
• -Consistent progression across sessions

I integrated ProfileService to manage production player data. Profiles stored stage progression, world unlocks, and relevant gameplay statistics.

Session locking ensured that the same player profile could not be actively loaded by multiple servers at once. This reduced the risk of conflicting writes, rollbacks, and duplicated progress.

• -Session-locked profile loading
• -Persistent stage and world progression
• -Safe release handling when players leave
• -Fallback handling for failed profile loads
• -Data structures designed for future expansion

Releasing a game is only the beginning of its technical lifecycle. I continued maintaining gameplay logic after release, investigating progression problems, save-related edge cases, and situations that appeared under real player traffic.

Fixes had to preserve existing player data while correcting the underlying behavior. This required understanding how a change would affect both new players and the hundreds of thousands of visits already represented in the game's saved profiles.

• -Post-release gameplay maintenance
• -Progression and checkpoint bug fixes
• -Persistence edge-case handling
• -Compatibility with existing player profiles
• -Performance-conscious multiplayer logic

A multi-world obby needs to support additional content without turning each update into a rewrite. I kept stage definitions, world requirements, and progression logic modular so the experience could continue growing.

New stages and worlds could be added through configuration while still using the same persistence and validation systems.

Escape the Worlds Obby reached more than 532,000 visits while maintaining persistent progression across its multi-world experience.

The project demonstrates my ability to own a Roblox game's technical foundation end to end: building the initial systems, preparing them for production, maintaining live player data, and supporting the experience after release.