Managing Dimensions on a Pixelmon Server

Support / Games / Minecraft / Mods / Pixelmon / Managing Dimensions on a Pixelmon Server
Create a Minecraft: Java Edition Server today!
Start Free Trial

The Dimension section contains the options Pixelmon uses for this part of the server. Enable or disable Pixelmon dimensions and control dimension-related access and world behavior.

Pixelmon Dimension Settings

The settings below are listed in the same order as they appear in dimensions.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 dimensions.yml key for reference.

Setting and Config Key Default and Accepted Values Description
Ultra Space ultra-space Default: true Values: true or false Whether the Ultra Space Dimension is activated or not.
Wild Berry Trees wild-berry-trees Default: false Values: true or false Where the Berry Trees are capable of spawning in the wild.
Tumblestone Spawn Chance tumblestone-spawn-chance Default: 0.009999999776482582 Values: decimal number The chance that a tumblestone block will spawn in the world.
Tumblestone Growth Chance tumblestone-growth-chance Default: 0.10000000149011612 Values: decimal number The chance that a tumblestone block will grow.
Tumblestone Restore Chance tumblestone-restore-chance Default: 0.25 Values: decimal number The chance that a tumblestone block will restore itself.
Common Fossils common-fossils Default: [helix, dome, old_amber, root, claw] Values: list List of fossils considered 'common' for regular fossil blocks. Valid values: helix, dome, old_amber, root, claw, skull, armor, cover, plume, jaw, sail, bird, dino, drake, fish
Rare Fossils rare-fossils Default: [skull, armor, cover, plume, jaw, sail, bird, dino, drake, fish] Values: list List of fossils considered 'rare' for deepslate fossil blocks. Valid values: Same as commonFossils

Important Dimension 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 dimensions.yml.

Settings That Work Together

Several dimension 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

Dimension 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.