Bad Mobs Mod FAQ

Open the badmobs-common.toml file in your config folder with a text editor, find the entry for the mob you want to block, and set allowNormalSpawning to false. Save the file and restart the game for the change to take effect.

It's in the config folder inside your Minecraft directory, named badmobs-common.toml. If you don't see it, launch the game once with the mod installed so it generates.

Yes, config changes are read at startup, so you need to restart Minecraft for them to apply. Some setups may reload on world load, but restarting is the reliable option.

Find that mob's entry in badmobs-common.toml, which uses the mod's namespace and mob name as the section header, then set its spawning options to false. If the entry isn't there yet, it gets added once the mod's mob has loaded at least once.

When set to true, it aggressively removes the entity from the world, bypassing all other spawning options for that mob. This is the strongest way to get rid of a mob, including ones already present.

Locate the minecraft:creeper section in badmobs-common.toml and set allowNormalSpawning to false. If you also want to stop spawn eggs and spawners from creating them, set those options to false too.

Yes, each mob has separate options for normal spawning, spawners, and spawn eggs. Set only the one you want to block to false and leave the others as they are.

Find the mob's section in badmobs-common.toml and set the option you changed back to true. Restart the game and the mob will spawn normally again.

Yes, it's designed to handle mobs from any mod, not just vanilla ones. Each modded mob gets its own section in the config once it's been registered.

No, it's a lightweight mod that only checks spawning rules, so it has minimal impact on performance. Blocking mobs can actually improve performance by reducing entity counts.

Bad Mobs lets you stop specific mobs from spawning in your world by editing a config file, and it works on vanilla mobs as well as mobs added by other mods. You can block normal spawns, spawner spawns, and spawn egg spawns separately, or remove a mob from the world entirely.

Open the badmobs-common.toml file in your config folder with a text editor, find the section for the mob you want to control, and change its spawning options to false. Save the file and reload or restart the game for the changes to apply.

Launch the game once with the mod installed so it generates the config file, then close the game and open badmobs-common.toml. Each mob has its own section with options for normal spawning, spawners, spawn eggs, and aggressive removal.

Every mob gets a section named after its ID, like minecraft:cow, with four true/false options: allowNormalSpawning, allowSpawners, allowSpawnEggs, and removeAggressively. Set the ones you want to block to false and leave the rest as they are.

AllowNormalSpawning only stops the mob from spawning naturally, but it can still appear from spawners, spawn eggs, or commands. removeAggressively bypasses all other options and actively removes the mob from the world, so use it when you want it gone completely.

Find the minecraft:creeper section in badmobs-common.toml and set allowNormalSpawning to false to stop them spawning naturally. If you also want to block spawner and spawn egg creepers, set those options to false too, or use removeAggressively to wipe them out entirely.

On Aternos, open your server's file manager, go into the config folder, and edit badmobs-common.toml directly in the built-in editor. Save the file and restart the server so the new settings take effect.

Yes, Bad Mobs is designed to handle mobs added by other mods as well as vanilla ones. You just need the correct mob ID for that mod's entity, which appears as its own section in the config once the mod is loaded.

Mob IDs follow the namespace:name format, like minecraft:zombie or modid:mobname, and each loaded mob gets its own section in badmobs-common.toml. If a mob's section isn't there yet, load the game once with that mod installed so the config generates it.

Bad Mobs is a lightweight config-based mod, so it has minimal performance impact and works fine on both singleplayer and servers. On a server, the config is server-side, so players don't need the mod installed on their clients for it to work.