Publisher / co-development due-diligence dossier ITCH.IO + WINDOWS DEVELOPMENT STATUSITCH.IO + STATUS DE DESENVOLVIMENTO WINDOWS

ECOS DO CERRADO

A Brazilian narrative investigation game about evidence, memory and the historical layers of Goiânia.

The city is not a backdrop. It is the case file.

DeveloperWilson Junior · Nonolho Games
EngineGodot 4.7.1
Current platformWindows / PC
Itch.io candidateCandidato itch.ioP82R25B / 0.8.9.146 · Windows x86-64
Structure8 chapters · chapter-by-chapter production
ITCH.IO CANDIDATEP82R25B / 0.8.9.146LATEST VALIDATEDP82R30 S6B / 0.8.9.151OPEN GATEGATE ABERTONative Windows human golden pathGolden path humano no Windows nativo
11:31
Latest gameplay · 30 Aug 2026Gameplay mais recente · 30 ago 2026

See the current investigation in motionVeja a investigação atual em movimento

The newest gameplay asset in the official Wix Media library: approximately 11 minutes 31 seconds of investigation flow, interface, documents, environments, pacing and atmosphere.O asset de gameplay mais recente na biblioteca oficial do Wix Media: aproximadamente 11 minutos e 31 segundos de investigação, interface, documentos, ambientes, ritmo e atmosfera.

Latest gameplay assetGameplay mais recente~11 min 31 sec · uploaded 30 Aug 2026~11 min 31 s · enviado em 30 ago 2026
Hosted review assetAsset de análise hospedadoWix Video · 1366×768 · 720p
Open latest master ↗Abrir master mais recente ↗
01
Executive snapshot

What a publisher needs to understand in five minutes

Ecos do Cerrado is beyond concept stage: it has a mature playable Chapter 1, an itch.io distribution path, current Windows development candidates, a defined eight-chapter narrative architecture and a clear production gap that can be scoped into co-development work packages.Ecos do Cerrado já passou da fase conceitual: possui um Capítulo 1 jogável e maduro, uma rota de distribuição no itch.io, candidatos atuais para Windows, arquitetura narrativa definida em oito capítulos e um gap de produção claro que pode ser transformado em work packages de co-development.

01

Playable proof

Chapter 1 is the current quality reference. The latest itch.io-targeted candidate is P82R25B / 0.8.9.146; the newest validated internal checkpoint is P82R30 S6B / 0.8.9.151.O Capítulo 1 é a referência atual de qualidade. O candidato mais recente direcionado ao itch.io é P82R25B / 0.8.9.146; o checkpoint interno validado mais novo é P82R30 S6B / 0.8.9.151.

08

Chapter structure

The full game is planned across eight historical chapters. Chapters 2–8 already have story, characters and text foundations.

PC

Platform reality

Windows / PC is the current validated production target. Console porting is a later feasibility and budget stage, not a finished capability.

OPEN

Commercial structure

Co-development, production services, publishing, financing or a hybrid structure can be discussed. No completion budget is represented as already committed.

StageAdvanced development / Chapter 1 reference production
Current teamSolo-led project seeking production partners
Completion capitalNot yet committed — financing is being structured
Immediate objectiveScope remaining production into milestones, team needs and a realistic budget
02
Player experience

Investigation through material evidence

Documents, maps, photographs, testimony, architecture and conflicting traces are not supporting flavor. They are the primary language of play.

  1. 01

    Collect

    Records, maps, testimony and evidence enter the investigation.

  2. 02

    Examine

    The player reads, zooms, compares and interrogates material through the investigative interface.

  3. 03

    Connect

    Relationships are established between people, places, dates and sources.

  4. 04

    Reconstruct

    A historical layer is assembled from connected evidence.

  5. 05

    Reframe

    The reconstruction changes the hypothesis and opens the next line of enquiry.

Creative pillars
Documentary investigationGoiânia / Cerrado identityMemory and evidenceNonolhoThoranicoCinematic presentation
Narrative rule

Historical decades are reconstructed through documents and evidence. The player remains anchored in the present; the project does not frame the experience as literal time travel.

03
Positioning

Why this project is distinct

The pitch is not “another detective game.” Its identity comes from the intersection of documentary investigation, a specific Brazilian city, original diegetic technology and an eight-chapter historical structure.

A

Evidence-first

The investigation depends on primary material, not only dialogue-tree deduction.

B

Brazilian specificity

Goiânia and the Cerrado provide an architectural, cultural and historical identity that is central to the product.

C

Original in-world system

Thoranico functions as a diegetic analysis layer that connects mechanics and fiction.

D

Long-form historical arc

Eight chapters allow the investigation to move across different periods without abandoning the same central city and thematic frame.

Intended audiencePlayers who value narrative investigation, historical mystery, document-driven discovery and atmosphere.
Market claim disciplineThis page does not invent sales forecasts, wishlists, awards or audience size.
04
Content architecture

Eight chapters, one city, changing historical layers

Chapter 1 covers the foundation of Goiânia and is the current playable reference. Chapters 2–8 already have narrative foundations and are being refined chapter by chapter rather than claimed as finished runtime content.

