The Morrowind Tools Project is an attempt to provide some helpful utility programs for the game The Elder Scrolls III: Morrowind. These tools will be related to mods ("plugins") for Morrowind and allow things that would be difficult to do with Morrowind's own modkit.
Some programs for The Elder Scrolls V: Skyrim were added more recently. So despite its name the project also contains tools for Skyrim.
- bsa_cli: a command-line interface for BSA archives of Skyrim
- bsafs: (Linux only) a FUSE file system for BSA archives of Skyrim
- conv_cams: (obsolete) tool to convert CAMS records in an ESM file to the pre-1.5 patch state
- formID_finder: command-line interface to search for form IDs in Skyrim
- formID_finder_GUI: a GUI that wraps
formID_findercalls in a more user-friendly way - small_high_elves: (just for fun) command-line tool that creates a Skyrim plugin which adjusts the size of high elves to be not so high anymore
- cell_translator: (incomplete) translates Morrowind plugins from one language into another
- data_cleaner: helps to find and delete unused files within the Data Files directory of Morrowind
- name_generator_mw: generates lore-friendly character names by using the names of The Elder Scrolls III: Morrowind as reference
- skill_rebalance: creates a Morrowind plugin that makes leveling up skills harder or easier
- spell_rename: helps to sort the spells in Morrowind's spell menu according to their spell schools by creating a plugin file that changes the spell names
- apps: contains code for application programs
- mw: contains code for Morrowind-related programs
- sr: contains code for Skyrim-related programs
- ci: scripts and other files that are used as part of Continuous Integration (automated builds and tests, etc.)
- dev: utilities / helper applications used during development
- lib: This directory contains the source code for stuff that is used in more than one branch of morrowtools.
- tests: contains code for test cases
- win64-compile-test: utility to test for 64 bit Windows OS when compiling
Within some directories you may find files named TODO or ToDo.txt. These files list some of the work that still has to be done for that specific directory.
To build these tools from source you need a C++ compiler with support for C++17, CMake 3.8 or later, the FUSE library, the LZ4 library and the zlib library (>=1.2.7). pkg-config is required to make it easier to find compiler options for the installed libraries. Additionally, the program uses Catch (C++ Automated Test Cases in Headers) to perform some tests.
It also helps to have Git, a distributed version control system, on your build system to get the latest source code directly from the Git repository.
All of that can usually be installed be typing
# Debian or Ubuntu
apt-get install catch cmake g++ git libfuse3-dev liblz4-dev pkg-config zlib1g-dev
or
# AlmaLinux 8 or Rocky Linux 8
yum install epel-release # required for catch
yum install catch-devel cmake fuse3-devel gcc-c++ git lz4-devel pkgconfig zlib-devel
or
# Alpine
apk add catch2 cmake fuse3-dev g++ git lz4-dev make pkgconf zlib-dev
into a root terminal.
Note: Instructions for building on Windows systems are currently not included.
It it possible, but the setup is a bit complicated. The easiest way to do it is
probably to get a MinGW compiler (e. g. as part of
Code::Blocks IDE) and download and compile
zlib manually. A few hints on how to compile zlib
manually can be found in the file zlib_info.txt. After that is done, you can
use the Code::Blocks project files (*.cbp) in the directories to build the
applications.
Get the source directly from Git by cloning the Git repository and change to the directory after the repository is completely cloned:
git clone https://github.com/Thoronador/morrowtools.git ./mwtp
cd mwtp
That's it, you should now have the current source code on your machine.
The build process is relatively easy, because CMake does all the preparations. Starting in the root directory of the source, you can do the following steps:
mkdir build
cd build
cmake ../
make -j4
If you want to run the test suite, too, then there is one more step:
ctest -V
There is an experimental Dockerfile that uses Docker to
cross-compile the tools for 32 bit Windows (also runs on 64 bit Windows).
It will create a ZIP archive named artifacts.zip located in
/opt/morrowtools/build/ when successful. This file contains the compiled
binaries after the Docker image has been built successfully. To start the build
type
docker build . -t morrowtools
in the root directory of your source checkout.
For information how to build natively on Windows, see the MSYS2 build instructions.
Copyright 2011-2024 Dirk Stolle
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.