How Pixelmon Curry Encounters Work
The Curry Encounter section contains the options Pixelmon uses for this part of the server. Configure Curry encounter chances, Pokémon pools, level ranges, and related camping behavior.
Pixelmon Curry Encounter Settings
The settings below are listed in the same order as they appear in curry.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 curry.yml key for reference.
| Setting and Config Key | Default and Accepted Values | Description |
|---|---|---|
| Curry Encounter Rates curry-encounter-rates | Default: {CHARIZARD: 4.0; KOFFING: 100.0; WOBBUFFET: 20.0; MILCERY: 7.0; COPPERAJAH: 5.0} Values: mapping of keys and values | The chance for a pokemon to join your team after cooking curry of a particular class. 1/X chance. |
| Curry Rating Cutoffs curry-rating-cutoffs | Default: [40, 65, 100, 135] Values: list | The cutoffs for ratings based on the minigame. The theoretical max score is 173, though in practice 150 is the highest most players can get. |
| Curry Battle curry-battle | Default: false Values: true or false | Determines whether a pokemon spawned by cooking curry will start a battle or just join the party. |
| Curry Nature Sync curry-nature-sync | Default: true Values: true or false | Determines whether a pokemon spawned by cooking curry will have its nature match the flavor. |
| Curry Ball Ordered Types curry-ball-ordered-types | Default: [poke_ball, great_ball, ultra_ball] Values: list | The pokeball types that curry spawns can use to join the party. This list is ordered, meaning that pokemon will prefer types listed first. |
| IV Boost iv-boost | Default: true Values: true or false | Whether high class curry provides an IV boost to curry spawns. |
Important Curry Encounter 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 curry.yml.
Settings That Work Together
Several curry encounter 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
Curry Encounter 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.