Sketchnotes
(the loop&arcs part from CS247G)
Play
I played A Dark Room, a minimalist, text-based adventure game created by Michael Townsend and released by Doublespeak Games in 2013. I played the digital browser version at https://adarkroom.doublespeakgames.com/ for approximately four hours, progressing from a single room, a large village, the dusty path, to the old starship. By the end of my playthrough, I had unlocked most of the game’s areas and mechanics. Its target audience seems to be players who enjoy exploration, strategy, and gradually uncovering complex systems, and its simple interface also makes it approachable for people unfamiliar with these genres.
One of the most distinctive features of A Dark Room is its minimalist presentation. Almost everything is represented through text and numbers. Players primarily interact by clicking on text buttons, while their available resources are continuously displayed on the right side of the screen. The map is also just letters, allowing players to understand their location and navigate without relying on elaborate visual representations. As an adventure game, it has both short loops for immediate feedback and long arcs for narrative. Minimalism helps players focus on the exploration, complicated resource exchange systems, the huge map without being distracted too much by the visuals or controls, and leave room for imagination.
The game’s combination of genres also shapes how it represents system dynamics. It begins almost like an idle or incremental game, where players gather resources and wait for actions to become available again. Gradually, it develops into a resource management simulation, and eventually includes RPG-style exploration and combat. These genre transitions are important because each introduces another dimension of the system. Resource management teaches players to understand production and consumption, while exploration creates new demands for resources and new opportunities to obtain them. Rather than introducing all these mechanics simultaneously, the game allows players to become familiar with one before encountering the next. I also really love the exhibited resources on the right, because it reflects my action immediately and lets me know that I’m always making meaningful choices.
The game operates at several different timescales. At the smallest scale, the game provides extremely short feedback loops, sometimes lasting only a few seconds. For example, when I stoked the fire, the text immediately changed to indicate that the fire was roaring and the room was warm. When I gathered wood or checked traps, the resources I collected were immediately reflected in the inventory. These repeated actions created a satisfying connection between what I did and how the game state changed. Some of these loops recur approximately every ten seconds, while combat has even shorter cycles. During fights, I could attack again whenever the action became available, often after only a few seconds, rather than waiting for a conventional turn-based sequence. This made combat feel active even though the interaction was simply clicking on text.
These short loops were important for sustaining my attention because the larger narrative arcs took much longer to unfold. Expanding the village, for instance, gradually introduced new people, professions, buildings, and production possibilities. Mysterious visitors and events also revealed more about the world and its history. Meanwhile, exploration along the dusty path formed another long arc. I could not simply travel to the most distant locations immediately. I needed better equipment, additional water capacity, and resources that could only be acquired by exploring nearer locations first. This progression created a reinforcing loop: gathering resources enabled exploration, exploration unlocked new resources and technologies, and those improvements enabled further exploration. The discovery of the old starship was particularly interesting because it emerged from a much larger progression that began with something as simple as maintaining a fire. Embedding the short loops in the long arcs provided continuous feedback and a sense of achievement, so that I feel more motivated to continue to see how the larger narrative unfolds.
The games’ resource economy is complicated. At the beginning, there were only a few resources to manage, such as wood and materials collected from traps. This allows players to familiarize themselves. As the village expanded, the economy became increasingly interconnected. Resources could be collected directly, produced by assigning villagers to different occupations, obtained through trading, or discovered through exploration. There is also a controlled balance, the later stage of the game, the easier to collect basic resources (e.g.village population grows, so more hunters can get fur) , so they introduced higher level resources (e.g. 300 fur for 1 teeth ). It seems that the economy evolves along with the player’s progression. Collection methods also get more complex: self, hiring villagers, purchase from shops, and from investigating the path , the methods become more available as the game progresses. This leads to the fun of Challenge. Players need to allocate resources and manage the system to achieve goals, and calculate the career distribution.
In terms of formal systems, A Dark Room has clearly defined resources, rules, actions, constraints, and state transitions. The player acts within these rules, but the outcomes emerge from interactions among them. I think the game is particularly successful at making its formal system understandable without explaining everything explicitly. Instead of reading a long tutorial, players learn the rules by interacting with them, observing the consequences, and gradually developing strategies. Thus, the onboarding approach from this game is what I want to take into my own system game. System games can become complicated very quickly, but the game starts with complete, short loops until the players are familiar, then move to the next mechanism and enrich the system gradually.
However, the short loops started to feel annoying as I progressed further into the game. For example, plague events occurred frequently, and I repeatedly had to rebalance the village population and production. Because the events used the same descriptions and required the same responses, they felt repetitive and distracting. I was more interested in the larger exploration arc, but the game continued demanding my attention for smaller tasks that no longer offered much novelty. At a later stage of the game, players are already bored with the short arcs. I wonder if there is a way to minimize them (e.g. happen in the background, or not dominate the interface) to leave space for the more important arcs.
The game communicates values of survival, adaptation, exploration, and resourcefulness. Progress depends on learning to manage scarcity, making tradeoffs, and using limited resources strategically. It also encourages curiosity by gradually revealing new mechanics and information rather than presenting the entire world at the beginning. It brings the aesthetics of Challenge and Discovery. However, the game also let players view the village inhabitants primarily as resources. Villagers become units of labor to distribute among occupations, and their value is frequently expressed through production rates. They only differ in number, instead of having any personality traits, and plagues or disasters events just reduce them quickly, making me feel a bit inhuman.
