Managing Pokémon, Mobs, and Entity Behavior in Pixelmon
The Entity Behavior section contains the options Pixelmon uses for this part of the server. Configure vanilla mob behavior, wild Pokémon aggression, battle initiation, and entity interaction rules.
Pixelmon Entity Behavior Settings
The settings below are listed in the same order as they appear in entity.yml. The table preserves each default and identifies the accepted value type. The Setting column shows a reader-friendly name first, followed by the matching entity.yml key for reference.
| Setting and Config Key | Default and Accepted Values | Description |
|---|---|---|
| Allow Vanilla Mobs allow-vanilla-mobs | Default: false Values: true or false | Whether or not regular Minecraft mobs like cows and zombies can spawn naturally. DANGER - can kill you while battling. Monster spawners containing zombies, skeletons, or spiders will be converted into monsters spawners that spawn pigs if this setting is disabled. Other monster spawners (including ones that spawn hostile mobs like Blazes, cave spiders, or silverfish) will not be affected, nor will spawn eggs. The Ender dragon also spawns naturally regardless of this setting. Warning: This setting when not refined with a datapack will use the default spawning logic instead of the implemented Betterspawner logic, possibly causing mob spam. In order to refine the replacement logic, a datapack must be used. |
| Allow Capture Outside Battle Dimensions allow-capture-outside-battle-dimensions | Default: [minecraft:overworld, minecraft:the_nether, minecraft:the_end, pixelmon:ultra_space] Values: list | Dimensions that allow players to throw Poké Balls and capture Pokémon outside of battle. |
| Engage Player By Poke Ball engage-player-by-poke-ball | Default: true Values: true or false | If enabled, battles between players can be initiated by a player throwing a Pokémon's Poké Ball at another player directly (rather than at the other player's Pokémon). |
| Enable Wild Aggression enable-wild-aggression | Default: true Values: true or false | Whether or not aggressive wild Pokémon initiate battles against players. |
| Can Pokémon Be Hit can-pokemon-be-hit | Default: false Values: true or false | Whether or not out-of-battle wild Pokémon can be hurt by minecraft attacks such as punching or swords. |
| Disabled Non Player Movement disabled-non-player-movement | Default: false Values: true or false | Determines if non player owned pokemon's movement is disabled or not. |
Important Entity Behavior Setting Notes
Defaults and Value Types
Boolean toggles, numeric rates, timers, lists, and mappings use different value formats. Preserve the value type shown in the table and keep collection syntax intact when changing entity.yml.
Settings That Work Together
Several entity behavior options can affect the same outcome. Review related rates, limits, timers, and lists together before deciding that one value is responsible for a result.
Testing Changes
Change one related group of settings at a time so its effect is easy to measure.
Test the result under the conditions affected by the setting, including relevant dimensions, player states, or encounter types.
Keep a copy of the previous values so unexpected balance or performance changes can be reversed quickly.
Final Thoughts
Entity Behavior settings are easier to balance when changes are deliberate and documented. Start with the defaults, adjust only what the server needs, and verify the result before moving on to the next group.
Need Help?
If you have questions or run into any issues, our support team is here to help! Reach out using the support widget on our website or visit our support center for further assistance.