Doom Mod Loader 2.1 (Old) file

Doom Mod Loader is a Doom (but NOT ONLY, here's the full list of compatible games) launcher for Windows (8.1 & 10) that allow you to easily load your game with your favourite mods and also:

• Works with most of modern doom sourceport (like zdoom, skulltag, gzdoom***, zandronum** etc... see below the tested ones)
• Saves groups of mod you want to play togheter in presets.
• Writes engine console parameters* for you (Or even add other ones if you know them!)
• Change mod loading order, so you can load different mods without let them replace each other stuff without control.
• Change launching options such as the starting level, the skill level, chose if play with faster monster, let them respawn (like in NIGHTMARE! difficulty) or just remove them.
• Change the video renderer mode.
• Use an alternative sourceport .ini file without the need of swapping them manually.

"DML_2.1.zip" (the downloadable file) contains 4 file:

1. DML v2.1.exe, it's the main executable, run this.
2. P36_UTILITIES.dll, it's a library that I've written which contain some generic code for read/write data, must be kept in the same folder as the executable.
3. README.txt, it's the readme file, that provided some information, a few quick "HOW-TO" guide and the changelog of the current version. Please read it.
4. DMLfilePatcher.exe, use it in order to patch 2.0/2.1 preset, do NOT run it more than once, as i can't tell the version of the preset, patching a new or already patched preset will make it unreadable for any dml version. Once used can be deleted, if this is the first time you use DML you can delete it right away.Read the "WHY THE PRESETS I'VE MADE WITH DML 2.0/2.0b ARE NO LONGER READ?" section of the readme for more info.

DML do not need installation, it's a semi-portable software ("semi" as all the preference, wad location ecc.. are stored in %appdata%/P36_Software/DML2/).

New features:

• Presets now keep also the load order (2.0/2.0b presets need to be patched trough the included patching utility to become compatible again with this new version)
• Presets can now store also the IWAD to run it.
• Now you can add folders (and subfolders) trough the new "File Manager" window. DML will scan for any compatible file in the directory. Single file are still supported.
• Added "reload resources" button, that will reload all resources used by dml (useful if you add mods to a folders while dml is running)
• Mods files (and folders) can be added by drag and drop in the new "File Manager" window.
• Added "all files" to filter list of the "add single file\s" window dialog. It's the default filter and include any compatible file. Filtering for single extension is still supported.
• Added the "[DON'T OVERRIDE]" option to the renderer list. This option will not force any renderer so the engine will keep using the current one.
• Added a "preferences" window, that will let you enable/disable the doom-like quit confirmation messages, the preset overwrite warning message, the delete/remove warning message and the succeded preset saving message.
• Now if you are just updating a preset (changing the order of files), if you click save the "overwrite" message will no longer show. It will show only if you're saving a new file or performing a "save as..." like action (by changing the name), and only if you don't disable the overwrite message within the preferences window.
• The current software version will show up at the top of every window.
• Added a horizontal scroll bar in the mod selection list, so mod with long name will not be cutted anymore.

Bugfixes

• Fixed bug where if you launched a second time from the mod load order window your sourceport without closing the window first, the "-file" parameters from the previous launch will not be cleaned. This was causing slower loads time and possible mod loading error.

Known bug:

• GZdoom "Quicksave.sav" files gets saved in the same directory as the dml2.1 executable instead on the gzdoom one.
• "-width" and "-height" do not work in any recent gzdoom version.
  This is a known issue thats been around since gzdoom changed the way the resolution is handled.
  This afflict any DML version, since the change has been made from the gzdoom side.
  Initially i was going to use "+win_w" and "+win_h" instead,
  but I soon scrapped the idea because this command will also change the stored the resolution in the gzdoom .ini,
  making the change permanent, so even if you removed the values from dml it will keep starting at that resolution.
  You can still change that way by writing it manually in the "Custom command line parameters" text area. Example: "+ win_w 1280 +win_h 720".

New settings (if you see a message the first time you run the new version with the following list, you can just dismiss it):

• LOAD_SUBFOLDERS
• SHOW_END_MESSAGE
• SHOW_DELETE_MESSAGE
• SHOW_OVERWRITE_MESSAGE
• SHOW_SUCCESS_MESSAGE
• USE_ADVANCED_SELECTION_MODE

(This is only the latest version changelog, you can find the full DML version history here)

• GZdoom (4-2-0, -height and -width do not work due to gzdoom way of handling resolution)
• LZdoom (3.82)
• Zandronum (3.0)
• Zdoom(2.8.1)
• QZDoom (2.1.0)
• Skulltag(98d)
• Chocholate Doom (3.0.0, really BASIC compability, most of the DML features don't work)

NOTE: Need Microsoft .Net Framework 3.5 to work. If your system is up to date you should have it arleady. Keep the doom mod loader .exe and "P36_UTILITIES.dll" in the same folder, otherwise it will not work.

* DML is more like a "modern sourceport launcher", that writes the engine console parameters for you, that means you STILL NEED a modern doom port to load your mod. I've tested so far the ones i've wrote, but as far a port use the console parameters linked above it will work fine!

** On Zandronum the "Disable SFX" (-nosfx) seems to do disable all sounds instead of disable only the sfx. Don't know why.

*** On GZDoom, -height and -width do not work anymore, due to the changes they did to the code that handles the resolution. This afflict any DML version. See the DML 2.0 changelog above for more info, I also mention a possible workaround for this issue.

Contacts:

• E-mail: p36software@mail.com
• Author personal twitter: @premo36