Troubleshooting

Troubleshooting

Home / Troubleshooting

BetaMoon fails during startup

Check the launcher console for the first error. Confirm Minecraft Beta 1.7.3, Java 8, ModLoader, Forge and the packaged BetaMoon JAR are installed as described in Installation. Apply ModLoader before Forge, and enable BetaMoon. The packaged BetaMoon JAR includes LuaJ 3.0.1.

An agent warning appears

BetaMoon's warning provides the Java-agent argument for the installed JAR. Add it to the instance's JVM arguments and restart Minecraft. If the JAR was moved or renamed, update the path. Consult the console for Java-agent initialization errors.

A script is missing from the list

Place a single .lua file directly in the active instance's betamoon/scripts folder, or install a packaged mod with betamoon.mod.json at its directory or ZIP root. Verify that it has a unique name and a modInit() function. The Scripts screen and launcher console report manifest, metadata, syntax, and dependency errors.

Warnings do not appear on startup or reload

Startup and reload notifications show errors by default. Warnings remain available in the Scripts screen and launcher log. To include warnings in the notifications, set notifications.showScriptWarningsOnLoad=true in .minecraft/config/betamoon.cfg and restart Minecraft.

Registration reports an occupied ID

Choose an available numeric ID and update references to that content. Check other installed mods and examples. Preserve IDs already used by saved worlds; see compatibility.

A module import fails

Export the table during the provider's initialization, import it in the consumer's modInit(), and add the provider's script name to the consumer's dependencies. The import uses the exported module name. See Modules.

A texture fails to load

Resolve the PNG path from the instance's betamoon/scripts folder. For a registered texture without path, use <namespace>/textures/<key-path>.png; otherwise use the supplied path. Copy required asset directories with the script and check spelling and capitalization. See Assets and Textures.

Changes require a restart

Check the restart indicator. Tile structures and other retained definitions require a fresh Minecraft process to apply changed schemas. See Hot reload.

A callback stops running

Inspect the first callback error. BetaMoon disables failed callback registrations. Fix the arguments, field values or return outcome, then reload the owning script, or restart for retained structural scripts. The block, item and tick references describe their respective contexts.

A recipe match cannot apply

Read the second result from match:canApply() or match:apply(). Check input changes, output capacity, remainder capacity and fresh context for conditioned recipes. See failure reasons.