-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
-
Does the model exist? Run
/bettermodel spawn <model id>. If that shows nothing, the model isn't installed in BetterModel. BetterMob can't create it. Content packs usually ship only YAML, the model files are separate. -
Is the ID the same? The ID in
model{mid=...}(orModel:) must match the BetterModel model exactly. -
Read the console right after spawning.
-
BetterModel model '<id>' does not exist.- the model isn't registered. -
BetterModel is not active while spawning '<id>' - no model attached.- BetterModel isn't enabled. -
BetterModel '<id>' could not be attached: ...- the message tells you why.
-
-
Using ModelEngine? Use
modelengine{mid=...}, notmodel{...}. The two plugins have separate model lists.
A mob without Type defaults to ZOMBIE. This usually means the file has an extra level of
indentation or the Type: line is missing. Check that Type: is at the root of the file
(or directly under the mob's ID in a multi-mob file).
BetterMob doesn't implement that mechanic, the line is skipped. See Skills for what exists. The rest of the skill still runs.
The condition is unknown and counts as true. A skill that depends on it will run more often than it should.
Two files define the same ID. The first one loaded wins, the other is ignored. Rename one or
disable a pack in config.yml. The same applies to skills and items.
- Run
/bettermob packsto see if the pack is enabled. - Check the console for
could not be parsedlines. They name the skill and the line. - Sub-folders and
Mobs/mobscasing don't matter, but a file must end in.yml.
Those rely on a remove{delay=...} @self ~onSpawn line. Make sure the line exists and that
you reloaded after adding it. Mobs that were already spawned keep their old definition.
The plugin isn't enabled. Check /plugins and the console at startup for an error from
[BetterMob]. Also make sure you typed only the command into chat.
Turn on debug with /bettermob debug verbose (and /bettermob debug filter <mob id>), trigger the skill again and read why it stopped. See Commands.
The message language comes from Language: in config.yml (en by default). If you see German lines, the setting is de or a custom file is selected, see Installation. The texts quoted on this page are the English ones.
Open an issue at https://github.com/HyperGaming99/bettermob/issues with your Paper version, the BetterMob version, the mob file and the console output.