Doom Mod Loader - v2.5 Gold [Windows]

Please read this whole page before downloading. Also take a look to the readme bundled with the software.
This is the download for the Windows version, if you're on Linux/Mac OS, please follow the instructions for the mono version here https://github.com/Premo36/DML2.X/releases/tag/v2.5-mono

Note: This is temporarly in "pre-release" state until I'm sure it does not have any bug and I can publish it on moddb and rollout the update notification via the internal update system. For now the internal updater notification will prompt you to install the old 2.4 version, so just ignore it for the next few days.

Before I start this text-wall, I want to stop for a second and thank eviltechno on moddb, as most of the new features have been developed starting from some of his suggestions, as v2.5 initially started only as a port for Linux.

This version as been tested only on Windows 10 (21H2) but it should run without any issue also on older windows version like 8.1 or 7 (If fully up-to-date). It may work also on XP, but it's never been tested under that OS.
Needs .net framework version 3.5 to work. If you don't have it installed or unsure about it, be sure to be connected to the internet the first time you open DML 2.X so that if it's missing, Windows can ask if you want to install it. On 7/8.1/10 it's an automated process, basically you just need to click ok/yes when prompted. On XP you may need to install net framework 3.5 manually, as DML 2.X will just crash on launch if the needed net framework it's missing. Again remember that it was never tested on XP. Take a look to the readme .txt bundled with the download for more info.

As always, make a backup of your CONFIG folder before updating! So if anything goes wrong you don't have to remade everything from scratch!

You may need to update your preset to store the new gzdoom way to set the rendering. If unsure on what those setting means or you're using an older gzdoom version that still use the old system, select "SDL + OPENGL | OPENGL" and "HARDWARE ACCELERETED (OPENGL)" or "DOOM SOFTWARE RENDERER". Take a look to the zdoom wiki for more info https://zdoom.org/wiki/CVARs:Display#vid_preferbackend

Changelog v2.4 => v2.5

NEW FEATURES:

