Rematches and one-battle challenges¶
GreatNPC tracks battle progression by player UUID and trainer ID. Two NPC entities that resolve to the same trainer preset can therefore share the player's progression. Giving an entity a different UUID does not by itself create a separate progression track.
Configure these settings in the NPC editor's Rematches section, or in the trainer preset JSON.
| Field | Default | Behavior |
|---|---|---|
one_battle_per_player |
false |
On/Off. When enabled, the player receives one successful battle start against this trainer. |
is_rematch_allowed |
true |
When false, a player with a recorded victory cannot battle again. A loss alone does not trigger this rule. |
cooldown_in_seconds |
0 |
Delay after a player victory. 0 disables this delay. |
daily_reset |
"" |
Optional daily availability reset, such as "06:00"; takes precedence over duration cooldown when valid. |
max_victories |
0 |
Maximum recorded victories per player; 0 means unlimited. |
When attempts and cooldowns count¶
The one-battle attempt is recorded only after Cobblemon reports a successful battle start. Losing that battle still uses the attempt. A rejected request, a failed start, or an introduction that never becomes a battle does not consume it.
The cooldown timestamp is updated only when the player wins. Losing does not start a new cooldown and does not move the last-victory timestamp forward. Victory count, defeat count, the used battle attempt, and the cooldown timestamp are separate history fields.
Checks apply together. Turning off the one-battle rule does not clear an existing cooldown, victory cap, or no-rematch rule.
Examples¶
Repeatable trainer with a 30-minute cooldown¶
{
"one_battle_per_player": false,
"is_rematch_allowed": true,
"cooldown_in_seconds": 1800,
"daily_reset": "",
"max_victories": 0
}
This is a settings fragment to merge into an existing preset with a valid team reference. The Rematches editor accepts durations such as 30s, 15min, 1h, and 2d; the preset field stores seconds.
One attempt, regardless of result¶
Repeat until the player wins once¶
Available again after the next daily reset¶
{
"one_battle_per_player": false,
"is_rematch_allowed": true,
"daily_reset": "06:00",
"max_victories": 0
}
Daily resets use the server's system time zone. They control availability relative to the last victory; they do not erase victory counters or re-enable a used one-battle attempt. A server restart does not normally make the trainer available early, because the persisted timestamp is used.
Reset a player's attempt¶
Replace the example UUID with the actual NPC UUID shown by /gnpc info while looking at it. The command resolves the NPC to its trainer ID and re-enables that player's one-battle attempt. It accepts one player profile, including an offline profile that the server can resolve. Load the NPC's chunk if its UUID cannot be found through the current location index.
This command leaves victories, defeats, and the cooldown timestamp intact. Other limits can still block the next challenge. It requires greatnpc.reset.
For a broader reset:
reset removes matching battle-history records, including counters, cooldown, and attempt state. Its player argument is an online player selector/name. Folder matching is based on trainer IDs.
/gnpc resetfirst Alex tutorial/brock sets the victory counter back to zero. It is intended to re-enable first-victory behavior, and does not clear the timestamp or used-attempt state. Use the appropriate reset for the desired outcome.
The current release keeps the NPC present after battle. A victory-triggered disappearance, smoke effect, and respawn-countdown hologram are not implemented features.