Add proximity-based map record reminders
This commit is contained in:
@@ -6,6 +6,48 @@ T5/T6 script and each native plugin. Current versions are recorded in
|
||||
|
||||
## 2026-10-17
|
||||
|
||||
### Increase map-record reminders as players approach the target
|
||||
|
||||
| Component | Version | Affected source |
|
||||
| --- | --- | --- |
|
||||
| `tws_t5_leaderboard.gsc` | `1.2.0` | `t5/scripts/tws_t5_leaderboard.gsc` |
|
||||
| `tws_t6_leaderboard.gsc` | `1.2.0` | `t6/scripts/tws_t6_leaderboard.gsc` |
|
||||
| `tws_t5_common.gsc` | `1.5.0` | `t5/scripts/tws_t5_common.gsc` |
|
||||
| `tws_t6_common.gsc` | `1.5.0` | `t6/scripts/tws_t6_common.gsc` |
|
||||
|
||||
- Add matching T5/T6 round-start reminders using the latest usable cached map
|
||||
record. Show at gaps of 20, 15, 10, 8 and 6 rounds, then every round for the
|
||||
final five. Show matching/overtake milestones, then stop reminders after the
|
||||
first overtake for the rest of the match. Milestones distinguish reaching a round
|
||||
from saving the result after match completion; `.leaders` remains available.
|
||||
Listen to the stock `start_of_round` event so reminders follow the actual
|
||||
start, including on T6 where the counter advances during the round break.
|
||||
Ignore duplicate starts and counter rewinds within the match.
|
||||
- Common renders a compact record header and one proximity/milestone line for
|
||||
six seconds, using two nonarchived elements in the existing service area.
|
||||
Keep full join/`.leaders` announcements, all tied holders and 12-second pages.
|
||||
Skip pending or active help/records, unready players and recent welcome/manual
|
||||
record requests; opening help discards a reminder. Release elements on idle,
|
||||
interruption, disconnect and game end. Both games work without optional HUD.
|
||||
- Reuse the cache without round-triggered HTTP requests. Empty, unavailable or
|
||||
expired records suppress reminders; skipped reminders are not queued.
|
||||
- Compatibility: leaderboard `1.2.0` requires matching common `1.5.0+`.
|
||||
There is no new native-plugin, backend or upstream dependency requirement.
|
||||
Unchanged HUD, AFK and other scripts retain their individual versions.
|
||||
- Validation: 169 leaderboard, 14 core HUD, 72 service HUD, 42 bank, 17 join,
|
||||
23 telemetry and 39 AFK portable checks passed, as did both moderation
|
||||
script checks. All nine T6 scripts compiled/assembled with upstream gsc-tool
|
||||
`8f1d6bd` libraries; the final changed common/leaderboard sources were rechecked
|
||||
after the event-timing fix. JSON uniqueness, all 18 script manifest entries,
|
||||
version/changelog consistency, local documentation links and `git diff --check`
|
||||
passed. Portable checks use engine shims; no live Plutonium validation or
|
||||
backend integration was performed. T5 has no gsc-tool compiler backend.
|
||||
- Deployment: copy the updated leaderboard and common scripts together for
|
||||
each installed game, then restart the map. No full server-process restart is
|
||||
required for this script-only update. No deployment performed. Live T5/T6
|
||||
rendering, readiness and round-transition validation remain required; see
|
||||
[record validation](README.md#map-record-announcements).
|
||||
|
||||
### Persistent AFK reserve and immediate expiration (Refs #12)
|
||||
|
||||
| Component | Version | Affected source |
|
||||
|
||||
Reference in New Issue
Block a user