KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#developer-tools #typescript #codex #ai-agents #claude-code #dsh #dsh-plugin #cli #macos #ai-agent #deepseek-harness #open-source

DoomTools

★ 74 Open GitHub ↗

Doom-related tools for Java. Home of DECOHack and lots of other utilities. Build WAD projects (and soon, other kinds) with ease!

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

![DoomTools Logo Banner](https://mtrop.github.io/DoomTools/images/doomtools-banner-darkened.png "DoomTools Logo Banner")  
Copyright (c) 2019-2025 Matt Tropiano

### Required Libraries

[Doom Struct](https://github.com/MTrop/DoomStruct) 2.19.5+  
[Black Rook JSON](https://blackrooksoftware.github.io/JSON/) 1.4.1+  
[RookScript](https://blackrooksoftware.github.io/RookScript/) 1.16.1+  
[RookScript-Desktop](https://blackrooksoftware.github.io/RookScript/) 1.10.2.1+

[FlatLaF](https://www.formdev.com/flatlaf/) 3.7+  
[RSyntaxTextArea](http://bobbylight.github.io/RSyntaxTextArea/) 3.6.0+  
[AutoComplete](https://github.com/bobbylight/AutoComplete) 3.3.2+  
[CommonMark](https://github.com/commonmark/commonmark-java) 0.19.0+  
[Jsoup](https://github.com/jhy/jsoup/) 1.15.3+

### Required Modules

[jdk.charsets](https://docs.oracle.com/en/java/javase/11/docs/api/jdk.charsets/module-summary.html)  
[jdk.crypto.ec](https://docs.oracle.com/en/java/javase/11/docs/api/jdk.crypto.ec/module-summary.html)  
[java.desktop](https://docs.oracle.com/en/java/javase/11/docs/api/java.desktop/module-summary.html)  
* [java.xml](https://docs.oracle.com/en/java/javase/11/docs/api/java.xml/module-summary.html)  
* [java.datatransfer](https://docs.oracle.com/en/java/javase/11/docs/api/java.datatransfer/module-summary.html)  
* [java.base](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/module-summary.html)

### Source

The `master` branch contains stable code (hopefully). Until a release is cut, the `master` branch will be shifting.

### Introduction

A bunch of command-line utilities for Doom stuff. This time, they're useful.

### Why?

Because they are all super useful, and can run anywhere (that runs Java). This also enables authors to
create a Continuous Integration path for building ongoing WAD projects. How cool would it be to always 
have a demo copy buildable at all times?

### Other Places to Download

#### Package Repositories

- [Arch Linux AUR doomtools-bin](https://aur.archlinux.org/packages/doomtools-bin) (courtesy of @sickcodes)
- [Fedora Linux Copr](https://copr.fedorainfracloud.org/coprs/electricbrass/doom/) (courtesy of @electricbrass)

### Compiling with Ant

**First**, to download dependencies for this project, type (`build.properties` will also be altered/created):

ant dependencies

To compile this program with Apache Ant, type:

ant compile

To make Maven-compatible JARs of this program (placed in the *build/jar* directory), type:

ant jar

To make Javadocs (placed in the *build/docs* directory):

ant javadoc

To compile main and test code and run tests (if any):

ant test

To make Zip archives of everything (main src/resources, bin, javadocs, placed in the *build/zip* directory):

ant zip

To create a Windows Installer in the `dist` folder:

ant dist.installer -Dinno.setup.dir=[Path-To-Inno-Setup] -Dembedded.jre.source.dir=[Path-To-Embedded-JRE]

To create all distributions (Bash, CMD, Installer):

ant dist -Dnatives.windows.dir=[PathTo-DoomTools-GUI-Native-Project] -Dinno.setup.dir=[Path-To-Inno-Setup] -Dembedded.jre.source.dir=[Path-To-Embedded-JRE]

To create a distribution and deploy it **(THIS WILL DELETE AND REBUILD THE TARGET DIRECTORY, `TARGETPATH`):**

ant deploy.cmd -Ddeploy.dir=[TARGETPATH]
	ant deploy.bash -Ddeploy.dir=[TARGETPATH]

To create the distributable JAR and deploy it to the target directory's `/jar` directory.

ant deploy.jar -Ddeploy.dir=[TARGETPATH]

To clean up everything:

ant clean

Note that the `deploy.dir`, `natives.windows.dir`, `inno.setup.dir`, and `embedded.jre.source.dir` 
properties are supplied above - it may be better to add local paths to your `build.properties` file for those.

### Installer Building and Native Code

Creating a bootstrap EXE for Windows GUIs requires another project, [DoomTools-GUI-Native](https://github.com/MTrop/DoomTools-GUI-Native).
It is not necessary for building or local deploying, but a package distributable will not be complete without it.

The EXE build and copy to `src/main/resources/shell/exe` will be skipped if the `natives.windows.dir` property is not set. You
are better off **NOT** setting it for every build as the EXE will more than likely be built differently every time.

Building a Windows Installer requires [Inno Setup 6.2.0](https://jrsoftware.org/isdl.php) or better, and requires that the property `inno.setup.dir` is set to Inno Setup's directory to make use of `iscc`.

The installer target will be skipped if the `inno.setup.dir` property is not set, and the embedded 
JRE version of the installer will not be built if `embedded.jre.source.dir` is not set.

### Recommended Minified JRE Setup

The JRE added to the installer (or even just for running DoomTools) should be one made with the following command line:

jlink --add-modules java.desktop,jdk.crypto.ec,jdk.charsets --compress=2 --output [jredir]

That's `java.desktop` for the required packages and `jdk.crypto.ec` to ensure it can hit secure sites for updating itself
and perhaps future tools that pull resources from secure TLS Internet addresses, and `jdk.charsets` for the extended charsets.

### Manually Updating Your Own Installed Version via Source

If you have your own installed version of DoomTools but want to keep that install intact AND also develop for it,
you do not need to go the route of direct-deploying to your install via `ant deploy.cmd` or `ant deploy.bash`
and risk obliterating everything in its target directory. For a *safer* approach, you can try the following (assuming
that you can already successfully build DoomTools from source; see "[Compiling with Ant](#compiling-with-ant)" above).

DoomTools is contained in one complete JAR. To build just this JAR file, type the following in the project directory:

ant jar.one

...and that will create a JAR file of the build in the `build/jar` directory (assuming project path defaults) 
called `doomtools-YYYY.MM.DD.HHmmssSSS.jar`, where `YYYY.MM.DD.HHmmssSSS` is the current formatted 
UTC date.

Then, you can copy or move that JAR file into the `jar` directory under the DoomTools install directory, and if
that JAR is the latest date, then all of the DoomTools CMD/Bash/EXEs will use that JAR automatically instead of 
the others that are also in that directory.

The `deploy.jar` target will copy the JAR to the `/jar` directory off of the deployment, if you set the `deploy.dir`
deployment root.

This is similar to how DoomTools updates itself - it just downloads the latest stand-alone JAR from its main releases.

### Other Notes

Even though this project can technically be used as a library, use caution when integrating this package 
with your own programs - contents and APIs that are not part of other third-party libraries will be in 
flux as the utilities evolve. This project makes **no promises about a consistent API structure** within itself,
despite keeping things documented in a publicly-accessible fashion.

### Utilities

#### DoomTools

A program that just displays info about the toolset that you are using (or manage other things, in the future).

#### DecoHack

A utility that uses a DECORATE-like language scheme for creating DeHackEd patches.

#### DImgConv

A utility that bulk converts images to Doom formats.

#### DMXConv

A utility that converts all sorts of sounds to DMX digital sounds using either the Java SPI or FFmpeg.

#### DoomFetch

A utility that fetches WAD files from different sources. Can serve as a dependency manager.

#### DoomMake

A project build utility that is agnostic to all operating systems (for the most part).

#### WadMerge

A utility that performs Script-based WAD compilation and merging.

#### WSwAnTbl

A utility that reads DEFSWANI/SWANTBLS data files and compiles it into ANIMATED and SWITCHES lumps.
Can also export a set of ANIMATED and SWITCHES lumps to a definition file.

#### WadTex

A utility that reads a DEUTEX-style texture file and imports it into a WAD file as TEXTUREx and PNAMES lumps.
Can also export TEXTUREx/PNAMES in the same way.

#### WTexList

A utility that scans textures in a WAD and outputs a list of found textures and flats, suitable for import into one of the next programs...

#### WTexScan

A utility that scans maps in a WAD and outputs a list of found textures and flats, suitable for import into the next program...

#### WTEXport

A utility that exports textures from one WAD into another, including associated ANIMATED and SWITCHES textures.

#### WadScript

A scripting system for doing practically anything with Doom stuff. Also includes Rookscript, a subset script.

### Special Thanks

Special thanks to, in no particular order, **Aurelius**, **Antares031**, **floatRand**, **Xaser**, **kraflab**, **skillsaw**,
and **punchyouinthefaceman** for their incidental QA testing. Lots of bugs were fixed because of all of you!

### Other

These programs and the accompanying materials are made available under the 
terms of the MIT License, which accompanies this distribution.

A copy of the MIT License should have been included in this release (LICENSE.txt).
If it was not, please contact us for a copy, or to notify us of a distribution
that has not included it.

This contains code copied from Black Rook Base, under the terms of the MIT License (docs/LICENSE-BlackRookBase.txt).

This also makes use of the [FamFamFam "Silk" icon set](http://famfamfam.com/lab/icons/silk/) by Mark James, under 
the terms of the Creative Commons 3.0 License with Attribution, Unported (docs/LICENSE-Silk Icons.txt).

DoomTools

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README