goldutil(1) Manual Page

Print parsed data from a BSP.

On a BSP with embedded textures, change the texture names to match what is in the original game’s materials.txt.
This allows setting proper material sounds to custom textures without having to distribute a materials.txt file.
Warning: The BSP cannot use any of the textures listed in the original materials.txt

Export a .map file the way TrenchBroom does, removing all layers marked as not exported. Output is written to STDOUT, if no <file> is provided the map will be read from STDIN.

Process neat_* entity macros and outputs the generated .map to standard output.
See Neat entities and goldutil fgd.

Create a graphviz digraph of entity caller/callee relationships from a .map file. ripent exports use the same format and can be read too. Output is written to STDOUT.

Extract node positions from a .nod graph into a .map populated with corresponding info_node entities.
Links between nodes are represented using target/targetname, nodes are duplicated to allow showing all links, TrenchBroom layers are used to separate links by hull type. The resulting .map file is not for engine consumption, only for TrenchBroom-assisted archaeology.

Create a sprite from the given ordered list of PNG frames and write it to <path>.

Input images MUST be 256 colors paletted PNGs, the palette of the first frame will be used, the other palettes are discarded and all frames will be interpreted using the first frame’s palette.
If the palette has under 256 colors it will be extended to 256, putting the last color of the palette in the 256th spot and remapping the image to match this updated palette. This matters for transparent formats. If you use pngquant(1) to create your palletized input files, you can use its --pngbug option to ensure the transparent color will always be last.

Output all frames of a sprite as PNGs in the current working directory.
The output files will be named after the original sprite file name plus a frame number suffix and an extension.

Create a WAD file from a list of PNG files and directories. Directories are not scanned recursively and only PNG files are used.
File base names (without extensions) are uppercased and used as texture names.
Warning: Names exceeding 15 chars will trigger an error as this is the maximum length supported by the WAD format.

Extract a WAD file in the given DIR as a bunch of PNG files.

Print parsed data from a WAD file.

Output to STDOUT the FGD to use with goldutil map neat.

Takes a materials.txt file and only keep the texture names that are used in the given BSP files. This is useful to keep a final materials.txt under 512 entries when working with large texture collections. Filtered materials are written to STDOUT.

Read all BSP files at the given directory and create a WAD containing only the textures used by the BSPs. This allows using large texture collections during development but only distribute the smallest possible WAD at release time.
Be aware that Half-Life requires the wads from the "wads" property to be present and will attempt to load them. Before release you should generate the output WAD, remove the WADs that were used during filtering from your worldspawn "wads" property, add the output WAD, and then rebuild your maps.

Make a WAV loop by setting CUE points.
In GoldSrc only the presence of these CUE points is checked, not their position.
This commands adds a CUE point at the end so ambient_generic can do its work.

An entity that can be used as a master in other entities, avoiding multisource quirks and limitations.
When targeting it:

Internally it works by setting up a button_target (<targetname>_proxy), a multisource (<targetname>), and three trigger_relay (<targetname>_on, <targetname>_off, and <targetname>_toggle).
trigger_relay entities targeting <targetname> are redirected to <targetname>_proxy. All other entities targeting <targetname> will be rewritten to target <targetname>_toggle.

Equivalent to env_message with three important differences: