https://manual.dengine.net/ 2026-04-11T14:06:38+00:00 https://manual.dengine.net/ https://manual.dengine.net/lib/tpl/dengine/images/favicon.ico 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 2009-08-13T15:05:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/file_formats?rev=1250175914&do=diff This article presents an overview of all the file formats used by doomsday. Textual formats Only a text editor is needed for creating and editing these file formats. * DED: Doomsday Engine Definition Binary formats These file formats require a special editor utility. * MD2: Quake 2 Model * DMD: Doomsday Model 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-19T19:35:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/manifest?rev=1489952147&do=diff Manifest files are used to provide the metadata for an addon, which does not, or cannot, contain the metadata itself. A good example of such a scenario is wanting to adapt an addon whose stipulated license prevents directly modifying the addon itself. A manifest may include loading instructions for the addon and how its contents should be interpreted. text/html 2014-10-19T10:03:01+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/package_identifier?rev=1413712981&do=diff * REDIRECT File_name_and_identifier 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. text/html 2017-03-13T11:41:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/package?rev=1489405307&do=diff text/html 2019-11-17T07:32:04+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/packages?rev=1573975924&do=diff Packages In Doomsday 2, resources are collected into packages. This article describes the Doomsday 2 package format and how you should go about creating your own packages. Package format A Doomsday 2 package can either be a folder or a ZIP archive. Regardless of the type, the file name must have a text/html 2009-08-14T09:56:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/packaging_resources?rev=1250243798&do=diff This article describes preferred conventions for packaging resources for doomsday_2.0. How ZIP files are treated The engine does not differentiate between regular directories and the contents of ZIP files. In the internal_file_system, ZIP files appear as directories. Their contents can be modified as if they were regular directories/files. This applies to creating/deleting files/subdirectories, and reading/writing files. 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 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 2017-03-13T12:04:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/subpackage?rev=1489406652&do=diff text/html 2017-03-20T11:57:34+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/tagged?rev=1490011054&do=diff text/html 2017-03-13T13:21:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/vdm?rev=1489411285&do=diff text/html 2017-03-15T07:34:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://manual.dengine.net/fs/virtual_directory_mapping?rev=1489563281&do=diff Virtual directory mapping 1.9.0 introduces virtual directory mappings (abbrev. VDM), which allow you to make the contents of one directory appear inside another directory at runtime. For example, you could have a directory called MyAuto with a set of data files somewhere on your hard drive. You could map this directory to