Last calibrated: August 2026
• Prize will be awarded in GBP and converted automatically to overseas currencies by Steam.
• Only entries submitted via this website submission form will be accepted.
• One entry per player, any suspected ‘alt’ accounts will be disqualified, including any other suspected linked accounts.
• Winners must have a Steam account to claim the prize. No alternative prize offered.
• If drawn winner is ineligible or refuses the prize, draw will be rerolled.
• Draw will take place during a live stream hosted by vincentleet on Twitch.tv; the stream will begin at 19:00UTC, August 29th.
• Prize winner will be contacted by ChrisYepYep within 48 hours of the draw taking place, via Discord. If the winner is not accessible via Discord, an undefined amount of time for contact may be required.
When navigating this labyrinth, the completion room will request parameters such as entering your Habbo Origins username and providing a screenshot asset to cross the threshold of the final prize diagnostic. This data is passed securely through Formspree. No permanent databases store your records here, and no elements are ever distributed to tracking configurations. A record of the username you enter, and the image you upload, will be stored for the duration of the event plus 1 calender month; to ensure we have your submission should the prize draw need to be rerolled.
To prevent structural reality collapses during progression, this script utilizes your application environment's localStorage metrics to retain structural context (remembering your active room indexes or audio configurations). This variable state lives directly upon your system and is never sent back to external endpoints.
This diagnostic environment runs deployed atop the GitHub Pages server matrix. Due to this server architecture, network metadata (including standard IP allocations, browser configurations, and structural request timestamp parameters) is logged inherently by operational frameworks. To verify how this structural code environment works, read the GitHub Privacy Statement.
If you desire to completely erase your data fingerprints from the architectural history of the maze, simply initiate the Reset Progress utility or scrub your web browser cache logs directly.