Development Status of Epstein Island Game: Prototype 0.12.0, What Works and What Is Missing

Development status: a prototype numbered 0.12.0

The browser build carries version 0.12.0 and calls itself a prototype in its own text at every turn. It runs without an account and without a download, and there are also packages for Windows, macOS, and Linux. All of it is playable, none of it is finished.

In parallel, the actual build is being made in Unity, and that is the main project. It has not been released, which is why there are no tested system requirements for it either. For the browser, it is simple: a current browser with WebGL is enough.

You can tell what these numbers are worth by looking at the website's own content. Characters, weapons, buildings, items, and quests all get pulled from the live game state, not typed in by hand. If something does not work in the game, it does not show up on the site either.

What is still missing, without sugarcoating it

The list sits right out in the open on the homepage. It is short, but it hits points that sting in day to day play, especially the last one.

• Redeeming the license key in-game is still in development, until then the key sits in your account
• The Unity build is the main project and has not been released yet
• No gamepad support, keyboard and mouse plus on-screen arrows on mobile are the tested setup
• No syncing of the singleplayer save across multiple devices
• Old saves can stop working after an update

TipIn singleplayer your save sits on your device, in co-op it sits with the server. If you are planning a longer session, it is safer to play it in one sitting.

Reading the workshop page: states, bars, history

Under Current Work there is no marketing copy, just an overview that rewrites itself every five minutes and after every update. At the top it says who is working on what right now and when the last release went out. If the page is older than half an hour, it says so itself and names the stuck build as the reason.

Every task carries one of five states: open, in progress, done, in review, or live. The state is not just claimed, it is backed by evidence. A build that is live on the island counts as live, one in the review environment counts as in review. Where evidence is missing, it explicitly says manual state next to it. Only intent gets entered by hand: priority, dependency, milestone, next step.

The percentages per area are counted, not estimated: completed tasks divided by all tasks in that area. The dark part of a bar sits live on the island you play, the light part is reviewed and still on its way. Below that runs a history of the last two days with timestamps and names, and the full history goes back weeks.

How it gets built, and why the pace shifts

There is no studio with a shift schedule behind this page. Work often happens in AI sessions that get kicked off and then reviewed, and the tools are named right there, Codex and Claude. Every session reports what it does, and every change to the game gets logged automatically. That is exactly why you can also see the days on the workshop page where little happened.

Nothing reaches the island until it has been built, tested, and checked again. The island itself is rebuilt to scale, with real elevations and buildings placed at their measured spot, and it keeps getting built out further. That explains why something changes almost daily, and why a save from last week is not guaranteed to keep working.

Some things are deliberately only half there. Characters get their voices added gradually: the main characters and the voices from the prologue speak their set lines with pre-recorded clips, the rest follow later. In-game items are technically set up too, but the list is empty. What is not settled does not get claimed.

How updates arrive, and when the full version ships

Updates come often and irregularly. No date gets named for a finished build, and that is a deliberate choice, not an oversight.

In the browser you do not need to do anything for this: open the page and play. The desktop app checks on its own at launch and only fetches the changed files, or you can do it manually through the game menu. The comparison between the two paths is covered in Browser or Desktop.

If you want to know whether checking back is worth it, look at the line showing the last published build. It sits right at the top of the workshop page, and it is more honest than any announcement.

Reporting bugs and sending ideas

Bug reports are explicitly welcome, and there is exactly one email address for everything. There is no phone number, no fixed response time is promised, but every email gets answered.

For your report to turn into an actual entry, three things need to be in it: which operating system and browser you used, what you did, and what happened afterward. A screenshot helps too. For purchase questions, add the order number from your payment email, or the search takes longer.

Ideas go through the same channel. The workshop page has a list of open ideas, the ones picked up move into tasks, and the ones already shipped stay listed as a record. The address and the most common answers are covered on the FAQ page.