Sample devlog: start with one playable action

Narrow the question

This sample game-development log concerns a movement prototype that does not exist. Imagine a starting point, a destination and an obstacle that can be passed by another route. The player chooses when to move and when to stop. There is no actual project, completed implementation or playtest behind this scenario. It simply demonstrates how a log might begin with a specific question.

The hypothetical prototype asks just one thing for now: can a player recognise an opportunity ahead and want another attempt at a more precise move? Map size, character progression and backstory remain outside this discussion. The controls, rules and feedback can then share one subject of observation: whether a single move creates a choice worth making.

Connect an action to a loop

In this example, an attempt could be described in four connected moments: notice the route, choose the timing, move, then use the landing position to decide what comes next. Each moment needs an understandable outcome. If the character passes the obstacle, the image should make the landing position clear. If movement never starts, there should be a reason to investigate before another input buries that uncertainty.

A minimal draft of the rules might specify where movement is allowed, whether its direction can change and where a failed attempt restarts. These are open options for this example, not established game rules. Retrying in place, for instance, could isolate one action for observation; returning to the beginning would bring the preceding route into the next attempt. Those alternatives ask different questions.

A development log could record how an implementation took shape here. With an actual project, prototype images, rule changes and demonstration clips would explain why one option remained and another was dropped. No engine, code structure or division of responsibilities has been specified for this sample, and the draft rules do not describe work completed by Proca.

Leave questions for a playtest

A proposed playtest for this hypothetical prototype could record where players pause, how they explain a failed attempt and what they change on the next one. These remain questions. There are no invented participant counts, completion times or satisfaction scores. A test that has never taken place cannot support a design conclusion.

The sample stops before the next attempt: first ask whether the action and its outcome can be understood, then decide whether to add routes or rules. An actual devlog would still need project context, evidence before and after changes, and the developer’s own judgement. That material is yet to come. This prototype is an example and does not belong to Proca’s project history.