Every visual novel with a small, enthusiastic fandom eventually accumulates guides that disagree with each other, and some of them are confidently wrong. Reading them is not difficult if you have a method. The method is simple: sort every claim into three buckets — implemented, planned, or unverified — and refuse to let a claim move buckets because it appears often enough.
The Freak Circus has three unusual properties that make bad guides common: the game is a prototype with a single implemented ending, its cast has published measurements but no published ages, and a lot of the interesting character material comes from fandom wiki pages rather than developer posts. Each of those has produced a specific category of misinformation.
The three buckets
- Implemented. You can reach it in the public build right now. One ending qualifies: "Missing", the bad ending on Day 1 reached by doing nothing while Pierrot is being mocked.
- Planned. The developer has named it, and it is not in a build. Four qualify: Pierrot, Harlequin, Protagonist, and "All together".
- Unverified. No first-party source, but repeated widely. Save paths, slot counts, autosave schedules, exact ages and birthdays, total completion time, Day 3 release dates, and any specific number of endings.
Most factual arguments about this game dissolve once every sentence is in a bucket. "The game has five endings" is a merge error: one implemented ending plus four planned ones, presented as a confirmed total the developer never gave.
Five questions to ask a guide
- Which build is this about? Version 0.2 is the current public build. A guide that never names a version is describing the author's memory.
- Does it link a source? An official page, a devlog entry, an AMA answer, a Tumblr post. A guide that cannot point at one of these is interpreting.
- Does it mark fandom material as fandom material? The costume details, the reason Pierrot is silent, Harlequin's role in Columbina's death — all useful, all from the fandom wiki, all worth labelling.
- Does it say where the spoilers start? A guide that spoils Day 2's opening without warning is not more useful than one that does.
- Does it hedge where it should? "Planned", "not implemented", "unconfirmed" are not weaknesses in a guide. They are the parts that will still be true after the next update.
The specific errors worth catching
Romance routes for characters who do not have them
The confirmed route options are Pierrot, Harlequin, both, or neither. There is no Jester route, no Ticket Taker route, and no Doctor route. The developer has described making the remaining characters romance options as a possibility rather than a commitment, and any such route would most likely arrive as an add-on or DLC. Guides that describe a Ticket Taker route "unlocked through persistence and careful dialogue", a Doctor "Clean Hands" ending, or a Jester route that "unlocks on Day 2" are all describing things that do not exist. The Day 2 update added characters, animated sprites, a redesigned menu, and an Android version — not new routes.
A "good ending" that does not exist
There are no good endings implemented. The only ending in the build is a bad one, and the romance conclusions that are often described as the "good" outcomes are the same planned endings listed above — unfinished, and not guaranteed to be the outcomes fans expect.
Precise numbers with no source
Specific ages, birthdays, a height for Columbina, a total runtime, an exact number of endings, and a precise save location are all fan inventions dressed as data. The genuine measurements are the developer's height chart and the relative age order — and no numeric age has ever been published for anyone in the cast.
Dates for Day 3
No release date has been announced, and the developer has asked that outside date claims not be repeated. A countdown page is a fan estimate with a clock on it. The only date that counts is the one on the official itch.io page or in an official post.
Reading sources without trusting them blindly
The fandom wiki is genuinely valuable for this game and it is worth using — with a specific caveat. It compiles character material from the game's own scenes, which means its character descriptions are close to the source, while its inferences and dates are not first-party. The practical habit is to keep the two apart while you read.
- What the wiki does well: costume detail, in-fiction explanations, relationship summaries, and the record of what the developer has answered in AMA threads.
- What the wiki gets wrong: numeric ages and most birthdays, a height for Columbina, and readings of ambiguous story events stated more firmly than the evidence allows.
- What to do: copy the description, keep the hedge.
Ask: "Could the developer contradict this tomorrow without anyone noticing?" If yes, the claim needs a hedge or an attribution. "The developer has confirmed eight ticket types" cannot be quietly contradicted. "Harlequin is 21" can, and has been.
One more thing: where you got the game
Before evaluating any guide, check its source links. The developer has stated that the itch.io page is the only official page for the game and has asked that the game not be re-uploaded or reposted. There is no official Discord server, so every server that is not linked from the official itch.io, Tumblr, Patreon, or Bluesky pages is fan-run or unauthorised.
Guides that push a "mirrored download", a "verification" program, or a "patched" installer are not guides at all. Never install a separate program or disable antivirus protection to obtain this game.
A working habit
Read a guide's scope note first. If it says which build it covers, where its sources are, and which parts are still in development, the rest of it can be trusted in proportion. If it opens with a confident claim about an ending that does not exist, put it down — that is a guide that will confidently tell you the wrong thing about everything else too.
For the verified version of the most-searched topics, start with the endings guide, the height guide, and the saving guide — all of which separate confirmed facts from unverified claims in the same way.