🗄️ Data & Database

LogBook uses a MySQL database to persist all operational data, including users, jobs, XP, ranks, and logs. This page outlines the core table structure and their relationships.

Core tables

• vtc_users – list of users with XP, role, SteamID, VTC tag
• vtc_jobs – submitted deliveries (manual or via API)
• vtc_xp – XP thresholds and rank names
• xplog – log of manual or bonus XP changes (reason, who, when)

Table structure examples

vtc_users

• steamid – unique user identifier
• username – display name
• total_xp – cumulative XP
• role – driver / admin / dispatcher
• joined_at – timestamp of registration

vtc_jobs

• id – auto-increment job ID
• steamid – user who submitted the job
• cargo, source_city, destination_city
• distance, delivery_time
• xp_earned

vtc_xp

• rank – name of the rank (e.g. "Local Driver")
• xp – XP required to reach this rank

xplog

• id, steamid
• reason, xp, timestamp
• Used to track manual XP additions or adjustments

VTC prefix logic

Tables can be prefixed per VTC (e.g. abc_vtc_jobs), allowing multi-VTC support within the same system instance.

Query tips

• Always sanitize input when querying by SteamID or VTC tag
• Use indexes on steamid and delivery_time for performance
• JOINs between users and jobs should use indexed fields

← Back to Wiki Index