Fulltext results:
- addon_bundle @modding
- ====== Add-on bundle ====== An //addon// bundle is a [[modding:addon_format|format]] first introduced by [[:Snowberry]]. As ... ==== Metadata ==== A couple of files inside the bundle have a special meaning: <code>[[info]]</code> (r... code> (required, folder) All the contents of the bundle should be placed here. TOC?? Now obsolete? --dani
- addon_box @fs
- art4.wad |... <note>Unlike in [[modding:addon bundle]]s, there is no **Contents/** subfolder. This is ... to the use of [[modding:Info]] in [[modding:addon bundle]]s. ==== Components ==== A box may contain mul... | episode1.pk3 | episode2.pk3 | ... Congrats! You now have a multi-component add-on bundle.
- addon_format @modding
- ta formats ===== ==== Addons ==== * [[:addon_bundle]] * [[:plugin_bundle]] (Snowberry extension) * [[:pk3|ZIP/PK3]] * [[:wad]] ([[modding:lmp]]) ==
- compiling_and_running_1.15_or_earlier_qmake @devel
- s all the binaries into a single **Doomsday.app** bundle. Consequently, it is not necessary to run "make i
- directory_structure @devel
- n the Mac, the executables are in the application bundle. In Unix they are in /usr/local/bin and /usr/loca
- pk3 @fs
- e]]. This is equivalent to the [[info]] file in [[bundle]]s. ====== See also ====== * [[automatic_f
- shell_help @multiplayer
- ver executable is inside the Doomsday application bundle. ==== Custom IWAD folder ==== Unless you've to
- shell_help_2.0 @multiplayer
- ver executable is inside the Doomsday application bundle. ==== Custom IWAD folder ==== Unless you've to
- plugin @snowberry
- ibution, "example.plugin". Each and every plug-in bundle should include a sub-folder called contents, in w
- version_1.2 @snowberry
- e location you installed Doomsday in. * Plugin bundle structure improved so that the Python modules of