Project Infinity overwrites Setup-ModName.debug for multi-component installs

[beetheimer23]

Project Infinity 0.10.7 appears to overwrite the conventional Setup-ModName.debug file with each component when multiple components from the same mod are installed. This results in each .debug log containing only the last component installed.

This is specific to Project Infinity, since mods installed with the standard WeiDU technique correctly append the .debug files without issue. I am aware that the PI Logs folder does contain logs for each component, and thus takes over the job. Nevertheless, this became an issue for me when I trusted that the debugs faithfully contained all the components, before discovering the discrepancy.

Setup-eefixpack.debug
WeiDU.log

ProjectInfinity-WeiDU-Debug-eefixpack-0.log

ProjectInfinity-WeiDU-Debug-eefixpack-2.log

ProjectInfinity-WeiDU-Log-Finished-Installation-2026.09.10-15꞉11.log

I reproduced this with EEFixpack Beta 2 using WeiDU 251.00. Components 0 (Core Fixes) and 2 (Game Text Update) both installed successfully. PI's own output and WeiDU.log confirm that both components were installed. However, after the installation, Setup-eefixpack.debug contains only the later component 2 installation.

The surviving component-2 invocation uses:

--force-install 2 --log Setup-eefixpack.debug

and does not use --logapp, so the conventional debug file thereby gets replaced by each successive component invocation.

To Reproduce

Start Project Infinity 0.10.7.
Use a mod with multiple independently installable components. I used EEFixpack Beta 2.
Select at least two components from the same mod. I selected component 0 (Core Fixes) and component 2 (Game Text Update).
Install them in the same PI operation.
Confirm in WeiDU.log that both components are installed.
Open Setup-eefixpack.debug in the game directory.
Observe that it contains only the later component's installation output, rather than both components.

Expected behavior
Setup-ModName.debug should preserve the complete debug history for the mod components installed during the PI operation.

For example, PI could create/truncate the conventional debug file when beginning the first component for that mod, then append subsequent component invocations, or otherwise consolidate the per-component PI logs into a complete conventional Setup-ModName.debug.

[GraionDilach]

What is the practical usecase here?

The individual logs offer better searchability and traceability (especially when combined with commands like grep). The merged debug file is really hard to trace when you install a platitude of components from the same mod during an installation.

Note that this is not a bug, but a feature request anyway, because --logapp isn't enabled as a default in WeiDU.

[beetheimer23]

guess my PI Logs folder gets a little cluttered sometimes. I thought it was easier to navigate to debugs for my provenance program. But I see what you mean, I will try to use PI logs.