# server-data/ — direct-port runtime files (ready to deploy)

These files are **direct copies** from the legacy 1.7.10 server. JSON schema identical between 1.7.10 and 1.12.2 vanilla Forge — they work as-is when copied to the server root on first boot.

## Files

| File | Purpose | Notes |
|---|---|---|
| `ops.json` | 6 server operators (level 4 each) | Stasik, BeckerOFF, Ma3auka, FoxySister, voyan, microwin7. UUIDs preserved. |
| `whitelist.json` | Whitelist (4 entries from legacy) | Whitelist enforcement off in `server.properties` (matches legacy `white-list=false`). |
| `banned-players.json` | Banned UUID list | Empty in legacy snapshot |
| `banned-ips.json` | Banned IP list | Likely empty in legacy snapshot |

## Deploy

Ansible playbook copies these files from `industrial-server/config/template/server-data/` → `<pelican volume>/` on **first boot only**. Live edits via in-game `/op`, `/whitelist`, `/ban` are not overwritten on subsequent deploys.

## What is NOT here

Other items from legacy `storage/` that need replacement on 1.12.2:
- `warps.json` — needs a 1.12.2 /warp mod (FE Commands or RandomTeleport+companion). See PORT_NOTES_PLUGINS.md § 1.5.
- `usercache.json` — Forge regenerates on first boot
- `help.txt` — Ultramine-specific, not used on 1.12.2

## Security note

⚠️ Legacy `settings/server.json` contained the rcon password in cleartext: `5bcsdg5sxgx5segxw4svsv5savsae5vesv`. **Do not reuse**. Generate a fresh password, store in 1Password vault `AlaMine` → `Industrial RCON`, set in Ansible group_vars.