Skip to content

RF DataData reference

Theme RU

Effects · Mesh effects (Chef)

“Number → EFF” tables

Total 21 Known 21 Derived 0 Unused 0

Used parameters

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\EffectFileList.txt` client file

Total 3 Known 3 Derived 0 Unused 0

Schema: text table (effects.md §4.3)
Registry level: ready for full
Digest: item effects by upgrade level

Offset	Field	What it is and how it acts	Assembled from	Server readers	Role	Status	Data
`—`	`effect number`	key effects.md §4.3	—	—	—	known	—
`—`	`EFF path`	path effects.md §4.3	—	—	—	known	—
`—`	`flag`	≠ 0 — Blend32 by upgrade level, 0 — from the file effects.md §4.3	—	—	—	known	—

`Chef\GuardTower.ini` client file

Total 3 Known 3 Derived 0 Unused 0

Schema: INI “number → EFF” (effects.md §4.1)
Registry level: ready for full

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	—	—	—	known	—
`—`	`path`	EFF path (≤ 255), the file must be on disk effects.md §4.1	—	—	—	known	—
`—`	`;…`	a word with `;` is skipped — only that one word effects.md §4.1	—	—	—	known	—

`Chef\Monster.ini` client file

Total 3 Known 3 Derived 0 Unused 0

Schema: INI “number → EFF” (effects.md §4.1)
Registry level: ready for full

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	—	—	—	known	—
`—`	`path`	EFF path (≤ 255), the file must be on disk effects.md §4.1	—	—	—	known	—
`—`	`;…`	a word with `;` is skipped — only that one word effects.md §4.1	—	—	—	known	—

`Chef\Npc.ini` client file

Total 3 Known 3 Derived 0 Unused 0

Schema: INI “number → EFF” (effects.md §4.1)
Registry level: ready for full

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	—	—	—	known	—
`—`	`path`	EFF path (≤ 255), the file must be on disk effects.md §4.1	—	—	—	known	—
`—`	`;…`	a word with `;` is skipped — only that one word effects.md §4.1	—	—	—	known	—

`Chef\recall.ini` client file

Total 3 Known 3 Derived 0 Unused 0

Schema: INI (effects.md §4.2)
Registry level: ready for full
Digest: animus effects

Offset	Field	What it is and how it acts	Assembled from	Server readers	Role	Status	Data
`—`	`kind`	animus kind (`AnimusItem` row number) effects.md §4.2	—	—	—	known	—
`—`	`level`	a multiple of 5; the client rounds the level down to a multiple of 5 effects.md §4.2	—	—	—	known	—
`—`	`path`	EFF, blend 9 effects.md §4.2	—	—	—	known	—

`Chef\siege.ini` client file

Total 3 Known 3 Derived 0 Unused 0

Schema: INI “number → EFF” (effects.md §4.1)
Registry level: ready for full

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	—	—	—	known	—
`—`	`path`	EFF path (≤ 255), the file must be on disk effects.md §4.1	—	—	—	known	—
`—`	`;…`	a word with `;` is skipped — only that one word effects.md §4.1	—	—	—	known	—

`Chef\Unit.ini` client file

Total 3 Known 3 Derived 0 Unused 0

Schema: INI “number → EFF” (effects.md §4.1)
Registry level: ready for full

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	—	—	—	known	—
`—`	`path`	EFF path (≤ 255), the file must be on disk effects.md §4.1	—	—	—	known	—
`—`	`;…`	a word with `;` is skipped — only that one word effects.md §4.1	—	—	—	known	—

Unused parameters

This category has no unused parameters: every field is read by the server, the client or the build.

← Back to category