Back to the journeyArchive comparison · original material and a later reconstruction
Recovered designs, a reconstructed homepage, and the ideas returning in a new form.
A question across time
Gameloom’s surviving designs reach back to 2012. Plans and a public homepage followed in 2013. The material recovered in 2026 shows an early ambition: make games, share worlds, and let players meet inside them.
The returning direction starts with distinctive games we author, connected by a shared engine. Community creation can grow from those foundations. The ambition still includes 3D worlds, browser and native players, multiplayer, and distributed execution.
Logo files carry modification dates from May to October. They date the artifacts, not the exact beginning of the idea.
The outline and architecture drawings describe a browser studio, shared resources, and client/server execution.
The homepage was archived in June; its logo, styles, and font were archived in August.
The originals were preserved, the homepage reconstructed, and the direction reconsidered.
The client and server each contain JavaScript. The client also has native communication and graphics components; the server has native tools. The plan separates responsibilities while making a shared game possible.
The image here is an unchanged copy of the recovered diagram. Open it for its original size.
The recovered HTML was decoded for modern text display. The original font, logo, and styles were embedded; a missing favicon reference was removed, and the About link was pointed to its archived page. No archived JavaScript was run.
This public image is an unchanged copy of that recovery screenshot. The page advertised Gameloom as coming soon; the recovered material does not establish a platform launch.
Follow a thread
These comparisons connect a historical proposal with the present direction. They describe intentions across time, not a claim that the original plan became a finished engine.
A browser-based studio would keep resources on servers, divide work between client and server, and publish games for people to play together.
Multiplayer and distributed execution are core requirements. The research asks how shared rules remain meaningful when different parts of a game run in different places.
The technical outline proposed browser or native players. Its architecture drawing gave native components explicit roles beside JavaScript.
Browser and native worlds remain part of the ambition, with 3D as a foundational requirement. The research explores how common game meaning can survive different execution and presentation choices.
The original audience notes focused on hobby programmers who already knew some programming. The plan joined making, hosting, and publishing.
Distinctive games we author now lead the direction. Their different demands shape a shared engine; community creation can grow from the same foundations.