WadFusion — simple IWAD merge utility

[Owlet VII]

I am very confused. Where are those errors from? What version of WadFusion and UZDoom is used? Why did you rename the IPK3 to a WAD?

For now, stable builds of WadFusion need to be matched with stable builds of UZDoom, and dev builds of WadFusion need to be matched with dev builds of UZDoom. This will remain a necessity until the next UZDoom release.

Do not rename the file extension of the generated IPK3. That will cause issues.

[DarkShadow]

1 image was from Delta touch and second image was from PC using wad fusion dev build with both. But i got these solved. Turns out that i needed to use wadfusion version 1.5.1 and it works great with delta using gz doom but in order to use it with delta UZdoom i need to edit the zscript.zs file. But now all is good.

[ZzZombo]

That is an excellent suggestion. I'll add a command line option to specify a source directory, and I'll also look into adding an option for the script to read from a text file with a list of directory paths (or specific files) that the user could set for it to search in.

Did you add it? I skimmed through the changelog, but found no mentions.

[TheVanessii]

Would it be possible to make a sort of system where any mod that calls for a LoR monster is funneled into the actor tag that WadFusion uses? For example, if a mod modifies the Vassago, but it looks at the tag "Deh_Actor_154" or "Vassago" instead of "ID24Vassago", there's something put in place that redirects it to that tag to be changed? There's a couple mods out there that change / enhance LoR content, but they just don't work with WadFusion due to actor name discrepancies (I think)

[Owlet VII]

That is an excellent suggestion. I'll add a command line option to specify a source directory, and I'll also look into adding an option for the script to read from a text file with a list of directory paths (or specific files) that the user could set for it to search in.

Did you add it? I skimmed through the changelog, but found no mentions.

I added it just now, you should be able to specify a source directory with the --wads argument, let me know if this is what you wanted. The option to specify paths for specific WADs is something that I have planned for a version 2.0.0 rewrite.

Would it be possible to make a sort of system where any mod that calls for a LoR monster is funneled into the actor tag that WadFusion uses? For example, if a mod modifies the Vassago, but it looks at the tag "Deh_Actor_154" or "Vassago" instead of "ID24Vassago", there's something put in place that redirects it to that tag to be changed? There's a couple mods out there that change / enhance LoR content, but they just don't work with WadFusion due to actor name discrepancies (I think)

Could you please give me examples of such mods? The way it's set up right now, DeHackEd patches should take priority, so I'm not sure what's breaking there.

Fusion no longer uses its own actors for the LoR monsters, those were moved to UZDoom. Fusion now only tells the game to use the native UZDoom actors in place of the DeHackEd actors, but as I said, loaded DeHackEd patches should take priority.

[AliciaPendragon]

Just used this to replace my old wadsmoosh iwad after I updated to UZDoom, and holy fuck

with everything, 249 maps across 18 epsiodes and the option to use the IDFKA, Buckethead and Thorr soundtracks??? Hell yeah!

[Owlet VII]

TheVanessii, I found one of the mods you must have been referring to: Legacy of Rust ENHANCED Content.

I can't make it work from Fusion's end. The way that mod works is by replacing any "Deh_Actor_150" to "Deh_Actor_155" DeHackEd actors that exist through a CheckReplacement ZScript event, and those actors are added by Legacy of Rust's DeHackEd patch. WadFusion doesn't extract the Legacy of Rust DeHackEd patch, so the mod has nothing to replace. Instead, Fusion assigns the editor numbers used by LoR maps to the ZScript implementation of the actors. This is a cleaner solution than extracting the DeHackEd patch.

This is something that should be fixed on the mod's side—it would also be a problem with any maps made for the ID24 spec, not just with Fusion. Checking the UZDoom actors for replacement in addition to the LoR DEH actors should fix it.

[ZzZombo]

Hey, thanks for getting around to adding. It was my fault for not being specific enough. My library is organized as a folder for IWADs only and folder for PWADs. SIGIL and such are in the latter and, well, IWADs are in the former. That's why I was hesitant to use WadSmoosh in the past, ruining my library organization would suck. Anyway, what I am getting at is, could you make the `-w` argument cumulative when specified several times?

[Owlet VII]

I see. Sure, I'll try to have it done later today.

[ZzZombo]

That's rad! Thank you!

EDIT: I just realized I forgot to subscribe to GitHub releases. Done!

[Owlet VII]

Hey, no problem.

Small status update: I've already modified the script to support passing multiple paths to search for WADs, but supporting all the various filenames that Sigil 1 & 2 were released with is now a pain in the ass. I'll publish the changes once I have that figured out.

EDIT: It's done and published. I probably won't be adding any more similar features until the 2.0.0 rewrite I have planned. Note that you'll need to clone the repository, this feature (and all the changes to WadFusion since May 2025) hasn't been "released" yet.
Hopefully I didn't break anything, since I had to make some big changes for this to work, and I can go back to my playthrough of Silent Hill in peace.

[ZzZombo]

Great, just got around to playing with this. Will report if anything bad happens.