-
Notifications
You must be signed in to change notification settings - Fork 0
Advanced Tools
What it is. A built-in text editor for game files, so you can tweak configuration files
(like dlclist.xml, content.xml, setup2.xml, or vehicles.meta) without leaving the app —
useful when a mod's instructions ask you to add or change a line in a loose text/config file.
How to use it.
- Go to Editor.
- Click Open File and choose the file (or Open dlclist.xml to jump to the one set in Settings).
- Edit the text, then click Save.
This is a fully manual tool — you can open and edit any file except executables
(.exe), which are strictly blocked. Saving always backs up the original first, then writes
UTF-8 text and asks for double-consent. Binary files can be opened, but a warning notes that
saving them as text may corrupt them. Writing into a protected folder triggers the on-demand
administrator prompt.
"Editing .exe files is not allowed"? By design — see Safety Model. Binary warning? The file isn't text; don't save unless you are sure it is safe. Save failed? The file may be locked or read-only; close other programs and retry.
What it is. A read-only assistant that inspects a mod folder and explains how to install it — useful when you've downloaded a mod and aren't sure what it contains or where the files go.
How to use it.
- Go to Install Helper.
- Click Select mod folder.
- Read the three sections: How to install (step suggestions), File types (what's in the folder), and Documentation (README / changelog text, selectable and copyable).
The folder is scanned recursively. Files are grouped by extension; README, changelog, .txt,
and .md files are shown in full; and guidance is derived from the detected types (add-on
dlc.rpf, .asi, .dll, .lua, .oiv, .meta). For add-on/dlcpack content it points you to
Install Mods → Add-on or to the Editor for dlclist.xml. It is completely read-only —
it never copies, moves, or changes any file.
"No known mod files detected"? Read the included documentation; the mod may use an uncommon layout.