First prove that NeoModLoader is actually running in this session.
Check Player.log →First-mod checklist
First-mod checklist
Section titled “First-mod checklist”This checklist is deliberately small. It does not try to teach every WorldBox system before your first success.
Beginner journey
Progress is stored only in your browser. This is not a test or mandatory order — just a short, low-risk route.
WorldBox, NML, mod.json, Main.cs and Player.log no longer look like five random terms.
Open the mental model →Generate only mod.json and Main.cs. No UI, Harmony or giant architecture yet.
Open generator →Launch the game and find the exact line emitted by your mod in Player.log.
Verify first launch →Do not rewrite everything: start from compile/load/runtime evidence.
Open first checks →Pick one recipe and expand only after that one path works.
Choose a recipe →What this checklist does not prove
Section titled “What this checklist does not prove”Completing it means your current skeleton and one chosen feature worked in your current environment. It does not make every API call version-independent, and it does not replace the evidence boundary on each recipe/reference page.
When a later task becomes version-sensitive, use the Compatibility Matrix.