- Dev mode in Anomalous Coffee Machine means unlocking debug access to speed up word discovery and testing
- The game runs on Godot, so launch flags, save edits, and external tools all work
- Save scumming is the safest method — back up saves before risky word inputs
- Always back up your save file before any manual edit to avoid losing progress
- Dev tricks are for single-player use only and do not affect achievements fairness
What Dev Mode Means in Anomalous Coffee Machine
Anomalous Coffee Machine is a word-experimentation horror game where you type inputs into an SCP-294-style machine and watch the character transform. With 730+ discoverable words and 680+ transformations, cataloging every outcome through normal play takes dozens of sessions. That is where dev mode comes in: a set of debug-oriented techniques that let you test words faster, inspect unlock states, and skip repetitive sessions.
The game is built on the Godot engine, which shapes what is possible. Godot titles typically store user data in a predictable directory, respond to launch arguments, and keep save data in editable text formats — all of which opens the door to developer-style testing in the retail build.
The public release may not expose a full debug overlay. Behavior of launch flags and save formats depends on the build (v0.9.4 on itch.io vs. the Steam release). Always back up your saves before experimenting, and never use these techniques outside single-player.
Dev Mode Methods Compared
There is no single official "dev mode" toggle. Instead, players combine several approaches depending on their goal. Here is how the main methods stack up:
| Method | Difficulty | Risk Level | Best For |
|---|---|---|---|
| Debug launch flag | Easy | Low | Checking overlay and unlock state |
| Save file editing | Medium | Medium | Unlocking word lists manually |
| Cheat Engine flags | Hard | Medium | Marking endings as seen |
| Save scumming | Very Easy | Very Low | Testing individual words safely |
| Mod support (official) | Medium | Low | Custom words and events |
Launch Flag Debugging
- Add a debug argument to launch options
- Check for an overlay showing word/unlock state
- Fastest way to inspect what the game tracks
Save File Editing
- Locate saves in Godot's app_userdata folder
- Edit the discovered-words list directly
- Highest risk — always keep a backup copy
Cheat Engine Flags
- Attach to the game process
- Search and set ending flag values
- Best for completionists chasing final unlocks
Save Scumming
- Copy the save before feeding a word
- Restore if the result is redundant
- No tools required, zero risk
The game officially supports mods on itch.io, including custom words and events. If your goal is testing new vocabulary, the mod route is cleaner and safer than hacking saves.
Step-by-Step: Enabling Debug Access
Follow this sequence to set up a dev-style testing environment. Each step builds on the previous one, so complete them in order.
Back Up Your Save Data
Locate the Godot user data folder (typically under app_userdata/AnomalousCoffeeMachine in your user directory) and copy the entire folder elsewhere. Every later step assumes this backup exists.
Add the Debug Launch Flag
In your Steam library, right-click Anomalous Coffee Machine, open Properties, and add the debug flag (e.g., anomalous-coffee-machine.exe --debug) to Launch Options. Launch the game and watch for a debug overlay displaying word and unlock state.
Inspect the Word List
With the overlay active (if your build supports it), check which words are marked discovered. Note the format of entries — this tells you how to structure manual save edits.
Test Words with Save Scumming
Before each machine input, copy your save. Feed the word, observe the result, and restore the save if the outcome was redundant. This catalogs effects rapidly without polluting session state.
Clean Up and Restore
Remove the launch flag when done, and restore your legitimate save backup if you want to return to a clean progress state.
A malformed save file can reset your progress entirely. Never edit the file while the game is running, and validate the format against an untouched backup before saving changes.
What Dev Mode Helps You Unlock
Debug techniques map directly to the game's completion targets. Here is what each approach helps you finish faster:
| Target | Normal Play Time | Dev-Assisted Method |
|---|---|---|
| Discover 730+ words | Dozens of sessions | Save scumming + word list edits |
| See all endings | Multiple full runs | Ending flag manipulation |
| Trigger hidden events | Trial and error | Save restore between attempts |
| Contradictory word pairs | Rare luck | Rapid input/restore cycles |
| Ending-gated words | Reach a major ending first | Flag the ending, then test |
Steam achievements for Anomalous Coffee Machine unlock based on in-game milestones. Using dev tricks to preview content is fine for a single-player game, but consider earning story achievements legitimately first — the branching dialogue is the heart of the experience.
Dev Mode Safety Checklist:
- Back up the full save folder before any edits
- Test launch flags on a disposable save first
- Keep a master save with legitimate progress
- Remove debug flags before normal play sessions
- Verify save file format against a clean backup
Risks, Rules, and Responsible Use
Every dev technique carries trade-offs. Editing saves can corrupt progress; external memory tools can misbehave after game updates change flag values; and skipping sessions means skipping the dialogue that makes the game interesting. The developer (HoruBrain) actively updates the title — ACM2 launched in December 2025 and ACM3 was announced with a trailer in 2026 — so save formats and flag layouts may shift between versions.
For legitimate help, join the official Discord (discord.gg/horubrain) or browse the devlog on the itch.io page, where the developer posts update notes, new word additions, and community-inspired content.
Recommended usage guidelines:
- Use save scumming as your default testing tool — it is safe and tool-free
- Reserve save editing for word cataloging, not progression
- Re-verify Cheat Engine values after every patch
- Never distribute modified saves for multiplayer or shared contexts
FAQ
Q: Is there an official dev mode in Anomalous Coffee Machine?
The public release does not ship with a formal dev mode toggle. However, since the game is built on Godot, debug launch flags, editable save files, and official mod support provide equivalent developer-style access for testing words and outcomes.
Q: Where are the save files located?
Saves live in the Godot user data directory, typically under app_userdata/AnomalousCoffeeMachine in your operating system's user folder. Always copy the entire folder before editing anything.
Q: Can dev mode unlock all 730+ words instantly?
Save file editing can mark words as discovered by adding entries to the discovered-words list, but the exact format depends on the build version. The safer route is save scumming: back up before each input, test the word, and restore if needed.
Q: Will using these tricks break Steam achievements?
Single-player experimentation generally does not disable achievements, but heavily modified saves can behave unpredictably after updates. Keep a clean backup of legitimate progress and earn story achievements normally where possible.