browser/openspec/changes/rebuild-scum-plugin-owned-data/evidence/scum-local-data-baseline-2026-08-18.md

SCUM Local Data Baseline - 2026-08-18

Scope

This is redacted structural evidence from the user-authorized local SCUM download and legacy projects. It records no player names, Steam IDs, IP addresses, coordinates, credentials, or row bodies.

Database

• /Users/tasia/Downloads/SCUM/Logs/SCUM.db is an empty zero-byte file and is not usable evidence.
• /Users/tasia/Downloads/SCUM/SCUM.db is the complete database: SQLite user_version=57, 162 tables, quick_check=ok.
• Aggregate rows: 74 accounts, 73 profiles, 72 prisoners, 7 squads, 18 squad members, 313 vehicles, 5 bases, 5 flags, 0 native event rounds, and 2 native timed-gift completion records.
• All nine packaged v57 SQL assets execute against the complete database.
• The account/profile cardinality proves that user extraction must start from user and left join the optional profile chain. Steam ID is the stable collection identity; profile ID, prisoner ID, and display name are attributes.
• The current map query returns player, vehicle, base, and flag points and the observed coordinates fit the declared SCUM island bounds.

Logs

• The download contains 568 UTF-16LE/LF log files across 19 filename prefixes. Filenames use a server-start timestamp and a file can continue growing for many hours; tailing therefore requires an offset cursor per file rather than a daily filename assumption.
• Each file starts with a blank line and one Game version: metadata line that must not become a business event.
• Login file logs contain single-line login/logout records with optional coordinates.
• The user-supplied BattlEye reported, connected, SteamID, and GUID sequence is supervised process stdout and does not occur in the downloaded file logs. It requires a separate ordered stdout projection.

Configuration

• The configuration directory contains ServerSettings.ini, list-based access files, EconomyOverride.json, RaidTimes.json, Notifications.json, and engine input/user settings.
• ServerSettings.ini reports settings version 7 and contains hundreds of scum.* keys. Config reads and patches must preserve unknown keys rather than reconstructing the file from a short allowlist.

Legacy Behavior

• The legacy robot continuously updated players and positions in the background and queued welcome text through the server command channel; browser presence was never the acquisition trigger.
• Legacy welcome behavior distinguishes first registration from a returning player and suppresses rapid repeated observations. This change uses the explicitly requested ten-minute window.
• The legacy implementation contains field-order mistakes in its user creation branch, so only its product behavior and stable field intent are reused, not its SQL/value assignments.