How this board works

No backend

There is no server. Every report you file lives in your browser under the ach_reports localStorage key. Export the file to move it between devices, or paste the BBCode export straight into a Steam community guide. The site reads back aggregated community consensus on each achievement detail page; the more reports players paste back, the sharper that consensus gets.

  • Pick an achievement card below and fill in the day, scene, key choice, and any notes.
  • Save the report. It appears in the โ€œYour filed reportsโ€ list and stays until you clear it.
  • Export to JSON for backup, Markdown for wiki/Discord, or BBCode for Steam guides.
  • Reports are timestamped and labelled with the achievement they belong to.

File a new report

15 achievements verified

Each card below is one achievement. The seed summary reflects the current community consensus; the form underneath is where you add your own experience. Trigger conditions for the hidden achievements (KITTY, CASSETTE, ENGING variants) are explicitly community-sourced and should be treated as starting points rather than authoritative fact.

#0

You've Been Warned

Trigger verified

Internal: DISCLAMER

Community consensus

Unlocks the first time the content warning on the main menu is acknowledged. There is no scenario where this is missed on a fresh install.

Typical: Main Menu Confidence: high
#1

Job Application

Trigger community

Internal: JOB_APPLICATION

Community consensus

Plays out during the opening sequence with Mom and the phone call. Radek floats an informal work offer; the achievement fires once the offer is accepted. No formal application paperwork is involved despite the name.

Typical: Day 1 Confidence: medium
#2

First Shift Speedrun

Trigger community

Internal: FAST

Community consensus

Day 1 has a visible countdown during the work shift. Players who scan and place every required product before the timer hits zero report the achievement firing at the end of the shift. Skipping optional dialogue on repeat attempts is the most common time-saver.

Typical: Day 1 Confidence: medium
#3

Beer Pressure

Trigger community

Internal: BEER

Community consensus

Triggers when Radek offers a beer at his place and the player accepts at least once. Reports indicate a single acceptance is enough; drinking heavily afterwards can lock in a different branch, so most players stop after one to keep other endings open.

Typical: Finale Confidence: medium
#4

Ideal Ending

Trigger community

Internal: ENGING_IDEAL

Community consensus

Players describe the Ideal variant as the most balanced resolution of the central relationship arc. The recurring recipe is firm boundaries, honest acceptance of help from supportive characters, and avoidance of open hostility. Frequently paired with the Willpower ending route.

Typical: Finale Confidence: low
#5

WTF Ending

Trigger community

Internal: ENGING_WTF

Community consensus

A deliberately absurd variant. Players are still narrowing down the exact choice mix; the working community recipe is a mix of boundary-setting with deliberately inconsistent choices and engagement with the weirder optional interactions. Treat any step list as a starting point, not a recipe.

Typical: Finale Confidence: low
#6

OK Ending

Trigger community

Internal: ENGING_OK

Community consensus

Often shows up on a blind first playthrough. Players report landing here when they make a mix of firm and compliant choices without committing fully to either the boundary or the compliance path.

Typical: Finale Confidence: low
#7

Worst Ending

Trigger community

Internal: ENGING_WORST

Community consensus

The bleakest variant. Players report it from consistently shutting out supportive characters while still complying with manipulative requests, without crossing into the more chaotic WTF branch. Often mentioned alongside the Wasted ending in community routes.

Typical: Finale Confidence: low
#8

All Endings

Trigger community

Internal: ENGING_ALL

Community consensus

Meta achievement for completionists. Requires seeing the Ideal, WTF, OK, and Worst variants on the same save profile. The realistic minimum is four full playthroughs; save backups before branch points are the common time-saver.

Typical: Multiple Confidence: medium
#9

Cassette Collector

Trigger community

Internal: CASSETTE

Community consensus

Hidden achievement tied to the boombox system. Players report collecting cassette tracks across the relevant days and inserting them into the boombox to confirm registration. Exact tape locations are still being mapped by the community.

Typical: Day 1 to Finale Confidence: low
#10

Money Master

Trigger verified

Internal: MONEY

Community consensus

The in-game coin target is 1000. The visible coin stat caps at 999, so the achievement fires when a separate running total crosses 1000 across days. Players frequently report being stuck at 998 or 999 right before the achievement fires; this is the running total catching up to the cap, not a bug.

Typical: Day 1 to Finale Confidence: high
#11

Kitty 1

Trigger community

Internal: KITTY_1

Community consensus

Hidden achievement. One of four cats placed somewhere in the game world with no in-game prompt. Players report the first cat as the easiest to stumble onto while exploring away from the critical path; no in-game hint is provided.

Typical: Day 1 or Day 2 Confidence: low
#12

Kitty 2

Trigger community

Internal: KITTY_2

Community consensus

Same rules as Kitty 1. Community reports place the second cat in a different scene from the first; each cat registers independently, so finding one does not reveal another.

Typical: Day 2 or Day 3 Confidence: low
#13

Kitty 3

Trigger community

Internal: KITTY_3

Community consensus

Community reports place the third cat further into the story than the first two. Several players note that revisiting earlier scenes after unlocking later ones sometimes reveals new interactions.

Typical: Day 3 or Finale Confidence: low
#14

Kitty 4

Trigger community

Internal: KITTY_4

Community consensus

Considered the rarest cat achievement. Community efforts are still ongoing to pin down a stable location; players who find it are encouraged to document the scene and conditions to help refine the consensus.

Typical: Finale Confidence: low

Your filed reports

Local to this browser

No reports yet. File one from a card above, or import a JSON backup to pick up where you left off.

Common questions

Tool scope
Where are my reports stored?

In your browser under the localStorage key "ach_reports". The page has no backend. Clearing browser data, switching browsers, or using private mode wipes the reports, so export a JSON backup before you switch devices.

Why are the trigger conditions marked as community-sourced?

Only one of the fifteen achievements has a directly verifiable trigger; the other fourteen have logic that the community is still narrowing down from playtest reports. Marking the source explicitly keeps the board honest and matches the provenance standard used across the rest of the site.

What is the difference between the seed consensus on each card and my filed reports?

The seed consensus is the current aggregated community understanding baked into the site. Your filed reports are your own playthrough notes that live in your browser. The two stay separate; future site updates fold exported reports back into the consensus manually.

How do I share my reports with the community?

Export the BBCode format and paste it into a Steam community guide comment, or export Markdown for Discord and GitHub. The exports are grouped by achievement and include day, scene, key choice, result, and notes for each report.

Can I edit a report after saving it?

Not directly. Delete the report and file a new one with the updated details. The export formats preserve the order you filed, so re-filing keeps everything in a clean sequence.