Include enough context
Editorial template: product title and app ID; build if visible; current location or chapter heading; objective; actions already attempted; observed result; desired spoiler level. Omit passwords, account identifiers and unrelated desktop details. A cropped screenshot of the relevant scene is usually clearer than “it does not work.”
Separate three kinds of statement
Fact: directly observable or attributable to a named source. Theory: an interpretation that could have alternatives. Unverified: a claim without sufficient reproducible evidence. Our articles use sourced sections and explicit editorial advice; we do not promote theories to puzzle instructions.
What would unlock deeper guides
A reproducible full-game route with build information would support a chapter guide. An observed input and its result would support a puzzle entry. Multiple independently checked branches would be needed before asserting an ending count. This local preview has no submission backend; keep evidence locally for the next editorial update.
A completed-style request template
Use this structure, replacing every bracket with your own observation: “I am playing [full title / app ID], [build if visible]. At [chapter or location], the objective says [text]. I tried [one action], and [observed result]. I already checked [relevant clue or item]. I want [a hint / a full solution].” For a farm report, identify feed, staff entrance and gate separately. For a boat report, say which key is named. For the color puzzle, attach your current board rather than only a sequence you tried.
Sources & evidence
Public sources reviewed 2026-10-27. Publisher statements are not independent gameplay tests. Store information may change.