The useful message names the page, the item or achievement, the patch you were on, and what the game showed. A screenshot description is enough. 'The wiki is wrong' is not enough to change a row, because the row is already tagged with its source. If your note confirms an unverified price, say so and the status can move to something stronger than a single community site.
This fan guide does not have a public inbox yet. The site owner can set NEXT_PUBLIC_CONTACT_EMAIL and the form below will appear. Until then, corrections are welcome as notes on the data files in the repository.
Questing Goose Studio and tinyBuild run the game. Steam lists support@tinybuild.com. The news posts link a Discord at discord.com/invite/probablystolen. Refunds and purchases are Steam's process, not this website's. Missing achievements, crashed saves, and mod breakage after 1.0.0.6 belong in those channels. This guide can only record what those channels already said in public.
What a useful correction looks like
The page URL, for example /items or /achievements.
The row name, spelled the way the game spells it. Labeller and Labeler have both appeared.
The patch, from the game's version or the newest Steam news title.
The number you saw, and whether it was a buy price, a sale value, or a tooltip.
Whether a second player has seen the same figure. One sighting stays unverified. Two independent sightings can be marked cross-checked.
Do not send a full save file. Do not send a memory-editor table. Do not send someone else's Discord handle as a source unless they published the note themselves. A correction can be wrong too, and the tag exists so a bad tip does not become the new default overnight. If you maintain a public wiki and want a row updated, a link to your page is welcome as a source string. It does not automatically outrank a Steam patch note.
There is no live chat and no promised reply window. A correction that names a patch can be applied the next time the data files are edited. A correction that contradicts a Steam post will not override that post. Messages about accounts, bans, or missing purchases are Steam's, even if they mention this guide in the subject line. The same is true of Workshop copyright disputes between mod authors. Point those at the studio or at Valve. This inbox, when it exists, is for the sentences on these pages. If you are writing on behalf of a wiki, a news site, or a video description, say so in the first line. A correction from a player who just opened the moisture farm tooltip is as welcome as one from a guide author. What matters is the patch and the number, not the size of the channel. Please do not send the same note to the studio's support address and expect this site to change. Those are different inboxes, and only one of them edits `src/data`.
Copyright and takedown
If you are the rights holder and a page quotes more of a Steam post than fair reporting needs, or if a future edit accidentally hotlinks a press image, write to the contact address with the URL and the change you want. The current build uses no store screenshots and no press art. Character names are used to describe systems the patches already name. This guide will remove a specific passage faster than it will argue about a fan's right to mention Lou.
What this page will not do
It will not recover a save, reset a rent payment, or explain a crash log. It will not review a mod you are about to publish, and it will not host a cheat table even if you attach one. It will not confirm a buyout price from a single screenshot of a difficulty this guide has not named officially. It will not add a Simplified Chinese mirror just because a message asked for one. Translation is a content project, not a setting. If the form is missing, the owner has not set NEXT_PUBLIC_CONTACT_EMAIL yet. That is a deployment step in the README, not a broken page. Until the address exists, the way to change a number is still the data file in the project. Players who cannot edit the file can wait for the inbox, or leave the confirmation on the studio's public channels where the next pass over the news feed can pick it up.
What a message contains
If the contact email is configured, the form is a mailto link. Your mail app sends the message. This website does not store a copy, because it has no database and no form backend. If the email is not configured, the page says so and nothing is sent. Do not include passwords, payment details, or a Steam guard code in a correction. A patch number and an item name are the whole request.
Frequently asked questions
Where do I report a game bug?
To tinyBuild at the support address on the Steam page, or in the developer Discord linked from their news posts. Not to this fan guide.
Will you reply?
Only if the site owner has set a contact email and chooses to reply. The page does not promise a response time.
Can I send a new recipe?
Yes. Include the machine, the inputs, the output, and the patch. It will be tagged with you as the source until a second confirmation exists.
Do you take guest posts?
No. Corrections to the data files are welcome. Sponsored articles are not what this guide is for.
Taken from the Steam store page, Steam news, or the publisher's launch announcement. The same claim appears in more than one independent community write-up, or a Steam achievement id matches those write-ups. Not an official patch note. Single community source, or sources disagree. Help us confirm before you rely on the number. Prices and unlock rates move after patches.
