Files
Module-Rust/server/model/visibility/visibility.db.js
wtclaude cc185db26b feat(rust): the rewards — tally, kit reward, chat and the news leg (phase 13b, protocol 10)
Four event verbs and the announce leg, per PLAN.md §29:

- rust.participation.open / .collect: the plugin counts who takes part
  (seconds, kills or both, in a zone this run opened or the whole server)
  and collect files them as the run's participants, keyed by Steam id.
- rust.kit.entitle: the five recipient modes (D101), rows in the new
  rust_perm_run_grants (D84) unioned into the permission push, one extra
  use of the kit per reward as site-held credits on perm.sync (D103),
  and the rust.kit.entitled notice deferred from phase 10 (D64).
- rust.announce: one server or every server (D105).
- rust.chat announce leg, speaking only on servers whose new news switch
  is on (D104) - a card on Admin -> Rust visibility (D106).

Budgets rust.grants and rust.announcements; the kit source and four
fixed-choice sources (core has no enum param type). rust_perm_run_grants
carries core's idempotency key so a revert of a lost answer can find its
rows. Protocol 10.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
2026-09-24 07:00:44 -05:00

64 lines
2.6 KiB
JavaScript

// ── SQL for the visibility settings ───────────────────────────────────────
//
// Two stores for one decision: the fleet default in `rust_settings`, and an
// optional per-server override on `rust_servers`. See `schema.sql` for why each
// lives where it does.
const core = require('../../core')
const SETTINGS = 'rust_settings'
const SERVERS = 'rust_servers'
/** One setting's stored value, or `null` when nobody has ever set it. */
async function getSetting(key) {
const rows = await core.query(`SELECT value FROM ${SETTINGS} WHERE setting_key = ?`, [key])
return rows[0] ? rows[0].value : null
}
async function setSetting(key, value, userId = null) {
await core.query(
`INSERT INTO ${SETTINGS} (setting_key, value, updated_by, updated_at)
VALUES (?, ?, ?, CURRENT_TIMESTAMP)
ON DUPLICATE KEY UPDATE value = VALUES(value), updated_by = VALUES(updated_by),
updated_at = CURRENT_TIMESTAMP`,
[key, value, userId],
)
}
/** One server's override, `null` for "inherit", or `undefined` when there is no such server. */
async function getServerPresence(serverId) {
const rows = await core.query(`SELECT presence_audience AS presence FROM ${SERVERS} WHERE id = ?`, [serverId])
return rows[0] ? rows[0].presence : undefined
}
/** Every configured server with its override, in the operator's own order. */
async function listServerPresence() {
return core.query(
`SELECT id, name, enabled, presence_audience AS presence, announce_news AS announceNews
FROM ${SERVERS}
ORDER BY sort_order ASC, id ASC`,
)
}
/**
* Sets or clears (`null`) one server's override.
*
* Returns nothing, deliberately. `affectedRows` would look like a way to tell
* "no such server" from success, and it is not one: without `foundRows` an
* UPDATE writing the value already there reports 0, and whether core's pool sets
* that flag is core's business. The model checks existence with a read first.
*/
async function setServerPresence(serverId, value) {
await core.query(`UPDATE ${SERVERS} SET presence_audience = ? WHERE id = ?`, [value, serverId])
}
/**
* Turns one server's news switch on or off (D104). Existence is the model's
* question, asked with a read first, for the reason given above.
*/
async function setServerNews(serverId, on) {
await core.query(`UPDATE ${SERVERS} SET announce_news = ? WHERE id = ?`, [on ? 1 : 0, serverId])
}
module.exports = { getSetting, setSetting, getServerPresence, listServerPresence, setServerPresence, setServerNews }