v2.5-beta5[Windows]

Please read this whole page before downloading, or if you're in an extra super duper hurry, read at least the "WARNING: This is a beta release" section...

Changelog v2.5 Beta N°4 => v2.5 Beta N°5

• The selected mod can now be pushed directly to the top/bottom of the list in the mod order window also by using pageUP/pageDOWN (#19).

Changelog v2.4 => v2.5 Beta N°5

• The preset name it's now fully visible while browsing the preset list, no matter how long the preset is (#13).
• Mods list "Order By" value it's now kept between application launches (#8).
• Preset order can now be changed via the software settings. Possible order are "Alphabetical - Ascending", "Alphabetical - Descending" , "Date - Ascending" and "Date - Descending" (#11).
• Mods list can now also be ordered by "Date - Ascending" and "Date - Descending".
• In order to make DML 2.X more portable, the DMLv2.ini now store just the name and not the whole path of the alternative sourceport configuration file (#9) .
• The "please insert a preset name" error message as now an error icon instead of a information one (#18).
• Added a workaround that mitigate the gzdoom bug where quicksave made with 'BIND [KEY] "SAVE QUICKSAVE.ZDS"' are saved in the wrong folder. Can be enabled in DML 2.X preferences. (#14) .
• The selected mod can now be pushed directly to the top/bottom of the list in the mod order window also by using pageUP/pageDOWN (#19).

WARNING: This is a beta release

Please keep in mind that this release is to be considered as a beta software, because I still haven't fully tested it yet. It may be unstable, crash, become sentient etc... so use with at your discretion... as you may... well just take a look here...
While using any release of DML 2.X tagged as "beta", ignore the "new version" notification, as those are linked to the official stable releases, not with the beta ones.
As any release I made of this software, this one also gets detected as "Malicius" on virus total by Malwarebytes (+ some other AVs). As they never really fix the detection but usually just whitelist the single exe, everytime I made a new version I have to go again trough the process of contacting each antivirus and report my software as a false positive. Now I've stopped doing that for beta releases, so be advised that your antivirus may report it as a threat: it's not. But you don't have to belive me, as "don't worry, it's safe " it's exactly what a malicius developer will say about his not-so-safe software, so feel free to take a look to the sourcecode and compile it yourself if you wish.

How to update from an older DML version

• DML v2.2 (or newer): You can just replace the old .exe with the new one keeping all your configuration files, and it should work right away, but just to be extra safe, go ahead and make a backup before updating, so if it messes up your presets or configuration files you can restore them without the need of re-configure everything from scratch. If you still have the "P36_UTILITIES.dll" you can safely delete it as it's no longer used since v2.2b.
• DML v2.1: Move all the contents of %AppData%\Roaming\P36_Software\DMLv2\ inside the CONFIG folder next to dml exe, then follow the v2.2 (or newer) instructions.
• DML v2.0/v2.0b: You have to first download the 2.1 version, go trough the presets update procedure (explained in the 2.1 readme) and then follow the v2.1 instructions.
• DML v1.0/v1.1: There is no way to update from 1.X to 2.X, you will have to recreate your presets from scratch.

Where is the README v2.5.txt?

Beta version prior to the release candidate usually comes without a readme file, as usually it's the last thing I update, if you need a readme, the 2.4 readme it's still valid for most of the software.

I've found a bug/something is not working right/I have a suggestion/I want to contact you

If you find any bug with this version please report it trough github (if you're familiar with it), or by sending an email at [email protected] with subject "DML 2.5 Beta 5 Bug - *Here describe the bug in a few words*" and in the mail itself try to explain with much accuracy and details as possible what happened, what did you expect it should have happened and a step by step guide on how to reproduce it, as if I can't reproduce it on my end, I can't fix it.

If you just want to contact me you can get in touch via email: [email protected]