yrtria/mod-gold-rush
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: hold the scheduler on an empty server instead of polling into an ambush

Browse source 
Every failed scheduled start overwrote the rolled Min/MaxInterval with a
hard-coded 5 minutes and never restored it, so on a server that sits empty
the scheduler degenerated into a permanent 5-minute poll. The moment the
first player logged in, an event fired within one retry window and anchored
on their exact position, with a server-wide announcement -- login ambush
rather than a scheduled world event. It also wrote a retry line to
gold-rush.log every 5 minutes forever (Debug defaults to 1).

StartEvent now counts eligible anchors when the schedule expires, holds
without consuming the interval while below MinPlayersOnline, and inserts
GraceMinutes once the world repopulates. The count runs only on schedule
expiry, never per world tick.

New config: GoldRush.RetryMinutes (5), GoldRush.GraceMinutes (15),
GoldRush.MinPlayersOnline (1). GraceMinutes = 0 rolls a fresh interval
instead. GM-forced starts pass scheduled=false and bypass both gates.

Verified with clang -fsyntax-only against the live build's compile flags.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019vTNrJGsprcjdjjjDJD5ZM
This commit is contained in:
Claude 2026-09-03 16:58:04 +00:00
parent 6244e2bc65
commit 2857b0580e
No known key found for this signature in database
3 changed files with 123 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

10
CHANGELOG.md
View file

@ -21,7 +21,17 @@ All notable changes to `mod-gold-rush` will be documented in this file.
ground height, rejects cliffs and lower floors, requires line of sight to the anchor,
and retries a few times before giving up on a node.
### Added
- `GoldRush.RetryMinutes` (default 5), `GoldRush.GraceMinutes` (default 15) and
`GoldRush.MinPlayersOnline` (default 1).
### Changed
- The scheduler no longer collapses to a fixed retry poll on an empty server. Previously
every failed attempt overwrote the rolled Min/MaxInterval with a hard-coded 5 minutes
and stayed there, so the first player to log in got an event announced on top of them
within one retry window. It now holds while the world is below `MinPlayersOnline`, and
waits `GraceMinutes` once the world repopulates before running. GM-forced starts
(`.goldrush start` / `teststart`) bypass both checks.
- Node scatter uses a square-root radius so points spread evenly across the disc
instead of bunching near the anchor.
- `DespawnHotspotNodes` resolves the map once instead of per node, and warns if the