I've put together a Wine wrapper for MDK, allowing it to be played on Linux almost like a native game & with no Wine knowledge required.

Simply run the build script to create the wrapper. If the installer files are not alongside the wrapper build files then the path to them will need to be specified either by passing it as an argument to the build script with -respath="<path>" or by setting an environment variable named WINEWRAP_RESPATH containing it. You can change the path to build the wrapper in and the name of the wrapper directory with the -buildpath= and -dirname= arguments. The build path can also be set with the WINEWRAP_BUILDPATH environment variable.

The output will be a directory containing the game set up within a preconfigured Wine prefix, along with its own copy of Wine, extracted game icons, documentation, and start script(s). From there simply run the start script to play. The start script also includes options for creating a shortcut, configuring the wrapper etc.

(to uninstall simply delete the game directory and any shortcuts you created, and the game's user data directory in ~/.local/share if you don't want to keep your saves & settings)

User data is stored under ~/.local/share/mdk

Full details are in the readme.txt and release notes. Here is the download link:

mdk_wine.tar.xz
(38.1 kB, SHA256: 2e110e04f902fc537696e197b106015d1a3406a74bdb4fd2d6f9deb355f79aef)

Last updated 2021/07/11

The wrapper uses Wine 6.0. Wine and Winetricks will be downloaded automatically if not present; to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap

This was put together very quickly - and has had little testing as a result - since GOG are currently giving the game away for free, but it seems to run well so far & I don't expect that there will be any issues. However if anyone encounters any problems then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion and/or The "Judas&trade; does this run in Wine" thread v1.173.

For more of my Linux Wine wrappers check out post 3 in this thread: Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion

At the very beginning, when script checks available packages, I got the following errors: Next, the following warnings: And the following closing messages:

It looks like a configuration issue pertaining to the system language/locale rather than an issue with the script. Were there any updates to your system recently that may have caused this?

You think so? I don't remember any updates related to the area, but I'll check. Perhaps it was caused by "inconsistent" settings, because I always try to use English versions of systems/apps with all the local settings (currency, date/number formats etc.) set to Polish. However never had problem with such approach.

By the way - MDK works perfectly so far. I've completed a few first Arenas with no issues.

I've completed the game without a single issue.
Thanks a lot for preparing the wrapper!

Edit:

I believe the process was unsuccessful and that's why there was no directory.


Original post:

Where is this directory? I've tried the .sh script under the latest Mint:

When I try to run it, it's opened by my text editor so...

I copied and pasted it into the Terminal.

Then I tried searching for "mdk" on my computer but I could find no game directory.

I did read the readme.txt file as well to no avail.

It shouldn't just open with your text editor; Mint should tell you that it's executable and ask what you want to do with it. It should be started from the terminal though, and copy & pasting the contents into the terminal will not work.

Open a terminal in the directory you extracted it to (right-click --> open in terminal) and type:

./mdk_wine.sh

then press enter. It'll create the MDK directory in the same directory as the mdk_wine.sh script

Thank you. Did you update this 2 days ago or when did you last update this wrapper? Just curious.

Also, I think Wine is giving me some trouble with your wrapper. Should I post the terminal output here or the forum you mentioned in you OP?

I only corrected a line in the post itself What error is it producing? Posting it here is fine

Ah, I see.

Here is the error:

Using Wine version: 2.10-staging
Checking for innoextract...
mdk_wine.sh: line 32: innoextract: command not found
System installed innoextract not found.
Using previously downloaded innoextract-1.6-linux.tar.xz in /home/vidsgame/.cache/winewrap/innoextract
/home/vidsgame/.cache/winewrap/innoextract/innoextract-1.6-linux.tar.xz: OK
Checking for icoutils...
Checking for installer and resource files...
All files found. Testing SHA256 hashes...
setup_mdk_2.1.0.29.exe: OK
mdk_res.tar.xz: OK
Testing checksum for PlayOnLinux-wine-2.10-staging-linux-x86.pol
PlayOnLinux-wine-2.10-staging-linux-x86.pol: OK
Creating directories...
Extracting innoextract...
Extracting Wine...
tar: lib/libwine.so: Cannot create symlink to ‘libwine.so.1’: Function not implemented
tar: lib/libwine.so.1: Cannot create symlink to ‘libwine.so.1.0’: Function not implemented
tar: bin/wineg++: Cannot create symlink to ‘winegcc’: Function not implemented
tar: bin/winecpp: Cannot create symlink to ‘winegcc’: Function not implemented
tar: share/man/man1/winecpp.1: Cannot create symlink to ‘winegcc.1’: Function not implemented
tar: share/man/man1/wineg++.1: Cannot create symlink to ‘winegcc.1’: Function not implemented
tar: Exiting with failure status due to previous errors
An error occurred trying to unpack Wine.

As always, thank you for the help.

Tar can't create the symlinks in the Wine package so it's failing... never had that happen before.

*quick Google search*

A lot of results have this issue occurring when trying to extract on filesystems that are formatted as FAT/NTFS or so. What filesystem does the partition where you have extracted the script use? If it's a Windows filesystem like FAT/NTFS then it won't work

It's a bad idea to run any Linux software from Windows filesystems... when I next update my wrappers I'll have the build scripts check the filesystem of the partition they're on & exit with a suitable error if looks like it's being used on a FAT/NTFS filesystem :)

Yes, unfortunately I have from previous experiences found that I have to keep my system fully compatible with Windows and Linux in terms of read and write so I'm doing whatever I could to the best that I could understand.

Windows' filesystems are more limited & don't store certain information, so Linux software really needs to have its own space. There shouldn't be any issue with using Windows filesystems for storing more general data like pictures, videos, documents etc. though.

I've modified all of the build scripts to abort on FAT/NTFS filesystems now, so the next time updates are released it'll be a lot more obvious what's wrong when someone tries this :)