Sample content: replace this post with a real devlog when ready.
A grey box answers one question: can the idea move? A first playable has to answer a harder one: can another person understand why they should keep moving?
The smallest useful loop
This sample prototype begins with three actions: move, collect, return. The first version had all three, but no readable rhythm. The collectables were everywhere, the return point looked like scenery, and failure had no useful feedback.
The repair was deliberately small:
- Put one collectable inside the starting view.
- Use the warm signal colour only on things that change state.
- Make the return point react before it becomes available.
- Restart in one input without an interruption screen.
What changed after watching
The useful notes were not feature requests. They were moments of hesitation: a turn toward the wrong doorway, a pause after collecting the last item, an attempt to interact with a decorative object.
The next build will keep the same mechanics and revise only those readings. More content can wait until the loop explains itself.
Build notes
- Engine:
[Game engine] - Input: keyboard and controller
- Build:
sample-0.1.3 - Next test:
[Date and audience]