A comprehensive manual to navigating the custom digital surprises. Learn how to bypass locks, trigger background scores, and troubleshoot React rendering issues.
The application has no traditional login page. It utilizes a pseudo-terminal lock screen to validate your identity and mount the correct React components based on your password payload.
The input field is strictly case-sensitive. Demo@123 is completely different from demo@123. Ensure caps lock is off unless specified.
If you were given a direct URL containing ?pass=..., the system will automatically parse the parameters and bypass the terminal screen.
The emotional impact of this architecture relies entirely on synced background scores (R&B, Jazz, custom tracks). However, modern browsers aggressively block audio from playing automatically.
Chrome, Safari, and Firefox have strict rules: Media cannot play until the user interacts with the document. This means if you bypass the lock screen using a direct URL, the music will NOT start immediately.
Apple iPhones have a physical silent switch. Even if media volume is up, Safari web audio might be muted if the physical switch is set to silent.
The memory timeline uses native scroll sniffing via React's Intersection Observer. As you scroll down, specific images and texts will fade in. Do not scroll too fast, or you might skip audio triggers mapped to specific sections.
This is a Single Page Application (SPA). If you refresh your browser mid-way through a game, door puzzle, or timeline, the React state will reset to zero. You will have to enter the password and start from the beginning.
If presented with multiple doors, clicking the wrong one might trigger a mock error or loop you back. Read the context clues provided in the text before the doors carefully.
If the system fails to mount, audio breaks, or the UI freezes, consult the matrix below before abandoning the experience.
CAUSE: JS Parsing Error / Old Browser
Vite compiles using ES Modules. Older browsers (like iOS Safari 14 or outdated Android Webviews) cannot read this and will crash silently.
CAUSE: CPU Throttling
The app uses heavy CSS backdrop-filters, SVGs, and framemotion logic. Phones on battery saver mode artificially limit the CPU and screen refresh rate.
CAUSE: Exact String Mismatch
The logic strictly checks the string input against hardcoded records. Auto-correct often adds an invisible space at the end of words.