#game-modding

game modding source worksheet file: use this as a comparison ledger before another broad note goes into the game modding playbooks folio. The attached Game Modding source review worksheet gives the post a document to work from: check Nexus Mods creator articles, compare it with SMAPI, then write the decision that changes.

The ledger fields are reader problem, source checked, claim to verify, decision affected, missing context, and next test. They keep the post useful after the first read because the next person can download the file, copy the tracker row, and see where the evidence is still thin.

Nexus Mods creator articles is the primary reference. It should settle one concrete game modding decision, checklist item, tracker row, worksheet field, or template example, not just make the topic sound more complete.

SMAPI is the comparison source. If it agrees with the primary reference, keep the shared rule, route, setting, policy, metric, or pattern. If it conflicts, put the disagreement in the worksheet instead of sanding it down.

Fabric example mod adds the artifact angle: document, dataset, repository, guide, API, checklist, or worked example. File the note under game-modding, mod-tools, asset-pipelines, ugc-guides only where those labels match a real worksheet field.

Video cross-check: Minecraft creator learning videos belongs here for workflow texture. Look for the exact screen, demo, route, process step, cut setting, or session moment that changes how the ledger is filled out.

Two sources to open first: help.nexusmods.com/category/21-modding-guides and youtube.com/@Minecraft/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.

The post earns a reply when someone improves one field: a better source, sharper caveat, stronger example, or missing beginner trap. The pass-fail test is whether the worksheet still helps after the title and author are removed.