Versions
A Version is an immutable, timestamped record of the managed world at one moment, on one map.- It is a full record, not a patch on the Version before it.
- It is scoped to a map. A Version captured on
gm_constructdescribesgm_construct, and restoring it onrp_downtownis refused rather than attempted. - It records which adapters were authoritative when it was taken, and what data format each of them was writing. That manifest is what lets Blueprints tell “this domain was empty” from “this domain was unknown” years later.
- It is never edited. Restoring, exporting and deploying all read it.
The product says Version. The stored document, the file on disk and the Adapter SDK all
say snapshot. They are the same object; the word changes at the glass and nowhere else.
Objects
An object is one managed thing, recorded as plain data:
There are no engine handles in a Version. A prop is recorded as six numbers and a handful
of strings, which is what lets a Version survive a restart, a map change and a trip to
another server.
Identity
Identity is how Blueprints decides that the prop in Friday’s Version and the prop in the world right now are the same prop. Every adapter declares the strength of the guarantee its ids carry:survives a restart
The same real object yields the same id after a full server restart, and that id is never
reissued to something else. Only persistent domains can be honestly restored across a
restart. DarkRP job spawns and saved PermaProps are persistent, because a database row
holds the id.
stable while the server runs
Unique and stable for the life of the process. A restart may invalidate it. Correct for
anything held only in memory, which is most props and every NPC.
no guarantee
Reported loudly and excluded from safe restore.
session-scoped, Blueprints reports those members as cross-session rather than
matching them by luck. A tool that guessed here would apply one object’s recorded state to
another, and the person watching would have no way to tell.
Adapters
An adapter teaches Blueprints one domain. Four ship with the product. Anyone can write more, and they get exactly the same contract, the same functions and no privilege the built-ins do not have. An adapter declares which operations it can honour for every object it produces:Groups, anchors and pivots
A group is a named set of up to 512 objects with its own anchor: the point the group is measured from and moved by. Groups are what migration and cross-server deployment operate on, because “the market stall” is a thing you built and “these forty props” is not. Full detail in Groups, anchors and pivots.Plans
Every destructive operation in Blueprints is planned before it is run, and the plan is shown to you in full. A plan states:- what will be created, moved, conformed and destroyed, per object;
- what it cannot act on, and why, in a sentence;
- what will be left alone because no adapter is authoritative over it.