Project P.I.T.T. Wiki uses source labels, official links, reproducible checks, community context, and update notes so guide content, player reports, access information, and placeholders do not get mixed together.
Updated
August 25, 2026
Core rule
Official sources are used for official claims. Community and editorial sources can help discover useful topics, but they stay labeled until they can be checked.
These are the main public sources used for Project P.I.T.T. Wiki. A source can be authoritative for one topic and weak for another, so each link has a use case and a limit.
Use for: Release access, current store description, supported systems, achievements count, languages, price checks, and official download path.
Limit: Store text does not prove hidden-route solutions, 200kg item weights, or every achievement trigger.
Use for: Publisher-controlled overview, official positioning, creator/publisher context, and high-level game description.
Limit: It is not a complete walkthrough or a live patch database.
Use for: Old demo history, developer context, early controls, comments, and the fact that the itch.io demo is outdated.
Limit: Old demo behavior must not override the current Steam demo or full game.
Use for: Public player questions, screenshots, community guides, update discussions, common blockers, and bug reports.
Limit: Community posts are discovery leads, not official confirmation by themselves.
Use for: Walkthrough leads, achievement cleanup routes, secret-route hints, and repeated player-tested patterns.
Limit: Guides need cross-checking against the current build before exact steps become settled wiki advice.
Use for: Official community path, update discussion, bug reporting direction, feedback channels, and support routing.
Limit: Discord chatter should be treated as community context unless it comes from a developer or controlled announcement.
Tier 1
Official Steam, itch.io, developer, and publisher pages
Tier 2
Official Discord, patch notes, store posts, and developer announcements
Tier 3
Maintained wiki or guide pages that cite observable in-game behavior
Tier 4
Steam Community, Reddit, YouTube, and player reports as discovery leads only
Tier 5
Unverified rumors, copied downloads, cracks, torrents, and cheat pages are not used as positive sources
Use these for official release, access, platform, achievement count, language, feature, and safe download claims. Do not use them to invent gameplay solutions they do not state.
Use these for version-sensitive changes such as demo availability, panel behavior, Phase 3 fixes, lost-item handling, and platform notes. Keep the date visible when the answer may change.
Use direct testing for mechanics, item behavior, stage fixes, and route checks. A claim is stronger when the same result can be reproduced in the current build.
Use credible guides for route leads and problem framing. Cross-check spoiler-heavy claims, achievements, 200kg, 0%, fuses, endings, and exact item behavior before publishing them as settled.
Use Steam discussions, Reddit, YouTube comments, Discord posts, and player reports to find real search language and blockers. Label them clearly unless stronger evidence supports the claim.
Use local keyword research and notes to plan page structure and search coverage. Internal documents are not public proof; public-facing facts still need official, reproducible, or clearly cited support.
Guide pages can explain search intent and route users through topics, but exact gameplay steps should stay conservative until checked against official, reproducible, or clearly cross-checked evidence.
Remote, Sticky Tools, fuses, 200kg, Bumpers, Fans, Magnets, and weight mechanics need official, in-game, or reproducible evidence before exact behavior is marked confirmed.
Bumper, Panels, debris, Piñata, rubble, 0%, and hidden-route pages should separate symptoms, likely related mechanics, confirmed fixes, and version-sensitive old advice.
Demo, price, release date, download, Steam, itch.io, and discount information must come from official or safe sources only. Price and discount claims need a last-checked mindset.
Android, APK, Discord, Steam Deck, macOS, Linux, PlayStation, and other platform claims should not be written as confirmed until official source evidence exists.
Treat these as unstable. Check the live store before writing a specific number or discount.
Separate old demo history from the current Steam demo and full game. Do not let old demo limits define current advice.
Keep 200kg, 0%, fuses, Secret Ending, panels, debris, and lost-object claims labeled when they depend on version or reproducible testing.
Check official sources first for Android, APK, Steam Deck, macOS, Linux, Discord, and support routes. Use third-party reports as supporting context.
Project P.I.T.T. Wiki should not build positive landing pages for cracks, torrents, SteamUnlocked, Skidrow, IGG, illegal free download mirrors, or cheat-engine acquisition paths. These terms may appear only as warnings or safety context. Access pages should send readers to official and safe sources only, never to mirror downloads, bypass tools, or piracy calls to action.
