About this guide
This is an independent guide to Escape Academy 2: Back 2 School, a puzzle game developed by Coin Crew Games and published by iam8bit Presents, released on 5 November 2026. The site is not affiliated with either company and takes no money from them.
It exists because the game is two days old and most of the questions players are asking already have answers - just not in one place. The 41 achievements have public unlock rates. The price and the five purchase options are on the store. The launch-day hotfix named exactly what it fixed. All of that is checkable, and none of it was collected anywhere on launch week.
Where the numbers come from
Every figure on this site traces to one of four sources, and the page it appears on says which:
| Source | What it provides |
|---|---|
| Steam store API for appids 3296060, 4198180, 4732000, 5370630, 5370680, 1812090 | Price, platforms, categories, PC requirements, languages, release dates |
| Steam announcement feed for appid 3296060 | The ten official posts between July and November 2026, including the 6 November hotfix |
| Global achievement percentages for appid 3296060 | All 41 unlock rates, pulled 7 November 2026 |
| Steam forum, including the developer's pinned FAQ | Player reports, developer replies, campaign length, cross-play rules |
Where a page quotes a player report, it says so and gives the thread's substance rather than a paraphrase that flatters the site. Where a page quotes the developer, the quote is verbatim. Where the game has published nothing - a chapter count, an expansion date, an achievement's display name - the page says that too, rather than filling the gap.
What this site will not do
Four things, stated so you can hold it to them:
- No invented puzzle solutions. The studio has not published any, and the rooms that generate the most questions have no settled community answer yet. A confident wrong solution costs a reader an evening.
- No fabricated numbers. No frame-rate benchmarks, no player counts, no sales figures. If a number is not in one of the four sources above, it is not here.
- No competitor links in the body. Sources are official. Other guide sites are not cited, quoted or linked.
- No content farms. Every page answers one question and says how it knows.
What this site covers, and what it deliberately skips
The scope is everything a player needs in the launch fortnight: what the game is, what it costs, whether it runs, how co-op works, where the puzzles stop people, and what has broken since launch. Twenty-three pages on those subjects, all written from official sources.
Four things are out of scope, and each has a reason rather than a policy:
| Not covered | Why |
|---|---|
| Step-by-step puzzle solutions | The studio has published none, and the rooms that generate the most questions have no settled community answer. A guessed solution wastes an evening. |
| Character or story analysis | The game is two days old and the story is the part reviewers liked least. There is nothing useful to say yet. |
| Codes | The game has no code system. Escape bucks are earned in-game. |
| Tier lists or stat tables | There are no stats to rank - no weapons, no builds, no damage numbers. |
What replaces those is the thing this site can do better than a generalist outlet: the numbers. All 41 achievement unlock rates in one table, the full price and SKU breakdown, the patch contents quoted verbatim, and the exact co-op limits.
How a page gets written
Four steps, in this order:
- Collect from official sources first. The store API, the announcement feed, the achievement percentages, the pinned developer FAQ. If a fact is not in one of those, it does not go in as fact.
- Read the player reports, and label them as such. The Steam forum is where the stuck points and the bugs surface, and several pages here exist only because a thread had no answer on it. Where a claim comes from a player rather than the studio, the page says so.
- Check the claim against a second source where one exists. Prices cross-check against two announcements. Platform lists cross-check against the store and the launch post. Bug reports cross-check against the developer's replies.
- Write it, then read it back for what it does not say. A page that stops where the evidence stops is more useful than one that fills the gap, and it is also the only kind that stays true next week.
Corrections
If something here is wrong, the fastest route is email - the address is on the contact page. Corrections that come with a source get applied first, because a claim with a link behind it is a five-minute fix and a claim without one is an afternoon.
The site carries a checked date on every page. The build it is written against is v1.0.20261105.001, the version introduced by the 6 November hotfix, and the update timeline tracks what has shipped since.
Who writes it
One person, working from public sources, on a site that runs no ads at the time of writing. That is worth saying plainly because the alternative - an unattributed "editorial team" - is how most guide sites describe a content pipeline.