What is managed
A DarkRP job spawn is a per-map, per-job spawn position: where a player of that job appears when they spawn. DarkRP stores them in its own database. Blueprints versions the position and which job it belongs to. That is the whole domain.The SQLite requirement
The reason is structural rather than a missing feature. A capture must answer synchronously: it has to return the world as it is, now. DarkRP’s storage layer runs inline on SQLite and is genuinely asynchronous on MySQL, so on MySQL there is no way to answer honestly at capture time. Rather than serving a cached answer that might be one write behind, the adapter reports itself unavailable with that reason, and its domain is left out of every Version. That is the safe outcome. A Version that recorded “there are no job spawns” would, restored, delete every one of them. The limit is scoped to this one adapter. Props, NPCs and every other part of Blueprints work normally on a MySQL DarkRP server. You will see the DarkRP adapter listed as unavailable on the Adapters screen, with the sentence explaining why, and nothing else changes.What it does not manage
Job definitions
Job definitions
Blueprints versions spawn points, not the jobs themselves. A Version that references
the
gundealer job restores onto a server where that job exists. Where it does not, the
object is refused with that reason rather than silently recreated.Jail positions
Jail positions
Out of scope. They live in the same DarkRP table but are a different business concept,
and Blueprints leaves them alone.
Moving a spawn between jobs
Moving a spawn between jobs
Not offered, because DarkRP exposes no way to do it. Re-inserting a row under a
different job would be a different spawn wearing an old identity, and the adapter
declines to claim a capability it cannot honour. This is why the adapter does not
declare property restoration at all.
Orientation
Orientation
A spawn is three coordinates. DarkRP does not store which way the player faces, so there
is nothing to capture and the adapter declares no orientation. Migration placement, the
ghost preview and post-restore verification all ignore angles accordingly, instead of
reporting a spawn as mis-rotated on three axes nothing ever wrote.
Identity
Job spawns are the strongest identity Blueprints has:persistent.
The id is DarkRP’s own primary key. DarkRP assigns it, the column never reissues a value,
the row is scoped to a map by its own column, and it lives in a database rather than in a
server session. Nothing about it is derived from a position, a model or an ordinal.
That means job spawns survive a server restart cleanly, and can be honestly restored across
one, which is not true of props and NPCs.
Verified against
DarkRP 2.7.0 (Workshop id248302805), on SQLite, validated in game including a real
server process restart.