19 lines
1.1 KiB
Markdown
19 lines
1.1 KiB
Markdown
# Rebuild SCUM Plugin-Owned Data
|
|
|
|
## Why
|
|
|
|
The previous SCUM data implementation placed game-specific projections, gift rules, and browser callbacks in Platform. That couples every SCUM version change to Platform releases and makes the implementation larger than the required relay role.
|
|
|
|
## What Changes
|
|
|
|
- Replace the recent SCUM direct-data and game-gift additions with a generic plugin data store and generic plugin-page data bridge.
|
|
- Keep SCUM SQLite, configuration, and log access plugin-declared and dispatched through Platform to Run.
|
|
- Put SCUM `scum_*` collection names, record shapes, gift catalog/grant behavior, map rendering inputs, and feature UI in the SCUM plugin package.
|
|
|
|
## Success Criteria
|
|
|
|
- Platform exposes no SCUM-, squad-, map-, or gift-specific data API/service/model added by this change.
|
|
- The SCUM plugin can read and write its scoped platform collections for users, squads, activity, gifts, and map points through generic bridge calls.
|
|
- Version-specific SQL/config/log declarations remain in the SCUM manifest and assets.
|
|
- Existing generic lifecycle and machine-job dispatch behavior remains intact.
|