Skip to content

Note that the GeigerCounters collection messages share one line #259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryanbarlow97 merged 2 commits into from
Oct 15, 2026
Merged

Note that the GeigerCounters collection messages share one line #259

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
72f8ae1
Note that the collection messages share one line
ryanbarlow97 Oct 15, 2026
63f5218
Show the shorter collection text
ryanbarlow97 Oct 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions projects/GeigerCounters/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,9 +287,9 @@ All chat text lives in a separate **`messages.yml`**, split into what players se
```yaml
# PLAYER - seen by anyone hunting a source
player:
found-source: "&#AA00FFYou have found the source of Arcane Radiation!"
found-source: "&#AA00FFYou found the arcane source!"
signal-bar: "&#AA00FFArcane signal"
dead-geiger: "&7Your Arcane Trace Detector has run out of fuel."
dead-geiger: "&7Your detector is spent."
limit-reached: "&cYou have already collected %max% sources in %window%. Try again in %time%."

# ADMIN - only ever seen by whoever runs /geiger
Expand All @@ -301,6 +301,8 @@ admin:
# ... 12 more, each documenting its own placeholders
```

On a collection, `found-source` and `dead-geiger` are sent as one line with a space between them, each keeping its own colours. A blank one is left out.

Console log lines stay hardcoded in English, so logs and bug reports remain readable whatever this file is translated to.

Upgrading? Messages are migrated automatically — out of `config.yml` and into the `player:`/`admin:` split, customisations preserved. `config-version` in `config.yml` tracks which migrations have run. Version 6 adds the source distances and the `bar` section, and lowers `detection.max-detection-distance` to `source.reroll-distance` if it was higher. Existing messages are never overwritten, so on any upgraded server `player.found-source` (if it says the source has moved) and `admin.usage`, `source-located`, `move-usage`, `move-invalid-coords` and `move-success` need updating by hand to the new wording and the `%player%` placeholder.
Expand Down