AddOnNode: Difference between revisions
Jump to navigation
Jump to search
Data on AddOnNode ID's numerical limits.
DavidJCobb (talk | contribs) No edit summary |
(Data on AddOnNode ID's numerical limits.) |
||
| Line 1: | Line 1: | ||
The '''add-on node''' system allows one NIF model to include the contents of another NIF model by reference. You can't specify arbitrary NIF files; rather, the game data defines a library of reusable NIFs. | The '''add-on node''' system allows one NIF model to include the contents of another NIF model by reference. You can't specify arbitrary NIF files; rather, the game data defines a library of reusable NIFs. | ||
In your ESP file, you can define an "AddOnNode" form, which consists of a 3D model and a unique numeric ID. Then, in any NIF file, you can create a BSValueNode. This is, functionally, just a local transform (i.e. offset from its parent node) and a value. In practice, however, the "value" specifies one of those unique numeric IDs. Skyrim will look up the appropriate AddOnNode form, load its NIF, and copy the contents of that add-on NIF to where the BSValueNode is. | In your ESP file, you can define an "AddOnNode" form, which consists of a 3D model and a unique numeric ID. Then, in any NIF file, you can create a BSValueNode. This is, functionally, just a local transform (i.e. offset from its parent node) and a value. In practice, however, the "value" specifies one of those unique numeric IDs. Skyrim will look up the appropriate AddOnNode form, load its NIF, and copy the contents of that add-on NIF to where the BSValueNode is. AddOnNode ID's values are limited to 65538. Numbers exceeding the limit will result in crashes. | ||
Here are a few examples: | Here are a few examples: | ||