1.6 KiB
1.6 KiB
Why
SCUM operators can invoke a one-off reward bridge command but cannot safely curate reusable gifts, freeze what was approved, or establish whether a targeted player received an item and its notification exactly once. A version-fenced gift workflow turns that raw capability into an auditable, least-privilege server-management operation.
What Changes
- Add editable SCUM gift catalogs with immutable published revisions and items sourced only from the currently verified server-version item catalog.
- Add durable, approval-gated targeted gift grants that freeze the selected revision and game-player identity before dispatching the declared
reward.delivercommand. - Track gift delivery and directed-notification results independently, including visible notification failures and terminal unknown delivery outcomes that are never retried automatically.
- Add safe Platform APIs, SCUM plugin schemas, and Chinese console workflows for catalog editing, revision preview, player selection, confirmation, approvals, and grant history.
Capabilities
New Capabilities
scum-versioned-gift-catalog: Version-scoped SCUM gift definition, immutable revisions, approval-gated directed delivery, and safe operational history.
Modified Capabilities
- None.
Impact
- Affects Platform domain/model/repository/service/validation/API layers and durable metadata persistence.
- Extends the SCUM plugin's typed client-bridge declarations and schemas, plus Platform Web API contracts and SCUM player console.
- Does not introduce commerce, direct RCON/game connections, arbitrary item/generator commands, raw game credentials, or raw database writes.