Fields read by the server or the client, or assembled from other files. The description says what the field means and how it acts; below it — where that was established.
Map\<map>\<map>.sptclient file
Total 3Known 3Derived 0Unused 0
Schema
dummy text (maps.md §2)
Registry level
ready for full
Digest
client copy; dummies needed by both must match (maps.md §8)
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
*name
dummy name; the prefix (*dm, *dp, *sd, *ds, *Ndr, *bd, *dq, *sa) selects the table; case matters
maps.md §2
—
—
—
known
—
—
min/max (6 numbers)
box, read as integers
maps.md §2
—
—
—
known
—
—
-node_tm` + 4×4 matrix
position — the last row of the matrix
maps.md §2
—
—
—
known
—
Map\<map>\<map>_dummy.sptclient file
Total 4Known 2Derived 2Unused 0
Schema
[LevelDummyListBegin], then records type code x y z: 1 — monster, 2 — NPC etc. (maps.md §3.4)
Registry level
derived
Derived from
server spawn blocks: [BLOCK].dat + spawn files + the dummy named after the block (type 1 records, maps.md §3.5); type 2 records — as imported
Digest
type 1 — quest target markers on the minimap, derived from the server spawn blocks (maps.md §3.4–3.5); type 2 is not used by the client; assembled automatically when the spawn changes (user decision 29.10.2026)
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
[LevelDummyListBegin]
rows before it are skipped
maps.md §3.4
—
—
—
known
—
—
type
1 — monster (lookup in Character.edf), 2 — NPC; others are removed
maps.md §3.4
spawn files / NPCs of the map
—
server → client
known
—
—
code
monster or NPC code (hex, at most 5 characters)
maps.md §3.4
spawn codes of [BLOCK]/<block>.dat, NPCs
—
client
derived
—
—
x y z
marker coordinates
maps.md §3.4
dummies of <map>.spt
—
client
derived
—
Map\<map>\<map>EXT.sptclient file
Total 3Known 3Derived 0Unused 0
Schema
dummy text (maps.md §2.1)
Registry level
ready for full
Digest
in the client — also music zones (sounds.md §5.3)
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
*name
town zone; the first letter is the town race (b/c/a/elan), otherwise the object's race
maps.md §2.1
—
—
—
known
—
—
min/max (6 numbers)
zone box
maps.md §2, §2.1
—
—
—
known
—
—
-node_tm` + 4×4 matrix
as in <map>.spt
maps.md §2
—
—
—
known
—
Map\<map>\<map>.sptserver file
Total 3Known 3Derived 0Unused 0
Schema
dummy text: *name + box + -node_tm (maps.md §2)
Registry level
ready for full
Digest
dummy type — name prefix; the NeutralC folder holds copies of NeutralA/B.spt
Offset
Field
What it is and how it acts
Goes to client as
Server readers
Role
Status
Data
—
*name
dummy name; the prefix (*dm, *dp, *sd, *ds, *Ndr, *bd, *dq, *sa) selects the table; case matters
maps.md §2
—
—
—
known
—
—
min/max (6 numbers)
box, read as integers
maps.md §2
—
—
—
known
—
—
-node_tm` + 4×4 matrix
position — the last row of the matrix
maps.md §2
—
—
—
known
—
Map\<map>\<map>EXT.sptserver file
Total 3Known 3Derived 0Unused 0
Schema
dummy text (maps.md §2.1)
Registry level
ready for full
Digest
town zones
Offset
Field
What it is and how it acts
Goes to client as
Server readers
Role
Status
Data
—
*name
town zone; the first letter is the town race (b/c/a/elan), otherwise the object's race
maps.md §2.1
—
—
—
known
—
—
min/max (6 numbers)
zone box
maps.md §2, §2.1
—
—
—
known
—
—
-node_tm` + 4×4 matrix
as in <map>.spt
maps.md §2
—
—
—
known
—
Unused parameters
This category has no unused parameters: every field is read by the server, the client or the build.