Vonix Server Utilities — Configuration & Data Path

Release Line: 2.0.2 Configuration ArchitectureLocal Properties & SQLite

VSU is entirely configured through local property files. It requires no external network endpoints, API keys, or web panel synchronization.

1. Properties File Reference

File location: config/vonix_server_utilities.properties (auto-generated on first launch):

# Maximum number of homes permitted per non-op player
max_homes=5

# Timeout in seconds before pending /tpa requests expire
tpa_timeout_seconds=120

# Optional delay before returning to death coordinates via /backdeath
death_back_delay_seconds=0

# Outside-Mod SPI Feature Gates (Default Fail-Closed)
panel_events_enabled=false
panel_stats_enabled=false
panel_death_history_enabled=true
panel_inventory_read_enabled=false
panel_teleport_actions_enabled=false

---

2. Dynamic Feature Management (/vonixsu feature)

Subsystems can be inspected and toggled at runtime without restarting the server:

Command	Purpose
/vonixsu feature list	View all registered feature subsystems and their runtime state.
/vonixsu feature enable <key>	Activate a specific subsystem (e.g. homes, warps, tpa).
/vonixsu feature disable <key>	Deactivate a subsystem (subsequent commands will report disabled).
/vonixsu feature reload	Re-read properties from disk and refresh active gates.
/vonixsu feature status <key>	Check detailed metrics for an individual feature gate.

# Runtime management example
/vonixsu feature disable crates
/vonixsu feature enable homes
/vonixsu reload

---

3. SQLite Persistence & WAL Mode

All homes, warps, moderation records, and virtual crate balances are stored in: config/vonix_server_utilities/data.db

• Write-Ahead Logging (WAL Mode): VSU initializes SQLite in WAL mode (PRAGMA journal_mode=WAL). This allows simultaneous read and write operations without database locking, preventing lag spikes when players save homes or query warnings.
• In-Place Reuse: Existing databases from prior VSU versions are detected and upgraded safely in place.

---

4. Retained Snapshot Recovery (v2.0.1+)

VSU includes an idempotent migration engine designed to recover historical server data from backup snapshots:

• Safe Import: On startup, if configured to ingest a retained VSU data.db backup, homes and /back//backdeath coordinates are imported transactionally.
• Source Immutability: The source backup snapshot is never modified or overwritten.
• Fingerprint Markers: A content-fingerprint marker is written to the database only after a recognized VSU source imports completely. Corrupted or partial non-VSU databases are skipped safely for later retry.

Migration Notice: VonixCore to VSU

Direct import from legacy VonixCore databases is no longer the supported migration path. Recovery procedures target retained VSU data.db schemas exclusively.