Reply to Re: Martridge - The DMOD Wizard
If you don't have an account, just leave the password field blank.
V0.5.1.4 is up on github https://github.com/drone1400/martridge/releases/tag/V0.5.1.4
I've added some special handling for launching a dmod with WinDinkEditPlus. Basically, you could launch any dmod with an editor application before too, but WinDinkEditPlus, being absolutely amazing, has some issues...
So the main issues with WDEP in 2022 on Windows 10 are two:
1. It tries to store config files in the C:\Windows directory, thus you need to launch it as admin at least once to configure the Dink installation directory...
2. It can't open a DMOD unless it is a subdirectory of WDEP's known Dink installation directory
I've implemented some automagic workarounds for this in Martridge like this:
1. If a config file is not found, then it asks you if you want to launch WDEP as admin so that it can save its initial config file in the C:\Windows dir, of course you are free to decline, but then you'll have to manually launch it as admin yourself
2. If a DMOD isn't a subdirectory of WDEP's known Dink directory, Martridge will ask you if you want to create a symbolic link to the DMOD directory. By creating a symbolic link to the DMOD inside the Dink directory, as far as WDEP is concerned, the DMOD is in the Dink directory and will be able to load it just fine. Martridge shows you an alret window where it asks you if you want it to launch a CMD.exe process as admin and run the command to create a symbolic link automatically, OR if you don't want it to do anything by itself, it gives you the full command in a textbox, so you can manually run it and create the symbolic link directory yourself.
NOTE: I've only really tested this working properly with the latest version of WinDinkEditPlus 2. I *ASSUME* that is the version everyone is using nowadays, but please correct me if I'm wrong...
EDIT: Planned upcoming changes:
- option for saving DMOD launch options on a per DMOD basis (as requested by Bluedy)
- figuring out a way to improve the DMOD launcher application selection
I've added some special handling for launching a dmod with WinDinkEditPlus. Basically, you could launch any dmod with an editor application before too, but WinDinkEditPlus, being absolutely amazing, has some issues...
So the main issues with WDEP in 2022 on Windows 10 are two:
1. It tries to store config files in the C:\Windows directory, thus you need to launch it as admin at least once to configure the Dink installation directory...
2. It can't open a DMOD unless it is a subdirectory of WDEP's known Dink installation directory
I've implemented some automagic workarounds for this in Martridge like this:
1. If a config file is not found, then it asks you if you want to launch WDEP as admin so that it can save its initial config file in the C:\Windows dir, of course you are free to decline, but then you'll have to manually launch it as admin yourself
2. If a DMOD isn't a subdirectory of WDEP's known Dink directory, Martridge will ask you if you want to create a symbolic link to the DMOD directory. By creating a symbolic link to the DMOD inside the Dink directory, as far as WDEP is concerned, the DMOD is in the Dink directory and will be able to load it just fine. Martridge shows you an alret window where it asks you if you want it to launch a CMD.exe process as admin and run the command to create a symbolic link automatically, OR if you don't want it to do anything by itself, it gives you the full command in a textbox, so you can manually run it and create the symbolic link directory yourself.
NOTE: I've only really tested this working properly with the latest version of WinDinkEditPlus 2. I *ASSUME* that is the version everyone is using nowadays, but please correct me if I'm wrong...
EDIT: Planned upcoming changes:
- option for saving DMOD launch options on a per DMOD basis (as requested by Bluedy)
- figuring out a way to improve the DMOD launcher application selection