• Now it works under Linux/Mac through mono (Be sure to have downloaded the mono version, the one with "mono" in the exe name, and follow the instructions otherwise it will not work! The page you are reading it's for the windows one that will NOT work in any way under Linux/Mac) (#12)
• 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".
• 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. (Windows/Linux only) (#14) .
• In the mod order window, the selected mod can now be pushed directly to the top/bottom of the list also by using pageUP/pageDOWN (#19).
• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

BUGFIXES:

• Fixed bug where the DMLv2.ini will store the whole path of the alternative sourceport configuration file instead of just the name, making DML 2.X not fully portable (#9) .
• Fixed bug where the "please insert a preset name" error message had of a information icon instead of an error one (#18).
• Fixed bug where the mods list extension filter only showed matching file that had a lowercase extension. Now it shows all matches (#24).

NEW SETTINGS:

• RENDERER2
• FILE_ORDER_BY
• PRESET_ORDER
• GZDOOM_QUICKSAVE_FIX
• AUTOLOAD_PRESET

As for this version, the only tested sourceport are:
(Remember that as long as it follows the zdoom command line standard, any engine will work fine)

FULL COMPATIBILITY:

• GZdoom (v4.7.1), -height and -width do not work due to gzdoom way of handling resolution)
• LZdoom (v3.87c)
• Zandronum (3.1)
• Zdoom(2.8.1)
• QZDoom (2.1.0)
• Skulltag(98d)

PARTIAL COMPATIBILITY (Some DML features will not work):

• Chocolate Doom (3.0.1)
• PrBoom+ (2.6.2)

Note: Some antivirus on virustotal (and maybe locally) flag it as malicious. I've tried to report this issue to both virustotal and the AV companies, but in the end I've just wasted time getting either ghosted or getting conflicting information where Virustotal says they can't do anything and that I should have contacted the AV company while the AV company says they can't do anything and that I've should have contacted virustotal... So if your AV flag it as malicious either whitelist it if you trust me, report it yourself to your AV company or take a look to the sourcecode and compile it yourself (The "master" brench is for Windows, the "mono" brench is for Linux/MacOS).

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.

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 *Here your OS* 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]

DONATE

If you like my work and you would like to support me, you can send monero to this address:

83XoYbCK9bZLF93kvY3RVHfWRtnLZAjLELUCP1foBMqoRi6zKF8NKXzTH2CobxvoZyREPcfgb6WwVaAu36iZDM72PYh2TCM

NOTE: Donation will NEVER be required, but are more than welcome ;) Don't worry if you can't/don't want to donate as it will not change the way I work. I would not make my software open source if I just wanted to profit from it.

CONTACTS

If you're interested in my softwares, games, open source projects or just want to contact me, you can find me here:
🔗 Website: https://p36software.net
✉ Support e-mail: [email protected] (for reporting bug/give feedback/ask for help)
✉ Info e-mail: [email protected] (for anything else)
🐦 Twitter: https://twitter.com/p36software (@p36software, gets updated more often)
📄 Github: https://github.com/Premo36
🔧 ModDB: https://www.moddb.com/members/premo36
🎮 IndieDB: https://www.indiedb.com/members/premo36
🎥 Youtube: https://www.youtube.com/channel/UC9yqO2r6CJeLcKebDr142eA

Doom Mod Loader - v2.5 Gold [Linux/MacOS through mono]

Please read this whole page before downloading. Also take a look to the readme bundled with the software.
This is the download for the mono version, that is intended to be used on Linux/Mac.
If you're on Windows, please download the windows version here https://github.com/Premo36/DML2.X/releases/tag/v2.5-windows

Before I start this text-wall, I want to stop for a second and thank eviltechno on moddb, as most of the new features have been developed starting from some of his suggestions, as v2.5 initially started only as a port for Linux.

What is mono and how to use DML 2.X on Linux/MacOS

Mono it's an open source implementation of Microsoft's .NET Framework. In order to use DML 2.X in Linux/Mac Os, you need to download and install the latest stable `mono-complete` for your operating system following the instruction on the official mono project website.

https://www.mono-project.com/download/stable/

If you're on a Linux based OS:

You may have the mono-complete package available on your distro repos, but it's usually an older version so it's better that you still follow the instructions from the mono project website and install it that way.
Note that the mono version as been tested only Linux Mint 20.3 and Debian 11. It should work fine on any debian based OS.
For Ubuntu/Ubuntu-based distro (like Linux Mint) follow the Ubuntu instructions.
For Debian/Debian-based distro (that are not Ubuntu/Ubuntu-based) follow the Debian instructions.
For CentOS, Red Hat Entriprise Linux or distro based on those, follow the CentOS/RHES instructions (note that DML 2.5 mono as NEVER been tested under those OS).
For Fedora/Fedora-based distro, you've guessed right! Follow the Fedora instructions. (note that DML 2.5 mono as NEVER been tested under Fedora).
For Arch/Arch-based system, like Manjaro etc... the official mono project does not have official packages for those distro. You may find something on your distro repos (note that DML 2.5 mono as NEVER been tested under Arch).

If you're on a Mac OS system:

the "mono-complete" package should be the only avaiable download for that platform. I call it "mono-complete" because on Linux it's modular. While DML 2.X under mono should work as well as on Linux, I couldn't test it myself as I don't own a mac. It's even more "as is" under that OS. I've never even had the possibility too boot it up on a Mac, let alone fix bugs. Also note that at 99.9% the 'Bind [KEY] "save quicksave.zds"' workaround will NOT work on Mac OS.

How to launch DML 2.X after mono is installed:

Once `mono-complete` is installed, you should be able to open DML 2.X by simply double-clicking on the `.exe` . If that does not work you may open it trough your system terminal by navigating to the folder where the DML 2.X it's located, writing `mono "DML v2.5 [Mono].exe"` (you have to write the precise, full `.exe` name, writing "mono DML" and then pressing tab should autocomplete to the correct name) and pressing "enter" on your keyboard.

This version of DML 2.X is a slighted different version from the windows one: All the core functionality works and, as a plus,it follows the user dark/light theme (On Linux at least), but it may have some minor graphical issues and the "check for update" functionality has been disabled as it would just crash DML 2.X, and I didn't bother find a solution as this version should be the last of the 2.X era (excluding an eventual bugfix release of course)

On Linux, to quickly found where a sourceport is installed (assuming you've installed trough your package manager) you can write in the console whereis gzdoom (where gzdoom is your sourceport name), which will output the path to the executable.

NOTE: The mono version may be less stable then the Windows one and if you use it on Mac OS keep in mind I've NEVER tested DML 2.X under Mac OS, as I don't own a mac.

You may need to update your preset to store the new gzdoom way to set the rendering. If unsure on what those settings means or you're using an older gzdoom version that still use the old system, select "SDL + OPENGL | OPENGL" and "HARDWARE ACCELERETED (OPENGL)" or "DOOM SOFTWARE RENDERER". Take a look to the zdoom wiki for more info https://zdoom.org/wiki/CVARs:Display#vid_preferbackend

Changelog v2.4 => v2.5 Mono

NEW FEATURES:

• Now it works under Linux/Mac trough mono (Be sure to have downloaded the mono version, the one with "mono" in the exe name, and follow the instructions otherwise it will not work!) (#12)
• 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".
• 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. (Windows/Linux only) (#14) .
• In the mod order window, the selected mod can now be pushed directly to the top/bottom of the list also by using pageUP/pageDOWN (#19).
• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

BUGFIXES:

• Fixed bug where the DMLv2.ini will store the whole path of the alternative sourceport configuration file instead of just the name, making DML 2.X not fully portable (#9) .
• Fixed bug where the "please insert a preset name" error message had of a information icon instead of an error one (#18).
• Fixed bug where the mods list extension filter only showed matching file that had a lowercase extension. Now it shows all matches (#24).

NEW SETTINGS:

• RENDERER2
• FILE_ORDER_BY
• PRESET_ORDER
• GZDOOM_QUICKSAVE_FIX
• AUTOLOAD_PRESET

As for this version, the only tested sourceport are:
(Remember that as long as it follows the zdoom command line standard, any engine will work fine)

FULL COMPATIBILITY:

• GZdoom (v4.7.1), -height and -width do not work due to gzdoom way of handling resolution)
• LZdoom (v3.87c)
• Zandronum (3.1)
• Zdoom(2.8.1)
• QZDoom (2.1.0)
• Skulltag(98d)

PARTIAL COMPATIBILITY (Some DML features will not work):

• Chocolate Doom (3.0.1)
• PrBoom+ (2.6.2)

Note: The workaround that make the custom saving method 'bind [KEY] "save quicksave.zds"' work, right now only works on WIndows/Linux (tested on recent gzdoom/zandronum version installed trough apt) , if you're on Mac OS the workaround will not work.

Note: Some antivirus on virustotal (and maybe locally) flag it as malicious. I've tried to report this issue to both virustotal and the AV companies, but in the end I've just wasted time getting either ghosted or getting conflicting information where Virustotal says they can't do anything and that I should have contacted the AV company while the AV company says they can't do anything and that I've should have contacted virustotal... So if your AV flag it as malicious either whitelist it if you trust me, report it yourself to your AV company or take a look to the sourcecode and compile it yourself (The "master" brench is for Windows, the "mono" brench is for Linux/MacOS).

Note: I flagged it as a pre-release on github even if it's not (this mono version it's the one that I personally use since I switched to Linux last year) to make clear that this version need a bit of extra work in order to run and to avoid "hiding" the Windows version. And also because on Mac OS it's literally untested.

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.

Note: If you've used the Windows version before, you can move your existng CONFIG and FILE folder to Linux and they will work out of the box if you were on v2.2 or newer (Except the sourceports, you'll need to install the Linux version). If you are on a older version you'll need to follow the update procedure on a Windows machine until you reach the v2.2. The same process should apply to Mac OS, but once again, I could ever test it on a mac os device.

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 pleas...

v2.5-beta7-mono[Linux+MacOS]

Please read this whole page before downloading. This is the download for the mono version, that is intended to be used on Linux/Mac.
If you're on Windows, please download the windows version here https://github.com/Premo36/DML2.X/releases/tag/v2.5-beta7

What is mono

It's an open source implementation of Microsoft's .NET Framework. Long story short, given that your C# application is not too much complex, you can make it work under mono in fairly low amount of time, and this will allow your Windows .net application to run under any OS where the mono runtime can be installed. Tought I would NOT recommend it for new project, due to how old and limited the project technology is (it do not work with WPF or really anything newer then winform...) and by how scarce and outdated the documentation is.

What do I need to use this DML 2.X version?

NOTE: If your are on Windows, this version is NOT for you!
You need to download and install the stable `mono-complete` for your operating system following the instruction on the official mono project website .
If you're on a Linux based OS, you may have the mono-complete package available on your distro repos, but it's usually an older version so it's better that you still follow the instruction from the mono project website and install it that way.
If you're on a Mac OS system, while DML 2.X under mono should work as well as on Linux, I couldn't test it myself as I don't own a mac.
Once `mono-complete` is installed, you should be able to open DML 2.X by simply double-clicking on the `.exe`. If that does not work you may open it trough the console by navigating to the folder where the DML 2.X it's located, writing `mono "DML v2.5 mono.exe"` (note that the .exe name will be different during the beta, you have to write the precise, full `.exe` name, writing "mono DML" and then pressing tab should autocomplete to the correct name) and pressing "enter" on your keyboard.
This version of mono is a modified version from the windows one, all the core functionality works and, as a plus,it follows the user dark/light theme (On Linux at least), but it may have some minor graphical issue and the check for update as been disabled as it would crash DML 2.X.
On Linux, to quickly found where a sourceport is installed (assuming you've installed trough your package manager) you can write in the console `whereis gzdoom` (where gzdoom is your sourceport name), which will output the path to the executable.

Changelog v2.5 Beta N° 6 Mono => v2.5 Beta N°7 Mono

• Fixed bug where the workaround for 'bind [KEY] "save quicksave.zds" ' did not work under Linux(#22 ).
• Fixed bug where the autoload selection was resetted to "-" each time a preset was deleted (#23 ).
• Changed "Autoload preset" label to just "Autoload"

Note: The workaround that make the custom saving method 'bind [KEY] "save quicksave.zds"' work, right now only works on WIndows/Linux (tested on recent gzdoom/zandronum version installed trough apt) , if you're on Mac OS the workaround will not work.

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

• Now it works under Linux/Mac trough mono!
• 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).
• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload preset" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

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 this new beta is so much beta that I may call it even an alpha!
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?

Starting from beta N°7 the updated (but still wip) readme is included. It should include every new feature. If something it's missing or not clear, feel free to contact me!

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 7 Mono *Here your OS* 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]

v2.5-beta7[Windows]

Please read this whole page before downloading, or at least the "WARNING: This is a beta release" section.
If you're on Linux/Mac OS, please download the mono version here https://github.com/Premo36/DML2.X/releases/tag/v2.5-beta7-mono

Changelog v2.5 Beta N° 6 => v2.5 Beta N°7

• Fixed bug where the autoload selection was resetted to "-" each time a preset was deleted (#23 ).
• Changed "Autoload preset" label to just "Autoload"

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

• 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).
• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload preset" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

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...
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?

Starting from beta N°7 the updated (but still wip) readme is included. It should include every new feature. If something it's missing or not clear, feel free to contact me!

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 7 *Here your OS* 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]

v2.5-beta6-mono[Linux+MacOS]

Please read this whole page before downloading. This is the download for the mono version, that is intended to be used on Linux/Mac.
If you're on Windows, please download the windows version here https://github.com/Premo36/DML2.X/releases/tag/v2.5-beta6

What is mono

It's an open source implementation of Microsoft's .NET Framework. Long story short, given that your C# application is not too much complex, you can make it work under mono in fairly low amount of time, and this will allow your Windows .net application to run under any OS where the mono runtime can be installed. Tought I would NOT recommend it for new project, due to how old and limited the project technology is (it do not work with WPF or really anything newer then winform...) and by how scarce and outdated the documentation is.

What do I need to use this DML 2.X version?

NOTE: If your are on Windows, this version is NOT for you!
You need to download and install the stable `mono-complete` for your operating system following the instruction on the official mono project website .
If you're on a Linux based OS, you may have the mono-complete package available on your distro repos, but it's usually an older version so it's better that you still follow the instruction from the mono project website and install it that way.
If you're on a Mac OS system, while DML 2.X under mono should work as well as on Linux, I couldn't test it myself as I don't own a mac.
Once `mono-complete` is installed, you should be able to open DML 2.X by simply double-clicking on the `.exe`. If that does not work you may open it trough the console by navigating to the folder where the DML 2.X it's located, writing `mono "DML v2.5 mono.exe"` (note that the .exe name will be different during the beta, you have to write the precise, full `.exe` name, writing "mono DML" and then pressing tab should autocomplete to the correct name) and pressing "enter" on your keyboard.
This version of mono is a modified version from the windows one, all the core functionality works and, as a plus,it follows the user dark/light theme (On Linux at least), but it may have some minor graphical issue and the check for update as been disabled as it would crash DML 2.X.
On Linux, to quickly found where a sourceport is installed (assuming you've installed trough your package manager) you can write in the console `whereis gzdoom` (where gzdoom is your sourceport name), which will output the path to the executable.

Changelog v2.5 Beta N° 5 Mono => v2.5 Beta N°6 Mono

• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload preset" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

Note: The workaround that make the custom saving method 'bind [KEY] "save quicksave.zds"' work, right now only works on WIndows , if you're on linux you'll have to move the file manually from your home folder to the gzdoom folder in .config (see #22 for more info), or just use the built-in quicksave feature.

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

• Now it works under Linux/Mac trough mono!
• 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).
• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload preset" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

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 this new beta is so much beta that I may call it even an alpha!
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. Also you can take a look to the (as now W.I.P.) 2.5 readme in this repository.

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 6 Mono *Here your OS* 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]

v2.5-beta6[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...

If you're on Linux/Mac OS, please follow the instruction here https://github.com/Premo36/DML2.X/releases/tag/v2.5-beta6-mono

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

• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload preset" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

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

• 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).
• Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload preset" combobox in the "Game" section of DML 2.X (#20).
• Updated the renderer selection in order to work with the newest gzdoom releases(#21).
• Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

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... cause the next Hell on Earth (didn't I made this joke already?)
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 6 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]

v2.5-beta5-mono[Linux+MacOS]

Please read this whole page before downloading. This is the download for the mono version, that is intended to be used on Linux/Mac.

What is mono

It's an open source implementation of Microsoft's .NET Framework. Long story short, given that your C# application is not too much complex, you can make it work under mono in fairly low amount of time, and this will allow your Windows .net application to run under any OS where the mono runtime can be installed. Tought I would NOT reccomand it for new project, due to how old and limited the project technology is (it do not work with WPF or really anything newer then winform...) and by how scarce and outdated the documentation is.

What do I need to use this DML 2.X version?

NOTE: If your are on Windows, this version is NOT for you!
You need to download and install the stable `mono-complete` for your operating system following the instruction on the official mono project website .
If you're on a Linux based OS, you may have the mono-complete package available on your distro repos, but it's usually an older version so it's better that you still follow the instruction from the mono project website and install it that way.
If you're on a Mac OS system, while DML 2.X under mono should work as well as on Linux, I couldn't test it myself as I don't own a mac.
Once `mono-complete` is installed, you should be able to open DML 2.X by simply double-clicking on the `.exe`. If that does not work you may open it trough the console by navigating to the folder where the DML 2.X it's located, writing `mono "DML v2.5 mono.exe"` (note that the .exe name will be different during the beta, you have to write the precise, full `.exe` name, writing "mono DML" and then pressing tab should autocomplete to the correct name) and pressing "enter" on your keyboard.
This version of mono is a modified version from the windows one, all the core functionality works and, as a plus,it follows the user dark/light theme (On Linux at least), but it may have some minor graphical issue and the check for update as been disabled as it would crash DML 2.X.
On Linux, to quickly found where a sourceport is installed (assuming you've installed trough your package manager) you can write in the console `whereis gzdoom` (where gzdoom is your sourceport name), which will output the path to the executable.

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

• Now it works under Linux/Mac trough mono!
• 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 this new beta is so much beta that I may call it even an alpha!
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 Mono *Here your OS* 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]

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]

v2.5-beta4

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°3 => v2.5 Beta N°4

• 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) .

In order to make the 'BIND F6 "save QUICKSAVE.ZDS" '-thing work:
1)Go into the DML 2.x preferences and enable "Workaround for 'BIND F6 "save QUICKSAVE.ZDS" '".
2)Every time you boot up gzdoom and wish to have a working quicksave, load your quicksave trough the "load" menu.
3)Right after it loads your quicksave, press right away "F6" (Or whatever key you've binded) in order to make a quicksave.

With the workaround you will have 2 quicksave.zds, the "current" one in the dml 2.X and the "old" one in the gzdoom "Save".
The "current" one is the one thats gets updated each time you save for the current gzdoom session, the "old" one gets replaced with the "current" one once you close gzdoom.
This way the next time you open gzdoom your last quicksave will be available.
If you don't quicksave after loading, and you try to quickload, gzdoom will now always quickload from the "old" quicksave until you close it.
Note that this as the name suggest, it's a workaround for something happening on the gzdoom side and in which I have zero control, it works for now but it may break with future gzdoom updates.

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

• 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) .

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 r̴͇̘̩̰̐ě̵̗̲̳d̴͉̥͚̥͇̃̿̾̄͝a̴̮͐̋̎̑̾ć̴̟̌̾̉ṯ̶̦͗̃́̀͝ę̸̱̲̉͝d̸̫̟̱̀͒̉͜͝
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 4 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]

v2.5-beta3

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°2 => v2.5 Beta N°3

• 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).

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

• 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).

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 [I've already run out of jokes to put here. Remember to D R I N K W A T E R].
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 3 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]