Why the hell another launcher?
The motivation was rather personal. I simply didn't like any of the existing ones.
ZDL is fine, but it's too minimalistic for me, it can't do much, and some tasks become very repetitive and annoying. And it's also becomming pretty dated, and looks like from Win98.
Rocket Launcher is nice, and with its support for all the various Doom engines still has a strong place in Doom community. However the UI feels rather weird and confusing,
especially in that area of saving&loading configurations which is important for me.
I also tried ZDoom Executor. The idea about presets is awesome, but the execution is weird too, to this day i still haven't figured out how to use the tabs properly, not very
intuitive. Plus there is only limited number of them and they are named only by fixed numbers.
And finally i wanted to improve my C++ skills and learn some GUI programming, and this seemed like a perfect opportunity.
First i wanted to keep it only for myself, because everyone else seemed to be satisfied with ZDL, but then i thought: Why not, maybe somebody will find it useful.
So there goes the Doom Runner - a modern Qt-based preset-oriented launcher, designed around the idea of one-click switching between multi-file modifications (Brutal Doom
with mutators, Project Brutality with UDV, Complex Doom Clusterfuck, ...) to minimize any repetitive work.
- unlimited number of named presets with single-click switching
- lists of IWADs and Map packs automatically synchronized with the content of a selected directory
- drag&drop of files from a directory window to the mod list
- internal drag&drop for reordering the files to load
- direct map launch and multiplayer options
- DM flags and Compatibility flags calculator with tooltips from official ZDoom wiki
- preview of the final launch command with the option to export it to .bat/.sh shell script
- runs on Windows and Linux (only 64bit because it's 2020)
- no stupid .NET or JRE required
1.1 is released for Windows and Linux (both 64-bit). It should be stable by now, although there are some known issues. I'm still open to suggestions any day. You can either write it here on forum or create an issue on Github. You can also write me an email to email@example.com or contact me on Discord as Youda#0008, but i preffer the Github options, so that your suggestions stay public and can be discussed by other users and also so that every issue has its own thread.
1.2 is released.
- reworked map-packs widget from list view to tree view to show a directory hierarchy
- removed "Current preset" mechanic and replaced it by disabling sub-windows to prevent user making changes that are not saved anywhere
- selected map file is now saved on quit and restored on next start
- added an "About" dialog with information about the application
1.3 is released.
- For each engine you can now set custom directory of config files (required for using it on Linux).
- You can now select multiple map files via CTRL, but they will always be loaded in alphabetical order. If you need to change the order, you have to either rename them, or add them to the mod list and reorder them there.
- Selected map files are now saved to presets instead of globally.
- Line for additional command line arguments has been split to preset-related and global one.
- You can now select whether "Launch options" in second tab should be saved globally or to presets.
- You can now drag&drop also in Setup dialog to IWAD list and Engine list.
- When using manual IWAD management mode, you can now give each IWAD a custom name by double-clicking on it in Setup dialog.
- IWADs are now distinguished from PWADs by file header instead of filename suffix.
- To select a map, a command +map is now used instead of -warp to allow custom map names.
- Added a basic support for Duke Nukem files (.grp and .rff).
- Double-clicking on a map pack will show content of an equally named txt file (if you double-click on AV.wad and there is AV.txt, it will show on screen).
- Fixed that collapsed directories always expanded again on every update.
- Fixed the "Allow jump/crouch/aim" checkboxes producing incorrect flags.
- Error message during parsing options.json file now contains more detailed information and checkbox to ignore them all.
- Automatic checking if there is a new version available.