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.
Chef\Real\Entity.iniclient file
Total 5Known 5Derived 0Unused 0
Schema
INI (effects.md §5.9)
Registry level
ready for full
Digest
map cutscenes .rvp
A separate table for map cutscenes, same format as Chef\Entity.ini.
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
[ENTITY_INFO] MAXENTITY
record count
effects.md §2, effects.md §5.9
—
—
—
known
—
—
[ENTITY1…N]
record section
effects.md §2, effects.md §5.9
—
—
—
known
—
—
INDEX
number that EFF files reference (< 0xC00)
effects.md §2, effects.md §5.9
—
—
—
known
—
—
ENTITY
path
effects.md §2, effects.md §5.9
—
—
—
known
—
—
ABSAXIS
default 1: the particle does not rotate with the object
effects.md §2, effects.md §5.9
—
—
—
known
—
Chef\Real\Monster.iniclient file
Total 1Known 0Derived 0Unused 1
Schema
INI (effects.md §5.9)
Registry level
ready for full
Digest
map cutscenes .rvp
Chef\Real\Particle.iniclient file
Total 5Known 5Derived 0Unused 0
Schema
INI (effects.md §5.9)
Registry level
ready for full
Digest
map cutscenes .rvp
A separate table for map cutscenes (.rvp), same format as Chef\Particle.ini.
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
[PARTICLE_INFO] MAXPARTICLE
record count
effects.md §2, effects.md §5.9
—
—
—
known
—
—
[PARTICLE1…N]
record section
effects.md §2, effects.md §5.9
—
—
—
known
—
—
INDEX
number that EFF files reference (< 0xC00)
effects.md §2, effects.md §5.9
—
—
—
known
—
—
PARTICLE
path
effects.md §2, effects.md §5.9
—
—
—
known
—
—
ABSAXIS
default 1: the particle does not rotate with the object
effects.md §2, effects.md §5.9
—
—
—
known
—
Chef\Real\Unit.iniclient file
Total 3Known 3Derived 0Unused 0
Schema
INI (effects.md §5.9)
Registry level
ready for full
Digest
map cutscenes .rvp
“number → EFF” for cutscenes: the number is the mesh_id of the cutscene object.
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
—
number
table key (see “Key” in §4.1); on a duplicate the first row applies
effects.md §4.1, effects.md §5.9
—
—
—
known
—
—
path
EFF path (≤ 255), the file must be on disk
effects.md §4.1, effects.md §5.9
—
—
—
known
—
—
;…
a word with ; is skipped — only that one word
effects.md §4.1, effects.md §5.9
—
—
—
known
—
Unused parameters
Fields that neither the server nor the client reads. For each: why it was decided so and where that was established. The editor keeps their bytes as they are.
Chef\Real\Monster.iniclient file
Offset
Field
Why unused
Data
—
contents
the client does not open the file: the strings .\chef\real\monster.ini / real\monster are absent in the AoP image (entity.ini, unit.ini, particle.ini are present)