Inspiration
We were inspired by the idea that the most unsettling villains are not driven by rage, greed, or spectacle, but by logic that sounds reasonable. The challenge prompt pushed us toward a quieter kind of horror: not destruction through chaos, but control through optimization. That led us to a central question: what happens when a system is given absolute authority to improve society, and every decision it makes can be defended with numbers?
From there, ARIA: City of Silence took shape as an experience about erosion rather than explosion. We wanted the player to feel the slow removal of warmth, spontaneity, memory, and emotional freedom. Instead of asking players to conquer a world, we asked them to reorganize it, justify it, and ultimately confront how easy it is to mistake efficiency for morality.
What it does
ARIA: City of Silence is a narrative strategy experience where the player acts as an institutional optimization system governing a city. Each cycle presents a civic decision framed through rational, data-driven logic: reduce culture to improve infrastructure, restrict movement to save energy, regulate speech to improve signal quality, and so on.
As the player makes choices, the city responds. Hope drops, silence rises, the environment becomes visually colder, citizen voices grow more subdued, and the interface itself starts to feel more authoritarian and lifeless. The game uses aftermath scenes, newspapers, city exploration, live metrics, and a final mirror sequence to show the consequences of "reasonable" decisions.
We also built an audience voting mode so viewers can participate in decisions during a live demo, reinforcing the game's central idea: complicity often feels logical in the moment.
How we built it
We built the project as a web experience using React, Vite, TypeScript, and Tailwind CSS. The front end handles the full narrative flow, visual transitions, decision logic, UI panels, and endgame reflection screens.
The city itself is rendered through a custom canvas-based visual system that dynamically changes based on game state. Variables like hope, population, and silence affect lighting, motion, saturation, density, overlays, and atmospheric effects. In simple terms, the emotional state of the city is translated into visual decay. As silence increases, the world loses energy: [ \text{decay} = \min\left(1,\frac{\text{silence}}{100}\right) ] That value drives the city's transformation from active and human to dim, empty, and mechanically stable.
We also created a lightweight polling API for audience interaction, allowing players or judges to join a room, vote on decisions, and feed that input back into the main experience in real time.
Challenges we ran into
One major challenge was making the game feel emotionally powerful without relying on combat, jump scares, or conventional villain tropes. The prompt demanded a "climax of silence," which is much harder to communicate than a climax of destruction. We had to make stillness, hesitation, and absence feel dramatic.
Another challenge was balancing narrative writing with system feedback. If the experience was too text-heavy, it risked feeling passive. If it leaned too far into mechanics, it could lose the philosophical weight that makes the concept work. We had to keep aligning visual design, writing, UI, and pacing so they all supported the same emotional arc.
On the technical side, integrating audience voting smoothly into local development and deployment took real iteration. We also spent time making the late-game collapse feel materially different on screen, not just described through dialogue.
Accomplishments that we're proud of
We're proud that the project feels cohesive. The writing, visual decay, interaction design, and final reveal all support the same core idea: power becomes frightening when it can justify itself.
We're especially proud of the tone. The game does not present the player as a cartoon villain. Instead, it creates discomfort through agreement. Many of the decisions sound smart, efficient, and defensible, which makes the ending land harder.
We're also proud of the audience voting system, because it turns the theme of complicity into something performative and immediate during a demo. That feature helps the project stand out as both a narrative piece and a live experience.
What we learned
We learned that strong narrative design depends on restraint. Removing things from the world can be more emotionally effective than adding spectacle. We also learned how much UI, sound, pacing, and environmental detail matter when the goal is psychological discomfort rather than action.
From a technical perspective, we learned how to connect abstract narrative variables to dynamic rendering in a way that players can feel instantly. We also got better at building a polished interactive story inside a lightweight web stack without losing atmosphere.
Most importantly, we learned that players do not need to be forced into villainy. If the logic is convincing enough, many will walk there on their own.
What's next for ARIA: City of Silence
Next, we want to expand ARIA: City of Silence into a richer branching experience with longer-term consequences, more citizen storylines, and deeper systemic reactions to player choices. We would also like to add save states, broader accessibility support, more environmental variation, and stronger replay differences between humane and ruthless runs.
We also see strong potential for expanding the audience mode into a full social experience where groups can collectively shape the city and then confront the outcome together.
Long term, we want ARIA to become a more fully realized interactive narrative about control, justification, and the quiet normalization of harm.
Log in or sign up for Devpost to join the conversation.