Party and access requirements¶
Requirements are evaluated before normal battles and rechecked after an introduction. The administrator test command bypasses progression and party-rule checks, so use a regular challenge to validate access rules.
Access gates¶
| Field | Behavior |
|---|---|
enabled |
Master switch for normal battle challenges. |
permission |
Permission the player must have; blank means no additional permission gate. |
required_player_tags |
Every listed Minecraft command tag must be present. |
forbidden_player_tags |
Any listed tag blocks the challenge. |
prerequisite_trainers |
The player must have a recorded victory against every listed trainer ID. |
Example settings fragment:
{
"permission": "myserver.gym.rock",
"required_player_tags": ["tutorial_complete"],
"forbidden_player_tags": ["gym_suspended"],
"prerequisite_trainers": ["tutorial/rival"]
}
Minecraft tags can be managed with /tag Alex add tutorial_complete and /tag Alex remove gym_suspended. Permission nodes are managed through the server's permissions provider. Menu visibility is configured separately through menu_permission and category permissions; a hidden menu entry is not a replacement for a battle-access rule.
Party size and levels¶
minimum_party_size defaults to 1 and maximum_party_size to 6. The configured format also imposes a minimum party size: two for doubles and three for triples. At battle start, enough Pokémon must additionally be able to fight. Fainted entries still count toward the party's total size and its level restrictions.
minimum_party_level defaults to 1 and maximum_party_level to 100. Each Pokémon in the party must be within that range; the check does not use an average. heal_player_before can restore the party after the normal rule checks, but it does not waive size, species, level, move, or other restrictions.
Required, forbidden, and allowed lists¶
Each family supports these suffixes:
| Suffix | Values |
|---|---|
_pokemon |
Pokémon descriptions with a species and optional form. This gate matches species/form, not every descriptive field. |
_type |
Arrays of exact type combinations; see below. |
_label |
Labels supplied by Pokémon form data. These are not Minecraft player tags. |
_held_item |
Held-item IDs. |
_ability |
Ability IDs/names accepted by the resolver. |
_move |
Move IDs/names accepted by the resolver. |
Required lists require every listed entry to be represented somewhere in the party. Different Pokémon may satisfy different entries.
Forbidden lists reject the party if any listed entry is present.
Allowed lists, when nonempty, restrict the encountered values to those lists. For species and type combinations, every Pokémon must be allowed. For moves, every known move must be allowed; listing one move does not merely require each Pokémon to know that move. Empty allowed lists add no restriction. A Pokémon with no held item contributes no held-item value.
Example:
{
"minimum_party_size": 1,
"maximum_party_size": 3,
"maximum_party_level": 30,
"required_pokemon": [{"species": "pikachu"}],
"forbidden_pokemon": [{"species": "mewtwo"}],
"required_move": ["protect"],
"forbidden_held_item": ["cobblemon:master_ball"]
}
Use /gnpc validate to check names against installed content. An item ID used in a rule is still subject to the installed item registry.
Type combinations and wildcards¶
Types are matched as sets, so order does not matter. Each inner list describes one combination.
| Rule entry | Matches |
|---|---|
["fire"] |
Pure Fire Pokémon only. |
["fire", "flying"] |
Exactly Fire/Flying, in either order. |
["fire", "*"] |
Pure Fire or any dual type containing Fire. |
["fire", "+"] |
Dual types containing Fire, but not pure Fire. |
["*"] |
Any single-type Pokémon. |
["*", "*"] |
Any dual-type combination. |
To allow only Pokémon with Water anywhere in their typing:
To require both a pure Electric Pokémon and a Fire/Flying Pokémon somewhere in the party:
These fragments belong in an existing trainer preset. They do not define a complete trainer on their own.