Configuring Meltan Spawns and Evolution in Pixelmon
The Meltan section contains the options Pixelmon uses for this part of the server. Control Meltan generation, Mystery Box behavior, smelting encounters, and Melmetal evolution requirements.
Pixelmon Meltan Settings
The settings below are listed in the same order as they appear in meltan.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 meltan.yml key for reference.
| Setting and Config Key | Default and Accepted Values | Description |
|---|---|---|
| Meltan Transform Chance meltan-transform-chance | Default: 0.75 Values: decimal number | Percentage chance for a Meltan to transform into Ditto on capture. 1 = 100% |
| Meltan Box Spawn Rate meltan-box-spawn-rate | Default: 300 Values: whole number | Chance for a Meltan to spawn with each opening. 1/X |
| Meltan Box Spawn Radius meltan-box-spawn-radius | Default: 15 Values: whole number | Maximum block distance away from the box that a Meltan could spawn. |
| Meltan Box Initial Scraps Count meltan-box-initial-scraps-count | Default: 4 Values: whole number | Amount of Netherite Scraps to initially open the Mystery Box. |
| Meltan Box Scraps Multiplier meltan-box-scraps-multiplier | Default: 1.8 Values: decimal number | Multiplier for the amount of scraps needed per box opening after the first. |
| Meltan Box Open Duration Millis meltan-box-open-duration-millis | Default: 100000 Values: whole number | Amount of time, in milliseconds, that it takes for the Mystery Box to open. |
| Meltan Box Cooldown Duration Millis meltan-box-cooldown-duration-millis | Default: 3000000 Values: whole number | Amount of time, in milliseconds, that it takes before the Mystery Box can be opened again. |
Important Meltan 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 meltan.yml.
Settings That Work Together
Several meltan 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
Meltan 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.