Purpose and preparation#

SirNukes / bvbohnen's X4 Customizer runs selected transformation plugins and writes an extension. The author documents a Windows build and Python source; use the chosen release's requirements. It is a separate tool.

First exercise#

  1. Launch Start_Gui.bat; configure the game and a dedicated output extension in Config.
  2. Open a small supplied example in Script and inspect selected plugins and output settings.
  3. Use Run Script. Writing files requires the appropriate output plugin, such as Write_Extension documented by the author.
  4. Compare original, patched and post-customizer states in File Viewer; use VFS to check file provenance.
  5. Run Check_Extensions separately to diagnose dependencies and XML patch errors.
POWERSHELL
.\Start_Gui.bat
# Separate diagnostic command:
.\Check_Extensions.bat

Expected result#

The first command opens the GUI; the second runs extension checks and reports diagnostics. It does not establish game effects or request a property transformation.

Checks and limits#

Treat the output directory as generated content; keep unique manual work elsewhere. Account for the enabled DLCs and mods that Customizer reads. Next: compatibility.