Identify the build before following a guide
Three different addresses have different roles: this .org portal provides the player and these guides; the player opens the separate .online website ↗; HoruBrain’s itch.io page ↗ is the developer’s release source. An update to one does not identify the build running on another.
Before trying a word or a sequence, note the host, date and any version label visible in your game. If no build label is shown, record “not shown” rather than guessing. ACM1 and ACM2 guides, and guides for a different ACM3 build, are not evidence that an input works in your session.
Checked on : the official page lists v0.1.2 downloads. The developer’s v0.2 announcement ↗ distinguishes the public build from the Patron release at the time of that announcement. These release labels do not verify the independent embedded website’s version.
Follow one word from input to inventory
- Give the game input focus. Click or tap the input area inside the game. The portal toolbar and your browser’s address bar are separate from that field. Follow any instructions displayed by the source website.
- Enter one word and keep its exact spelling. Use the game’s own submission control. Do not assume a result name, a transformation name or a word from a previous game is an accepted input.
- Read the immediate response. If the game reports an unrecognised word or another condition, record that message before changing anything. If a cup is created, look for it in inventory and note its displayed label.
- Choose one next action. The developer describes drinking, offering a cup to a neighbour, and selling online. Follow the options actually available in your build. Record the recipient or action separately from the word.
- Compare one change at a time. Changing the word, recipient and sequence together makes it difficult to tell what caused a different result. A repeat in another build is a separate observation.
This is a way to observe the game, not a promise that every input succeeds or that an action is reversible. No particular word, price, recipe, coin cost or outcome is certified by this page.
Keep input words, cup labels and outcomes separate
- Input word
- The exact text you submitted to the machine.
- Cup label
- The name displayed on the item you received. Copy what you see; do not silently replace it with the word you remember typing.
- Action and outcome
- What you did with that item, followed by the message or change you observed. A cup existing in inventory and a later transformation are different observations.
A name shown in a gallery or another guide may describe a result rather than an accepted keyboard input. Likewise, a combination or an ordered sequence is not necessarily a single machine word. Check the source and build before treating these as interchangeable.
Copy a simple experiment record
Use this blank worksheet in your own notes. It contains no sample results or untested words.
Date / browser: Entry host / visible build: Exact word entered: Machine response: Cup label in inventory: Action / recipient / earlier steps: Observed result: Repeat result / differences:
For a failed attempt, keep the response and starting conditions. For a successful attempt, a non-explicit screenshot of the input or inventory label can help preserve spelling and context. Keep private information and explicit scenes out of public reports.
Loading or input not responding
Nothing receives your typing: first check whether the text went into the browser address bar or a portal control. Return focus to the game’s own field. A page that is still loading and a game rejecting a submitted word are different problems.
The game displays a rejection: preserve the exact message, spelling, host and build. Check the instructions for that release. Repeatedly reloading the portal is not a way to make an unsupported word valid.
The embedded area stays blank: allow the source time to load, or use Original site to open it directly. The footer’s “Frame navigation ended” message only describes the frame event; it does not prove that the internal game is ready. The portal cannot repair files controlled by the remote host.
On a phone: the developer lists touchscreen input for its release, but the separate embedded host may serve a different build. Try the game’s displayed touch controls and use Fullscreen or Original site for more room. This is not a phone-hardware compatibility test.
Use portal controls without losing your place
- Guide links
Help from the homepage opens in a separate tab so the existing game frame remains in place. Reading the notes below the player does not reload it.
- Fullscreen
Changes the surrounding display where the browser supports it. It does not save, reset or unlock game content.
- Reload
Replaces the embedded frame. Unsaved progress may be lost; it is not an in-game save or recovery command.
- Original site
Opens the configured external website in another tab. Do not assume that the new context shares or transfers progress.
Saving progress before you reload
Read the save-progress and website-data guide before refreshing, changing browsers or clearing site data. It explains what the portal’s code does and which game-saving details remain unverified. This portal does not read or back up the separate website’s saves.
Sources and verification scope
The basic gameplay sequence and listed input devices come from the developer’s public release page ↗. Portal-control descriptions come from this website’s configuration and button implementation. The checklist and blank record above are original observation aids, not a tested word database.
We have not verified an exhaustive ACM3 word list, individual recipes, transformation totals, a complete walkthrough, the embedded build’s save behavior or its version. Third-party claims are not presented here as our playtest results. For the portal’s identity and data services, see About & source and Privacy.
Reviewed on 17 October 2026. Non-explicit guidance for an independent 18+ portal. The source retains its own age confirmation and access rules; this website does not bypass them.