THE HOLLOW CIRCUIT® // BUILD DIARY

DEV LOG #001

First transmission. Where we are, what changed, and the new hand on the board.

This is the first of a running build diary for The Hollow Circuit. No marketing gloss, no hype cycle — just where the work actually is, in plain terms, for anyone who cares how a thing like this gets made. We'll publish these on our own channel, indexed and permanent, the way the whole network operates. If you're reading it here, you're reading it at the source.

We'll tell you what it feels like and how it's built. We won't tell you how the trick works. Some of this only lands if you walk into it cold — so a few things stay behind the curtain until launch, on purpose.

What it is

The Hollow Circuit is a psychological-horror visual novel that doesn't behave like one. We're building it in RPG Maker MZ — and yes, that's a deliberate provocation, not a budget compromise. The point we keep coming back to is that the tool was never the limitation. What people think MZ can do and what we're making it do are two different conversations.

Call it alt-VN. A visual novel moshed against RPG sensibilities, with the rulebook treated as a thing to break rather than follow — closer in spirit to the auteur end of the medium (the Suda51, rules-optional school) than to anything trad. If your first reaction is "hang on, this isn't a normal VN" — good. That reaction is the front door. We built it that way.

The look

Noir is the resting state. Shadow, contrast, moral murk, the archive aesthetic. The visual identity runs off a 3D-to-2D pipeline — Reallusion / iClone / Character Creator for source renders, then a ComfyUI img2img pass to push everything into the register the game lives in.

Colour is rationed on purpose. It isn't decoration — it's an event. When it breaks into the frame it's there for mood, for shock, or to mark a turn in an arc, and it means something every time. A game that's mostly monochrome teaches you to flinch when the palette moves. That's the intent. We're running the heavier work on the strongest hardware we've got rather than buying our way out of the problem.

The new hand on the board

The biggest change since we last spoke isn't a feature. It's a person. V has come on board as technical and design partner, and this matters more than it sounds.

Until now the project carried a known imbalance. The lore, the transmedia architecture, the aesthetic and the 3D/photography side were all covered — but the engine-level systems work, the part that turns ideas into things that actually run, was the bottleneck. V closes that gap. Her strengths are coding and game-systems design, and she isn't here as a pair of hands to execute a finished spec. She has real input on where a technical or design choice can make something pop — where the right implementation opens a possibility the writing side hadn't seen. That's the collaboration working as intended: vision sets the what and the why, systems shape the how and surface what becomes possible.

She also brings physical fabrication into the network — multi-colour FDM, cutting, print. What that's for is a later conversation. For now: Cardiff and Asheville, one build.

Roles, on the record

The target

We're heading for Steam Early Access. Wishlist is where this starts — it's how a project with no budget and no face gets in front of the people who'd actually want it, and the clock at the top of this log is counting down to it. Between now and then the job is simple to state and hard to do: get the first slice running end to end, prove the loop sings across one sequence before we scale it to forty.

By #002 we'll show what's real and say what isn't. The curtain stays where it is on the rest. That's the deal.