/edit — Modify an objective
The /edit command modifies an objective already tracked on your server. Before it existed, correcting a mistake meant running /remove then /add again.
Parameters
indexautocompleteRequiredThe objective to edit — pick it from the suggestionstypeautocompleteNew objective typerarityautocompleteRarity of the objective — leave empty for DragonmapautocompleteNew Black Zone map nametimestringNew time remaining until spawnSyntax
/edit index:<index> [type:<type>] [rarity:<rarity>] [map:<map>] [time:<time>]Parameters
Only index is required. Every other parameter is optional: supply just the ones you want to change.
| Parameter | Type | Required | Description |
|---|---|---|---|
index | Autocomplete | Yes | The objective to edit. Pick it from the suggestions rather than typing it. |
type | Autocomplete | No | New objective type — one of the 8 values (see objective types) |
rarity | Autocomplete | No | New tier for nodes (4.4–8.4), colour for cores and vortexes (Green, Blue, Purple, Gold), or size for portals (Small, Medium, Large). A Dragon takes none. |
map | Autocomplete | No | New Black Zone map name (see map list) |
time | Text | No | New time remaining until spawn |
Accepted time formats
The time parameter accepts several notations. A bare number is always minutes.
| Input | Interpretation |
|---|---|
1:30 | 1 hour 30 minutes |
02:30 | 2 hours 30 minutes |
1h30 | 1 hour 30 minutes |
1h30m | 1 hour 30 minutes |
1h 30 | 1 hour 30 minutes |
1h 30m | 1 hour 30 minutes |
1h | 1 hour |
90 | 90 minutes |
45m | 45 minutes |
90m | 90 minutes |
The value is a delay from now, never a clock time. It is recounted from the moment you submit the edit, not from when the objective was first reported.
The delay is capped per type, as with /add: 30, 60 or 180 minutes for a Small, Medium or Large Ancient Lands Portal, and 1440 minutes (24 hours) for every other type. These caps are a typo guard rather than a game rule (see time limits). When a value is both malformed and out of range, the format error is reported first.
Selecting the objective
Start typing in the index field and the bot lists your server’s active objectives:
#1 — Vortex Gold Thetford (14:20 UTC)
#2 — Ore node 8.4 Avalanche Ravine (16:05 UTC)
#3 — Core Purple Martlock (18:45 UTC)The list shows up to 25 objectives and covers active ones only; expired objectives are gone and cannot be edited.
Typing the number by hand still works, but without that safeguard.
Permissions
You can edit an objective if any of these is true:
- You have the Administrator permission
- You have the Manage Messages permission
- You reported the objective yourself
These are alternatives, not cumulative requirements. The same rule governs /remove.
Behavior
Partial updates
Only the parameters you supply are changed; everything else stays as it was. To change just the rarity, supply only rarity.
If you supply no field at all, nothing is modified and the bot replies:
No changes were supplied, nothing to update.Confirmation
The confirmation is ephemeral (only you see it) and lists each field that actually changed:
Your objective has been successfully updated!
rarity: Purple → Gold
map: Thetford → MartlockA field you supplied with its existing value is not listed, since nothing changed.
Validation
The bot refuses an edit that would produce an invalid objective:
| Situation | Response |
|---|---|
| Unknown type, rarity or map | One or multiple value(s) are incorrect, please try again. |
| Rarity invalid for the resulting type | This rarity is not valid for the selected type |
| Time in an unrecognised format | Invalid time format. Accepted formats: 1:30, 02:30, 1h30, 1h30m, 1h 30, 1h 30m, 1h, 90, 45m, 90m |
| Time beyond the accepted range | The provided time is out of the accepted range |
| The edit would duplicate an existing objective | It appears that the objective you are trying to add already exists |
The type and rarity check applies to the resulting combination: the fields you supply merged with the stored ones. Changing only the type on a Core Purple objective is rejected if the new type does not accept Purple. The five rarity-validation outcomes of /add apply to that resulting combination, Dragons included.
Three cases are specific to mutations between families:
- Editing a stored
Dragoninto a rarity-bearing type without supplyingrarityis rejected: the rarity is missing. A Dragon has no stored rarity to reuse, so you must supply one along with the new type. - Editing a stored rarity-bearing type into a
Dragonwithout supplyingrarityis accepted. The old rarity is discarded, since a Dragon takes none. - Resizing a portal to a smaller size without supplying
timeis rejected as out of range when the remaining time (whole minutes, seconds truncated) exceeds the new size’s cap. Supply atimewithin the new cap in the same edit.
Maintenance detection
Editing time recalculates whether the new spawn time crosses the daily 10:00 UTC maintenance window, exactly as /add does.
Message refresh
After a successful edit, the bot deletes its tracking message in the channel and posts an updated one, so the shared list always reflects current data.
Cooldown
This command has a 2-second cooldown per user.