23 lines
1.5 KiB
Markdown
23 lines
1.5 KiB
Markdown
## Why
|
|
|
|
SCUM player intelligence currently presents useful local identity and risk context, but administrators cannot safely correct the limited in-game state that the installed server version explicitly supports. A controlled patch workflow is required so changes remain reviewable, version-fenced, approved, and executed only through the companion command channel.
|
|
|
|
## What Changes
|
|
|
|
- Add a SCUM version-scoped player-state field catalog for supported skills and character attributes only.
|
|
- Add player-state read snapshots and an approved `game-state.patch` bridge operation with optimistic state-version checks, safe execution-window checks, and confirmation reads.
|
|
- Persist an immutable patch audit record containing requested old/new values, reason, requester/approver, command result, and confirmation status.
|
|
- Add authorized API contracts and Chinese console controls that show the editable diff, approval state, readable outcome, and player context.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
|
|
- `scum-player-state-patch`: Version-fenced, approved SCUM player skill and character-attribute changes via the game-client bridge.
|
|
|
|
## Impact
|
|
|
|
- Affects Platform player domain/models/repositories/services/validation/API and durable metadata storage.
|
|
- Extends the SCUM manifest with a bounded patch command and typed schemas, plus Platform Web contracts and console records.
|
|
- Does not permit SQL, raw configuration/JSON/INI writing, direct game database access, unbounded state editing, automatic moderation, gifts, or map trails.
|