The Lantern of the Laughless Saint Early Access Roadmap

This roadmap page paraphrases publicly stated Early Access intentions for The Lantern of the Laughless Saint. It is not an official publisher timeline graphic. When Steam or NerveLabs publish more precise milestones, we will update.

Stated EA shape

• Length target: less than a year in Early Access
• Update cadence goal: every 1–2 weeks during EA
• Focus: polish plus substantial new content—enemies, areas, equipment, quests
• Systems to deepen: spell crafting, alchemy, fishing, and related mechanics
• After EA: continued free improvements; possible slight price increase
• Future interest: mod support mentioned as a planned additional feature direction

Community loop

NerveLabs emphasizes Discord playtests and Steam community feedback as guiding forces. If you care about the island’s direction, bring bug reports and specific friction notes—not only memes. Link destinations live under Links.

What a good EA player mindset looks like

Expect incomplete UX around systems that are already “fully featured” at launch but scheduled for flesh-out. A spell recipe that feels god-tier in week one may be tuned in week three. Keep light notes; rely on spell crafting and alchemy principles over rigid spreadsheets.

Wiki tracking plan

1. Summarize patches that change guides or tiers.
2. Expand verified controls, maps, and NPC hooks.
3. Revise playstyle tiers when balance shifts.
4. Keep release date accurate if schedules move.

How roadmap ties to prep pages

Before launch, use system requirements and the launch-day checklist. During EA, return to Getting Started only for onboarding friends; veterans should watch this roadmap and the Updates Hub.

Relation to The Holy Fool

Developer messaging positions Laughless Saint as sharing toolkit DNA with a larger successor, The Holy Fool, with improvements flowing between projects. That is context for why EA exists—not a promise that Holy Fool content appears inside this game.

What we will not invent

Exact calendar dates for “alchemy 2.0,” named milestones without sources, or guarantee that every 1–2 week target ships without slip. Roadmaps are intentions. Compare them against live patch notes after August 17, 2026.

Stay flexible, report clearly, and let the Amphitheater—and the patch notes—record how the island grows.

Feedback that actually helps developers

Write reports with: build identity if shown, steps, expected result, actual result, and whether co-op was involved. Attach screenshots. Separate “I died to a funny spell” stories from “UI hid a critical cost” bugs. Good feedback shortens the distance between this roadmap’s intentions and the island you want to inhabit, and it gives our wiki cleaner patch summaries later.

Personal roadmap sync

Make a tiny personal roadmap: systems you want polished, quests you want expanded, co-op friction you will report. Compare it monthly to what actually shipped. That sync keeps disappointment specific and feedback useful. It also tells you which wiki hubs to reread—Systems after progression patches, Guides after traversal changes, Tier List after balance passes.

Content appetite versus polish appetite

Some players want more areas immediately; others want fishing and spell crafting to feel finished. Name your appetite in feedback. Studios cannot prioritize both first every week. Knowing your appetite also tells you which wiki pages to watch—world explorers watch exploration guides, system tinkers watch crafting pages, and everyone watches this roadmap for the next stated focus.

Continuity note for Early Access

Treat roadmap intentions as a compass for feedback: name whether you want content or polish next, file reproducible reports, and reread Systems or Guides when the shipped patch matches your appetite.