Playable referenceNarratively structured / production remaining
05
Build & technical due diligence

Separate itch.io distribution status from internal development authoritySeparar o status de distribuição no itch.io da autoridade interna de desenvolvimento

The latest package prepared specifically for itch.io is P82R25B / 0.8.9.146. Development has already advanced to the validated P82R30 S6B / 0.8.9.151 checkpoint. Native Windows human golden-path validation remains the explicit gate before promoting a newer build as definitively public.O pacote mais recente preparado especificamente para itch.io é P82R25B / 0.8.9.146. O desenvolvimento já avançou para o checkpoint validado P82R30 S6B / 0.8.9.151. A validação humana do golden path em Windows nativo continua sendo o gate explícito antes de promover uma build mais nova como definitivamente pública.

Latest itch.io-targeted packagePacote mais recente para itch.io

P82R25B / 0.8.9.146

PlatformPlataforma
Windows x86-64
PackagingEmpacotamento
5 ZIP + 1 BAT · QA transport gates PASS5 ZIP + 1 BAT · gates de QA do transporte PASS
Public gateGate público
Native Windows human golden path still required before definitive promotionGolden path humano no Windows nativo ainda obrigatório antes da promoção definitiva
Open itch.io project page ↗Abrir página do itch.io ↗
Latest validated internal checkpointCheckpoint interno validado mais recente

P82R30 S6B / 0.8.9.151

Engine
Godot 4.7.1
Validated scopeEscopo validado
S1–S6B corrections validated; live PT/EN refresh includedCorreções S1–S6B validadas; refresh PT/EN ao vivo incluído
Next gatePróximo gate
S7 consolidated audit + candidate golden path; human Windows gate remains separateS7 auditoria consolidada + golden path do candidato; gate humano Windows permanece separado
Chapter 1 recorded gates

Current evidence inside the latest package

14 / 14Chapter 1 audit controls · score 100
68 / 68Documents tracked
61 / 61Hotspot centers clickable at 1280×720 and 1024×576
PlayablePrologue with zoom, voice and subtitles
ImplementedDocument viewer zoom / pan and right-click return behavior
ImplementedSave / CONTINUE flow and Chapter 2 firewall
ImplementedImmersive office sequence with Clarice and Saint-Hilaire / map material
ImplementedChapter ending returns to menu after “CONTINUA EM 1940”

These are recorded package gates, not a claim that the complete eight-chapter game is release-ready, certified or finished.

06
Production reality

What is built, what exists in narrative form, and what still needs production

The project is intentionally presented without collapsing “written” into “implemented.” That distinction is central to realistic scoping.

AreaCurrent stateProduction need
Chapter 1 runtimePlayable and robust referencePolish, human QA, regression and feedback-driven refinement
Chapters 2–8 narrativeStory, characters and texts already structuredNarrative refinement, implementation, integration, pacing and chapter-specific content production
EngineeringGodot project and Chapter 1 systems existCo-development capacity, tooling, integration and runtime stabilization as scope requires
Art / visual polishEstablished visual identity and playable presentationAdditional artist support and refinement may be required chapter by chapter
Audio / voicesAudio is part of the current experienceHuman voice production, immersive soundtrack and professional finishing should be scoped with specialists
QA / releaseAutomated / package checks exist for the current checkpointHuman golden path, broader QA, accessibility, regression, release engineering and store readiness
Console platformsNo validated console build is claimedPorting feasibility, certification scope and budget as a separate future stage
07
Production scenariosCenários de produção

Three ways to scope the next stage — without inventing a budgetTrês formas de estruturar a próxima etapa — sem inventar um orçamento

These are planning envelopes, not quotes or funding asks. Their purpose is to show how the same project can be financed and produced at different levels once a co-development partner turns the remaining work into milestones and real costs.Estes são envelopes de planejamento, não cotações nem pedidos de funding. O objetivo é mostrar como o mesmo projeto pode ser financiado e produzido em níveis diferentes quando um parceiro de co-development transformar o trabalho restante em milestones e custos reais.

S2 · ENHANCED

Enhanced Production

The PC completion plan plus a larger specialist layer for presentation, accessibility and launch quality.O plano de conclusão no PC com uma camada maior de especialistas para apresentação, acessibilidade e qualidade de lançamento.

  • Everything in Core PC CompletionTudo do Core PC Completion
  • Expanded visual polish and chapter-specific art supportPolish visual ampliado e suporte de arte específico por capítulo
  • Professional voice, soundtrack and audio finishing as scopedVoz profissional, trilha e acabamento de áudio conforme escopo
  • Broader accessibility, localization, UX and launch-readiness supportAcessibilidade, localização, UX e preparação de lançamento mais amplas
Budget statusStatus do orçamentoscope being costed with co-development partner
S3 · EXPANSION

PC + Console Expansion

