cm | ||
d3xp | ||
framework | ||
game | ||
idlib | ||
MayaImport | ||
renderer | ||
sound | ||
sys | ||
tools/compilers/aas | ||
ui | ||
.gitignore | ||
CMakeLists.txt | ||
config.h.in | ||
COPYING.txt | ||
README.md |
dhewm3 Mod SDK
This repository contains an SDK that can be used to create modifications ("mods") for (or port Doom3 mods to) dhewm3.
It contains (mostly) the same source files as the original Doom3 SDK, but these
are taken from dhewm3 and are licensed under GPLv3, not the SDK license.
Another small difference is that this is built using CMake
instead of SCons + VS Project files.
This means that you need CMake to build it, but don't worry, on Windows it can
create a Visual Studio Solution for you so you can program and compile with
Visual Studio like you might be used to.
Some ports of existing Mods
This repository also contains ports of existing mods whichs authors released the source under GPL; you can find these in their own branches: Classic Doom 3, Denton's Enhanced Doom3, Fitz Packerton HardQore2 and Scarlet Rivensin: The Ruiner
You can find Win32 DLLs of those mods that work with dhewm3 1.5.0 at https://github.com/dhewm/dhewm3/releases/download/1.5.0/dhewm3-mods_1.5.0_win32.zip
The equivalent Linux amd64 (x86_64) libs can be downloaded at https://github.com/dhewm/dhewm3/releases/download/1.5.0/dhewm3-mods_1.5.0_Linux_amd64.tar.gz
How to build
On Windows
You need CMake either Visual Studio (2010 and newer have been tested) or MinGW-w64
- Clone the dhewm3-sdk git repo
- (optional: switch to an existing mods branch:
git checkout dentonmod
) - create a build directory in your
dhewm3-sdk/
directory (build/
orbuild-dentonmod/
or whatever) - Start the CMake GUI
- Select your
dhewm3-sdk/
folder for "Where is the source code" and your
build directory from step 3 for "Where to build the binaries". - Click
[Configure]
, select what you want to build with, e.g. "Visual Studio 15 2017", click[Finish]
, wait for CMake to do its thing- If you're using MinGW you'll have to select your build type now, e.g.
Debug
(not optimized but debuggable) orRelease
(optimized and thus faster, but can't be debugged that well). - (For Visual Studio you don't have to select a build type now, you can do it in in Visual Studio)
- If you're using MinGW you'll have to select your build type now, e.g.
- Click
[Generate]
- Building:
- If you're using Visual Studio, you should be able to just click
[Open Project]
to open the generated Project in Visual Studio. You can now compile the SDK in Visual Studio (and of course make your changes to the code). - (Untested:) For MinGW, open your MinGW or MSys shell, switch to your build directory and execute
make -j4
to build the game DLL
- If you're using Visual Studio, you should be able to just click
- Now it's time to copy the DLL (e.g.
dentonmod.dll
) to your dhewm3 install, where base.dll and d3xp.dll are- For Visual Studio the DLL should be in a subdirectory of your build directory, depending on the build type you selected in
build/Debug/
orbuild/Release/
or similar - For MinGW the DLL should be directly in your build directory.
- For Visual Studio the DLL should be in a subdirectory of your build directory, depending on the build type you selected in
- start the game with that mod, like
dhewm3 +set fs_game dentonmod
(Make sure to actually have the mods game data in the right directory as well; the directory name should be the same as the game lib name, but without .dll, for example dentonmod/ for dentonmod.dll)
On Linux and other Unix-likes
On Linux and similar the following should work (if you have cmake, make and GCC/g++ installed):
- Clone the dhewm3-sdk git repo
- switch to your git clone's directory:
cd dhewm3-sdk
- (optional: switch to an existing mods branch:
git checkout dentonmod
) - create a build directory:
mkdir build
- switch to build directory:
cd build
- create Makefile with CMake:
cmake ..
- by default, this will create an RelWithDebInfo build, which is optimized but still has debug info, so it's somewhat debuggable. You can select another kind of build with
cmake -DCMAKE_BUILD_TYPE=Debug ..
for a Debug build with less optimization, which will make it easier to debug (but possibly slower). You could also replace "Debug" with "Release" for a proper optimized Release build without any Debug info.
- by default, this will create an RelWithDebInfo build, which is optimized but still has debug info, so it's somewhat debuggable. You can select another kind of build with
- compile the mod .so:
make -j4
- it (e.g.
dentonmod.so
) should now be in the build/ directory, copy it to your dhewm3 install, where base.so and d3xp.so are - start the game with that mod, like
dhewm3 +set fs_game dentonmod
(Make sure to actually have the mods game data in the right directory as well; the directory name should be the same as the game lib name, but without .so/.dylib, for example dentonmod/ for dentonmod.so)
How to port a Mod to dhewm3
The usual (easiest) way to port a mod is to make a diff between the mod's source
and the Doom3 SDK and apply the resulting patch to the vanilla game source (from the master branch).
Afterwards usually some manual work must be done to resolve patching conflicts and get the mod to compile.
Also, the CMakeLists.txt file must be adjusted (see the dentonmod branch for examples).
Please note that currently I only accept mods that are released under the
GPL license - the one used by Open Source Doom3 (i.e. not only the Doom3 SDK license) -
because neither the GPL nor the SDK license allow merging code from both licenses.
So please get permission from the mod authors first.
Yes, this unfortunately means that unless you manage to contact Sikkpin and get
his permission, there will be no Sikkmod for dhewm3 (and neither other mods that
use Sikkmod code) :-(
(If you are Sikkpin, please get in touch!)
Getting in touch
If you are a mod author and want to release your mod's sourcecode under GPL, but don't want to port it yourself (or don't have time or are unsure how) please contact me, I can probably help you :-)
The easiest way to contact me is by creating an issue in this Github repository,
or by sending a DM to caedes in the id Tech Forums
or by pinging caedes in the #iodoom3 IRC channel on FreeNode.
If you prefer E-Mail, you can find my address in the git commits.