Recent game update broke the mod this mod relies on. Specifically "Legacy Mod" which this mod had bundled.
Only way to get this mod to work at this point is to down patch Doom to the previous version.
Ill look into remaking this mod in the way my Doom Eternal version is made but Im unsure if thats possible atm.
Ive updated the link on the main page to the latest Doom Mod Launcher however with the current version of the game; it wont launch the game automatically.
See below note from Modding Discord:
**DOOM (2016) has been updated.** The good news is, it's a very minor update that shouldn't break any DOOMModLoader-based mods. The bad news is, you can no longer launch the game EXE directly (meaning that **you must manually launch the game through Steam after using DOOMModLoader**), and it breaks DoomLegacyMod (causing the game to instantly close), SnapHak (its *XINPUT1_3.dll* file doesn't work (nor cause problems), but it includes DoomLegacyMod's *d8input.dll* file), and DOOMLauncher (which relied on launching the game EXE directly).
**If you have installed DoomLegacyMod or SnapHak for DOOM (2016), you must delete *-/steamapps/common/DOOM/dinput8.dll* before you can launch the game!**
Ur mod interrupting Rune Trial #3 Where u need to kill 30 mobs with Super Shotgun. There is a problem with respawning enemies.After uninstalling all files everything working fine.
Ur mod interrupting Rune Trial #3 Where u need to kill 30 mobs with Super Shotgun. There is a problem with respawning enemies.After uninstalling all files everything working fine.
In Doom Eternal's KTD comment section, creator discusses the variable length of time dead can be kept around. He says if you keep too many dead around for too long, it blocks new spawns from occuring. He says 1-minute is the generally optimal length of dead-decay time, but it's dependent on the player's ability, where skilled players can get spawn-blocked with even just a +10-20 second dead-delay length.
So given there's an objective contingent on a number of spawn here, I'm betting this mod's dead-decay length variable is breaking the necessary amount of objective spawns from happening. Try lowering KTD's dead-decay rate variable down to see if this trial becomes beatable.
Figured it out. The "candidade.cfg" is executing the "KTD2016.cfg" In the KTD2016.cfg file, I changed the value of "ai_death_FadeDelay" from 6000 to 1
As expected, the main corpse (not the gory bits, those seem to operate on different values) disappeared immediately, and the last 4 demons finally spawned.
This is a quick fix, but I do still wish it was possible, maybe for the rune trials, to change values according to what's required, that'd be neat.
Virustotal doesn't like the Discord hosted file (https://cdn.discordapp.com/attachments/696423960169939054/871140270996082698/DOOMLauncher.zip) https://www.virustotal.com/gui/file/8ca2f5c0768b6632eedcdd1dce6ddda5da90b2c93fcf906bbe3ad1e1bfa7cb85 I have seen false positives before but not as many as with this one. Usually the false positive pings in couple of different places and it's pretty easy to see it's a false positive. Not with this file.
The official github one (https://github.com/jfmherokiller/DOOMExtract/releases/tag/1.8) https://www.virustotal.com/gui/file/b84aa85b296b5c1f76f10a36d43ff3d7164e102201104b80fc4bb53bacbaaf95 Even though this is the same file, same mechanics it's completely clean.
I would honestly stay away from the Discord hosted file and the mod creator should be reported. Altough the mod itself is not malicious, he is touting a link which seem to contain compromised software.
I have just this and no other mods. Gives the following console output. Quick googling suggests it maybe something about regional settings but idk.
DOOMModLoader 0.2 by infogram - https://github.com/emoose/DOOMExtract
Extracting/copying mods into C:\Users\name\AppData\Local\Temp\tmpFAD3.tmp Extracting Keep The Dead v1.3.zip
Unhandled Exception: System.ArgumentException: 1 is not a supported code page. Parameter name: codepage at System.Text.Encoding.GetEncoding(Int32 codepage) at ICSharpCode.SharpZipLib.Zip.ZipFile.ReadEntries() at ICSharpCode.SharpZipLib.Zip.ZipFile..ctor(FileStream file) at DOOMModLoader.Program.ExtractZipFile(String archiveFilenameIn, String password, String outFolder) at DOOMModLoader.Program.Main(String[] args)
I seem to be having trouble getting this to work.. when I try to run DOOMModLoader.exe, it gives an error message saying that there is an unhandled exception, and that it cannot locate the necessary files at systems.diagnostics.*. Do you have an idea of how I might be able to fix this? Thank you for any help.
Give Feedback
124 comments
Only way to get this mod to work at this point is to down patch Doom to the previous version.
Ill look into remaking this mod in the way my Doom Eternal version is made but Im unsure if thats possible atm.
Ive updated the link on the main page to the latest Doom Mod Launcher however with the current version of the game; it wont launch the game automatically.
See below note from Modding Discord:
**DOOM (2016) has been updated.**
The good news is, it's a very minor update that shouldn't break any DOOMModLoader-based mods. The bad news is, you can no longer launch the game EXE directly (meaning that **you must manually launch the game through Steam after using DOOMModLoader**), and it breaks DoomLegacyMod (causing the game to instantly close), SnapHak (its *XINPUT1_3.dll* file doesn't work (nor cause problems), but it includes DoomLegacyMod's *d8input.dll* file), and DOOMLauncher (which relied on launching the game EXE directly).
**If you have installed DoomLegacyMod or SnapHak for DOOM (2016), you must delete *-/steamapps/common/DOOM/dinput8.dll* before you can launch the game!**
Edit: Reverting candidate.cfg back to the default fixed it. Seems that something in KTD2016.cfg is causing the bug.
So given there's an objective contingent on a number of spawn here, I'm betting this mod's dead-decay length variable is breaking the necessary amount of objective spawns from happening. Try lowering KTD's dead-decay rate variable down to see if this trial becomes beatable.
In the KTD2016.cfg file, I changed the value of "ai_death_FadeDelay" from 6000 to 1
As expected, the main corpse (not the gory bits, those seem to operate on different values) disappeared immediately, and the last 4 demons finally spawned.
This is a quick fix, but I do still wish it was possible, maybe for the rune trials, to change values according to what's required, that'd be neat.
https://www.virustotal.com/gui/file/8ca2f5c0768b6632eedcdd1dce6ddda5da90b2c93fcf906bbe3ad1e1bfa7cb85
I have seen false positives before but not as many as with this one. Usually the false positive pings in couple of different places and it's pretty easy to see it's a false positive. Not with this file.
The official github one (https://github.com/jfmherokiller/DOOMExtract/releases/tag/1.8)
https://www.virustotal.com/gui/file/b84aa85b296b5c1f76f10a36d43ff3d7164e102201104b80fc4bb53bacbaaf95
Even though this is the same file, same mechanics it's completely clean.
I would honestly stay away from the Discord hosted file and the mod creator should be reported. Altough the mod itself is not malicious, he is touting a link which seem to contain compromised software.
DOOMModLoader 0.2 by infogram - https://github.com/emoose/DOOMExtract
Extracting/copying mods into C:\Users\name\AppData\Local\Temp\tmpFAD3.tmp
Extracting Keep The Dead v1.3.zip
Unhandled Exception: System.ArgumentException: 1 is not a supported code page.
Parameter name: codepage
at System.Text.Encoding.GetEncoding(Int32 codepage)
at ICSharpCode.SharpZipLib.Zip.ZipFile.ReadEntries()
at ICSharpCode.SharpZipLib.Zip.ZipFile..ctor(FileStream file)
at DOOMModLoader.Program.ExtractZipFile(String archiveFilenameIn, String password, String outFolder)
at DOOMModLoader.Program.Main(String[] args)