Skip to content

First-mod checklist

This checklist is deliberately small. It does not try to teach every WorldBox system before your first success.

FIRST MOD

Beginner journey

Progress is stored only in your browser. This is not a test or mandatory order — just a short, low-risk route.

0 / 6Progress
NML is visible in the log

First prove that NeoModLoader is actually running in this session.

Check Player.log →
I know what each piece is

WorldBox, NML, mod.json, Main.cs and Player.log no longer look like five random terms.

Open the mental model →
I created a minimal skeleton

Generate only mod.json and Main.cs. No UI, Harmony or giant architecture yet.

Open generator →
I found my own marker

Launch the game and find the exact line emitted by your mod in Player.log.

Verify first launch →
If it breaks, I know the first check

Do not rewrite everything: start from compile/load/runtime evidence.

Open first checks →
I added one feature

Pick one recipe and expand only after that one path works.

Choose a recipe →

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.