INTERACTIVE EXPERIENCE / 06
Unirexcity
02 FROM SOURCE TO DELIVERY
A change has
somewhere to go.
Inspect the build, follow its artifacts, and see how application and content reach their destinations.
speed 2.5 · jump 5.3 · jump enabledReadyChoose a job to inspect its inputs, outputs and dependencies.
03 SHARED FOUNDATIONS
Build the system.
Use it across worlds.
Select a package to trace where it is used. Then explore what each project adds around those shared foundations.
Connections from the inspected Unity package manifests. City’s controller is shared architecture, rather than a package connection shown here.
AROUND THE CORE SYSTEMS
The Hunt
A game assembled from shared systems, with its own movement rules, content and progression. The same state contract supports specialized runner behavior.
- Running, jumping, rolling and flying states
- Power-ups, destructible obstacles and object pooling
- Configurable missions, rewards and stamp-card progression
- Custom transition-map and data editors
About this experience. A Three.js adaptation of selected systems from the original Unity projects. Movement, collisions and transitions use simplified browser algorithms. Pipeline playback is a simulation based on the archived GitLab configurations. It does not run Unity builds or publish changes to the original projects.
The inspected configurations include test templates; this page does not present them as verified active release gates. Package connections reflect the inspected manifests. The demo uses Mixamo’s X Bot and animation clips from the Three.js examples, with adapted jump and crouch poses. The character illustrates the controller and is not an Unirexcity asset. Character credit: Adobe Mixamo ↗
Have a similarly specialized problem?