Playable experiments

Abstract

Watchman's first minute is established through black frames, a distant bell, fading brazier embers, and the awakening of the fire-marked knight. Production began with Grok concepts and keyframes, continued through five image-to-video segments and an edit in Jianying, then entered Godot as an OGV file. This record covers silent environmental narrative, grain boiling in slow generated shots, and the transition from high-definition cinematic imagery to a pixel-art game. It also documents a manual-first method: determine shot by shot which images survive motion before turning the successful decisions into a reusable pipeline.

Abstract

This entry documents a pipeline for turning a generated concept into a usable pixel boss. The work lies not in a single generation but in choosing the medium, anchoring style, and iterating by hand: an existing enemy defines density, silhouette, and palette; PixelLab supplies seven animation states; grounding, scale, motion, and an existing area effect are then corrected and assembled. Failed approaches remain visible to mark the boundary between concept art and in-game assets.

Abstract

This entry documents Watchman's asset-management pipeline: heterogeneous packs are repacked into standard atlases, manifests record animation timing and foot anchors, and indexing, mapping, and composition tools keep hundreds of resources searchable and replaceable. The lasting object is not one asset set, but infrastructure that can absorb placeholders, later replacements, and continued expansion.

Abstract

This entry records the extraction of combat values from code into balance.json and the browser console built for centralized search, editing, and live comparison. Assertions lock derived relationships and valid ranges so tuning cannot quietly change program logic. The tool does not replace judgment; it shortens the distance between a decision, its validation, and a rollback.

Abstract

This entry organizes an AI development workflow that can run independently overnight. A bounded brief defines the work, automated tests form the merge gate, and adversarial review searches for judgment gaps outside the test suite. The final delivery includes code, verification results, and a change report, keeping unattended execution inspectable and reversible.

Abstract

This entry records Watchman's radial world structure: the hub concentrates characters and systems, bonfires anchor saves and death return, and regional lamps handle transit between areas. The first chapter remains linear, using distance, return paths, and node density to pace progression, so spatial structure carries navigation, risk, and narrative at the same time.

Abstract

This entry decomposes combat weight into tunable timing and feedback relationships rather than higher damage numbers. Stance, stance breaks, executions, parry windows, and turn speed jointly shape the rhythm of attack and defense. Frame-by-frame tests then calibrate hit stop, displacement, and recovery so that every exchange carries legible risk and reward.

Abstract

This entry explains why the combat system is concentrated in one iron sword and how build variation is moved into forging, transformations, scabbards, and whetstones. A single core weapon reduces animation and feel-maintenance costs while preserving a combinatorial space of moves, attributes, and special forms: a solo-development trade-off between systemic depth and production scale.

Abstract

This entry defines Watchman's direction as a side-view Soulslike set within an unending night, then records how a solo developer organizes several AI production lines from a director's position. Task briefs, test gates, and adversarial review establish the boundary of delegation, keeping design judgment human while implementation, validation, and documentation move in parallel.