Install and Script Workflows

Install And Script Workflows

ChangeEdit separates file-copy work from script-compilation work, but both surfaces follow the same pattern: register entries in a top-level list and add per-item metadata only when needed.

Install Workflow

The install panel uses [InstallList] to map generated section names to destination folders.

[InstallList]
install_folder0=override
install_folder1=modules

Each install-folder section then lists files to copy or replace:

[install_folder0]
File0=my_file.tga
Replace1=my_existing.utc

• FileN means copy into the destination folder.
• ReplaceN marks a replace-style install entry.
• The mass-add dialog can populate large file sets quickly from a folder selection.

Script Workflow

The script panel uses [CompileList] for source script registration:

[CompileList]
File0=k_ai_master.nss

If a script should not land in override, ChangeEdit writes a per-script section:

[k_ai_master.nss]
!Destination=my_module.mod

• !Destination is omitted when the destination is override.
• SaveProcessedScripts in the Settings panel controls whether processed scripts are kept for debugging.

Practical Notes

• Install sections are destination-driven.
• Script sections are source-file-driven.
• Both surfaces are easier to maintain when filenames stay consistent with the actual mod package layout.

Related Pages

• Settings Reference
• changes.ini Structure Map
• Build, Smoke Test, and PR Checklist