A later expansion path that adds console feasibility and porting only after the PC production base is stable enough to justify it.Uma rota posterior de expansão que adiciona viabilidade e porting para consoles somente quando a base de produção no PC estiver estável o suficiente para justificar isso.

  • Everything required for a stable PC release candidateTudo necessário para um release candidate estável no PC
  • Godot console feasibility and middleware / porting assessmentAvaliação de viabilidade Godot em console e de middleware / porting
  • Platform-specific UX, performance and certification workUX específica de plataforma, performance e trabalho de certificação
  • Separate platform milestones; no validated console build is claimed todayMilestones separados por plataforma; nenhuma build de console validada é alegada hoje
Budget statusStatus do orçamentoscope being costed with co-development partner
The numbers come after the scope.Os números vêm depois do escopo.

No scenario is represented as financed or committed. Once technical ownership, staffing, milestones and external-service costs are validated, each scenario can support a publisher, fund, investor, grant or third-party-financed co-development conversation without inflating the project to fit a funding source.Nenhum cenário é apresentado como financiado ou comprometido. Depois que responsabilidades técnicas, equipe, milestones e custos de serviços externos forem validados, cada cenário poderá sustentar uma conversa com publisher, fundo, investidor, edital ou co-development financiado por terceiro sem inflar o projeto para caber em uma fonte de capital.

08
Production framework

A milestone structure before a budget number

The current commercial goal is to turn the remaining game into measurable work packages. A credible completion budget should come from that scope, not from an arbitrary top-down number.

M0

Technical & production diagnosis

Review build, architecture, content pipeline, chapter backlog, QA gates and staffing assumptions.

OUTPUTScope + risks + ownership map
M1

Chapter 1 hardening

Human QA, regression, UX/UI polish, visual and audio finishing, accessibility and release-readiness criteria for the reference chapter.

OUTPUTCommercial-quality reference chapter
M2

Chapter production pipeline

Convert chapters 2–8 from narrative foundations into repeatable runtime production packages.

OUTPUTValidated pipeline + chapter milestones
M3

Full-game integration & QA

Cross-chapter systems, saves, regression, localization, audio, performance and final PC release readiness.

OUTPUTPC release candidate target
M4

Platform expansion

Only after PC stabilization: evaluate console porting, certification, platform-specific UX and commercial viability.

OUTPUTSeparate platform scope
09
Partnership thesis

A partner should accelerate production without erasing authorship

The project is open to different commercial structures. The desired outcome is a professional production relationship with clear responsibilities, milestones, budget logic and aligned incentives.

NONOLHOIP · narrative · characters · investigation · creative direction
PRODUCTION PARTNEREngineering · QA · art · audio · production · release support
PUBLISHING / CAPITALFunding · distribution · go-to-market · platform reach

Work-for-hire / scoped co-dev

Defined packages, milestones and fees for the areas where the partner adds production capacity.

Publishing

Capital, distribution and market execution structured around a completion plan and commercial terms.

Hybrid structure

A mix of paid production, deferred compensation, revenue share or other aligned structures can be explored if viable for both sides.

Third-party financed co-dev

Publisher, fund or investor finances a qualified production partner while Nonolho retains the project’s creative leadership.

Current financing status

No completion capital is currently represented as committed.

The next useful number is a professional scope-based budget. That budget can then support publisher, grant, fund or investor conversations.

10
Commercial boundaries

Negotiable terms are not the same thing as automatic IP transfer

Publishing economics and production responsibilities can be negotiated. Narrative ownership and canon are protected unless a separate human agreement explicitly says otherwise.

Open to negotiation
  • Publishing structure
  • Recoup
  • Revenue share
  • Service scope and milestones
  • Territories and distribution
  • Marketing commitments
  • Platform support
Protected unless explicitly negotiated
  • Narrative canon
  • Characters
  • Historical investigation and clues
  • Documents and evidence logic
  • Solution and ending
  • Underlying narrative IP
  • Creative direction
11
Review package

Start with the game. Then inspect the dossier.

Every link below serves a different due-diligence purpose: playable proof, fast visual understanding, long-form worldbuilding or public project context.

12
Open gates & risks

The gaps are visible enough to scope

A serious publisher page should make the risk surface inspectable. These are the current areas that partnership and production planning need to close.

R1

Financing

No completion capital currently committed. Mitigation: scope first, then structure publisher / fund / investor capital around a credible budget.

R2

Human QA

Latest internal package still needs a real-Windows golden path. Mitigation: explicit validation gate before promotion.

R3

Chapters 2–8 runtime

Narrative foundations exist; implementation remains. Mitigation: chapter pipeline and repeatable work packages.

R4

Art & audio scale

Later chapters may require specialist visual, voice and music capacity. Mitigation: scope specialists per chapter rather than assume one flat cost.

R5

Release readiness

Full-game regression, accessibility, localization, store and release engineering remain future work. Mitigation: dedicated M3 integration milestone.

R6

Porting

Console viability is unvalidated. Mitigation: separate feasibility, certification and budget stage after PC stabilization.

Direct publisher line

If the fit is real, the next conversation is about scope

The immediate goal is not to force a pre-defined deal structure. It is to identify the right production role, responsibilities, milestones, budget logic and commercial path for the project.

Developer
Wilson Junior
Studio
Nonolho Games
Email
wilsaoo@gmail.com
Location
Goiânia · Goiás · Brazil
X
@nonolho