Skip to content

Commit 6b91d74

Browse files
authored
docs: fix
1 parent 36bdbbe commit 6b91d74

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

docs/upgrades.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -20,17 +20,17 @@ You can define multiple upgrades here, as the section accepts a list of entities
2020

2121
For this type of upgrade, the `type` must be set to `spawner`.
2222

23-
* **`add-levels`**:
23+
* **`add-levels`**
2424
The number of levels to add when the upgrade is purchased once.
2525
This value can be fractional, e.g. `0.2` means a 20% chance for an extra resource per spawn.
2626
On the fifth purchase, this would guarantee one additional resource per spawn.
2727
By default, spawners start at level `1`, though this can be customized for individual spawners.
2828
See [Arena Editing Commands](commands.md#arena-editing) (`/bw admin <arena> spawner add <type> [holo enabled] [start level] [name] [team]`).
29-
* **`max-level`** (optional):
29+
* **`max-level`** (optional)
3030
The maximum level a spawner can reach through upgrades. Once reached, the upgrade becomes unavailable.
31-
* **`shop-name`** (optional):
31+
* **`shop-name`** (optional)
3232
The name displayed in chat when the upgrade is purchased. Defaults to `UPGRADE`.
33-
* **`notify-team`** (optional):
33+
* **`notify-team`** (optional)
3434
If `true`, all team members will be notified when the upgrade is purchased.
3535

3636

@@ -39,17 +39,17 @@ For this type of upgrade, the `type` must be set to `spawner`.
3939
There are three ways to specify which spawners the upgrade affects:
4040

4141
1. **Using named spawners**
42-
* Assign a name when creating the spawner.
43-
* Use the `spawner-name` field to target it.
44-
* If multiple spawners share the same name, they will all be upgraded.
42+
* Assign a name when creating the spawner.
43+
* Use the `spawner-name` field to target it.
44+
* If multiple spawners share the same name, they will all be upgraded.
4545
2. **Using type**
46-
* When creating a spawner, set its `team`.
47-
* Use `spawner-type` to define which spawner type to upgrade.
48-
* All matching spawners of that type belonging to the team purchasing the upgrade will be upgraded.
46+
* When creating a spawner, set its `team`.
47+
* Use `spawner-type` to define which spawner type to upgrade.
48+
* All matching spawners of that type belonging to the team purchasing the upgrade will be upgraded.
4949
3. **Using all linked spawners**
50-
* Link the spawners as in the previous mode.
51-
* Set `team-upgrade` to `true`.
52-
* All team-linked spawners will be upgraded, regardless of name or type.
50+
* Link the spawners as in the previous mode.
51+
* Set `team-upgrade` to `true`.
52+
* All team-linked spawners will be upgraded, regardless of name or type.
5353

5454
### Example
5555

0 commit comments

Comments
 (0)