https://manual.dengine.net/ 2026-04-11T14:23:45+00:00 https://manual.dengine.net/ https://manual.dengine.net/lib/tpl/dengine/images/favicon.ico text/html 2020-01-10T10:55:10+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/pk3?rev=1578653710&do=diff PK3 format This article provides an overview of the usage of PK3s with Doomsday. PK3 is the recommended container format to use when creating addons for Doomsday that contain a lot of resources (hires textures, MP3's, models, etc.). Overview PK3 or PAK3 is the format used by text/html 2018-10-19T11:40:59+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/lump_assembly?rev=1539949259&do=diff Lump assembly As the name implies, a lump assembly is an assortment of lumps arranged into an assembly (inside a folder). It is also possible to include a hierarchy of folders inside a Lump Assembly (therefore puting lumps into “namespaces” where they can have a load order implied; see below). It is even possible to nest text/html 2017-03-20T10:51:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/pwad?rev=1490007118&do=diff PWAD stands for “Patch wad”. PWADs contains data_lumps that partially or fully augment/replace the data from iwads. See also * WAD text/html 2020-01-10T10:56:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/addon_box?rev=1578653798&do=diff Box (add-on format) Sometimes it is necessary to combine multiple addons into a single 'mod' package for distribution. A mod consisting of multiple (perhaps by different authors) can be packaged together into a single folder. The .box format was initially created for the Snowberry launcher app. Recent versions of Doomsday support it, too. text/html 2018-12-06T07:33:03+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/package_tags?rev=1544081583&do=diff Package tags Package tags are used for categorizing and flagging packages. It is important to define valid and complete tags for each package because this helps users find the right ones, and allows the engine to treat packages appropriately. With the exception of the tags listed below, you are free to use any combination of letters, numbers and underscores as a tag. A tag cannot contain space characters.