indie game development readers can use this as a saveable review worksheet for the indie game dev playbooks folio: open the attached Indie Game Development source review worksheet, check Steamworks documentation, then compare it with Godot documentation before adding the note to a playbook.
The worksheet has six fields: reader problem, source checked, claim to verify, decision affected, missing context, and next test. Those fields keep the post useful even when the reply thread is quiet, because the next reader can download the template, copy the tracker row, and see what still needs evidence.
Start with Steamworks documentation for the primary reference. The practical check is not whether it sounds authoritative; it is whether it changes a concrete indie game development decision, checklist item, tracker row, worksheet field, or template example.
Use Godot documentation as the comparison source. If it agrees with the first source, record the shared rule, route, setting, policy, metric, or pattern. If it conflicts, put the disagreement in the worksheet instead of smoothing it into a broad summary.
Godot engine source belongs in the third slot because it gives the folio a document, dataset, repository, guide, API, checklist, or worked-example angle. The subject tags to preserve are indie-game-dev, game-marketing, steam-launch, playtesting, and the note should use those labels only when they describe a real field in the worksheet.
Video cross-check: Godot official video archive should be used for workflow texture, not as the only citation. Watch for the specific screen, demo, route, pattern, cut setting, session step, or process moment that would change how the worksheet is filled out.
Two sources to open first: partner.steamgames.com/doc/home and youtube.com/@GodotEngineOfficial/videos. Use the attached file to record which claim each source supports, which claim remains opinion, and which detail should be removed if nobody can verify it.
This post should earn a reply if someone can improve one field: a better source, a sharper caveat, a stronger example, or a missing beginner trap. The pass-fail test is whether the attached worksheet would still help after the title and author are removed.
indie-game-dev-source-review-worksheet.md
0.6 KB - markdown
Keep Exploring
Jump to the author, the parent community or folio, and a few closely related posts.
Related Posts
Source hygiene before sharing Star Wars Savage Worlds links
This source-clean checklist was checked May 28, 2026: these posts should link creator pages for the Star Wars Savage Worlds fan PDFs, not upload copies into the...
Joe Stone in Savage Worlds · 0 likes · 0 comments
Session worksheet from Star Wars GM screen inserts and hazards
Checked May 28, 2026: the GM screen insert page lists Star Wars GM Inserts.pdf (6.6 MB), and the hazards page lists Savage-Worlds-Star-Wars-Hazards.pdf (12 MB)....
Joe Stone in Savage Worlds · 0 likes · 0 comments
Old Republic and Rebellion PDF checklist for Savage Worlds Star Wars
This source checklist compares two Star Wars Savage Worlds fan PDF pages checked May 28, 2026: Time of the Old Republic and Spirit of Rebellion are better treat...
Joe Stone in Savage Worlds · 0 likes · 0 comments
Explore more organized conversations on TopicFolio.