Difference between revisions of "Data File"
no edit summary
imported>Google0008 |
imported>Google0008 |
||
| Line 22: | Line 22: | ||
'''Light Plugin:''' <code>.esl</code> | '''Light Plugin:''' <code>.esl</code> | ||
*Light plugin (.esl) file are a new optimized file format, introduced in the 1.10 Update. They behave like a normal plugin, except for the following: | *Light plugin (.esl) file are a new optimized file format, introduced in the 1.10 Update. They behave like a normal plugin, except for the following: | ||
**.esl files are read-only. Active development should be done in an normal (.esp) plugin. | |||
**.esl files bypass the 32-bit plugin ID limit (255). | **.esl files bypass the 32-bit plugin ID limit (255). | ||
**.esl files have a budget of no more than 4,000 forms. | **.esl files have a budget of no more than 4,000 forms. | ||
**.esl files are treated as unique files from the .esp it was converted from, so saved games will not be compatible between them. | **.esl files are treated as unique files from the .esp it was converted from, so saved games will not be compatible between them. | ||
*To convert a normal plugin (. | *To convert a normal plugin (.esp) to a light (.esl) plugin, load your .esp file, and under File, select Convert Active File to Light Master. | ||
*It is good practice to run Compact Active File Form IDs to optimize your formids within the 4,000 form budget. | *It is good practice to run Compact Active File Form IDs to optimize your formids within the 4,000 form budget. | ||
**NOTE: Compacting form ids does change formids in the plugin, so only do this before converting to .esl, and not on a .esp (plugin) you plan on releasing. | **NOTE: Compacting form ids does change formids in the plugin, so only do this before converting to .esl, and not on a .esp (plugin) you plan on releasing. | ||