How Ecos investigates.
A mini-dossier for people who want to look below the surface: the player fantasy, evidence types, the role of contradiction and what the project learned while turning interface back into investigation.
Value first. Payment second.
Open the full dossier before deciding. If it is worth the price to you, register the purchase and turn usefulness into direct development support.
What happens when different records do not tell the same story?
Ecos do Cerrado is a narrative investigation game for PC set in present-day Goiânia. The player cross-checks documents, maps, photographs, testimony, architecture, objects and conflicting versions of events.
The system organizes; the player interprets.
The proposition is not to click until the game reveals the answer. The experience depends on noticing differences, absences and relationships between evidence. The tool can record and test; interpretation remains with the player.
Space
Environment, architecture, object placement and observable detail.
Record
Documents, maps, photographs and archives.
Voice
Testimony, memory and competing versions of events.
Observe the space
Investigation begins in the world.
Find evidence
A clue should be discovered, not merely listed.
Open and read
The document has to be understood.
Compare another source
Difference between sources creates tension.
Form a relationship
The relationship comes from the player.
Test the hypothesis
The system checks whether it is supported.
Understand the consequence
The next step exists because something was understood.
Practice without spoilers.
Source A: “The project was delivered on schedule with no meaningful interruption.”
Source B: “Residents report three weeks of stoppage and blocked street access.”
Question: what relationship would you test first?
What would you verify before accepting that relationship?
This example is generic and is not part of the game's canon.
A language decision.
The public devlogs record a consistent direction: avoid turning rooms into hotspot dashboards and let interface appear when it has a purpose. The ambition is to read the space before the menu.
Environment first. Interface when it helps investigation.
A development demo, not a final game disguised as one.
The public page presents build 0.9.0 v5 for Windows x86_64 and explicitly says the project remains in active development, with bugs, inconsistencies and systems still evolving. Later internal candidates are not automatically promoted as the public build.
What funding changes.
The public presentation also separates prototype from release target: development voices and AI-assisted translation help validate the project, while the funded target includes human performance, professional editing/localization, LQA, external QA, accessibility and release polish.
Build a supported reading.
Strongest evidence:
Source that most challenges it:
Current hypothesis:
What would make you change your mind?
Small payments do not “finish the game”. They buy risk reduction.
The public production plan separates development, QA, UI/UX and accessibility, localization/LQA, audio, release, marketing assets and contingency. Individual support contributes to that path; it is not equity, financial return or permission to alter canon.
You helped keep the investigation moving.
Write your name or pseudonym here and save this page as PDF.
This is a symbolic receipt and does not replace the financial/tax receipt issued by the payment method.