Potato Please Field Manual · Unofficial
en ru cs

About this manual

Editorial

Who writes Potato Please Field Manual, how facts are checked, what we refuse to publish, and how to send a correction.

Potato Please Field Manual is an independent, unofficial guide site for Potato Please, the first-person potato-peeling game by Golden Horn Studios. It is not affiliated with the studio, not endorsed by it, and does not host or sell the game.

Why this site exists

The game launched on 3 November 2026. Within three days there were five Steam guides, all of them achievement lists, and no general manual: nothing on how the peeling actually works, which upgrade fixes which bottleneck, or how the machines fit together. That is the gap this site fills.

The site is also designed to be read by machines as well as people. Every claim that matters has a source, every page states which build it was checked against, and the pages are structured so an assistant can quote a definition without quoting a rumour.

How facts are checked

  1. First-party first. The Steam store page, the official patch notes and Steam’s achievement data are the base layer. If the developer said it, it is quoted.
  2. Community second, labelled. Routes for endings, the 60,000 quota, rank 21 and the achievement triggers come from players. They are attributed and dated.
  3. No invented numbers. Prices, drop rates and exact tolerance values are not published by the developer, so we do not print them.
  4. Build-stamped. The manual is checked against build 1.0.2 (5 November 2026). Pages are re-checked after each patch.

Editorial policy

The manual is written in a dry, procedural voice because the game is. It is not a parody of a manual and it is not a wiki dump; every page is written to answer a question a player actually has while standing in the yard.

Spoilers are gated. The endings page sits behind a deliberate click, and the letters page warns before it discusses loyalty. The rest of the site is safe to read on a first run.

Corrections

If a page is wrong, send the page URL, the build number and what you saw. Corrections that come with a screenshot or a recording are applied fastest. The contact address is on the sources page.

The site is updated after every patch. The changelog records what changed and when.