Fulltext results:
- packages @fs
- ckage contents (see [[package licensing]]). | | ''tags''| Keywords/tags that apply to the package, as a white-space separated list of words. This is used for organizing larger collections of packages and for finding packages (see [[package tags]]). | **<nowiki>__init__.ds</nowiki> script.** ... he title, as that is specified separately. * **Tags.** It is important that packages are tagged using all the [[package_tags|relevant tags]] since that enables users to locate the package more easily. * **Zipping.** When distributing a package, the top-level package folder should be
- resource_packaging_guidelines @modding
- the user interface. When choosing the title and tags for the package, consider them together: when the user searches f... om adding game names (for example "hexen") in the package title, because Doomsday expects these to be included in the package tags. Tags should be used primarily as a tool for allowing the user to find the package. For example, if the user is interested in 3D models for Hexen, they might enter "hexen model" as the search terms. All packages that have the tags "hexen" and "model" will then be listed. In the
- package_tags @fs
- ====== 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 on... sday will try to automatically guess which game a package is meant to be used for, however you can also manually use these tags in the package metadata. This will override any a
- developer_guidelines @devel
- ker issue). Your commit message should contain //tags// that describe the type of commit (e.g. ''Fixed'... d by the commit. You can see many examples of the tags by examining the Git history. The commit tags serve a couple of purposes: * At-a-glance summary of w... Index the commits in the [[:codex]]. While the tags are not checked for validity, you should generall
- 1.15 @version
- econfiguring. ===== Internal progress ===== **Packages.** So far Doomsday has had no internal understan... owberry frontend has been responsible for parsing package metadata and deciding which actual files Doomsday... cript]] language. We have put together a new [[fs:package]] format that takes full advantage of FS2 and Doo... er, we will also allow loading old/other resource package formats for backwards compatibility, although the
- 2.1 @version
- pg?190}}**Custom game IWADs.** You can select any package as the main data file of a game instead of just t... own IWADs.** Mod lists show “gamedata” and “core” tags on request. You can search for these tags easily via the Mods tab menu. The “gamedata” tag is given to ... ecognized IWADs, and “core” is for Doomsday’s own packages. **Improved mod editing behavior.** If you edit
- automated_build_system @devel
- if the master branch has new commits, and if so, tags and builds a new release. The releases become ava... bed above. Alternatively, there are prebuilt .deb packages available in [[https://launchpad.net/~sjke/+arch... able : A **stable** build is one which has been packaged for widespread distribution and has been extensi... ts to generate an installable binary distribution package under //distrib/releases//. The script takes no
- compiling_and_running_2.0 @devel
- * Download a [[http://dengine.net/source|source package]]. * Check out the [[https://github.com/skyjak... hen switch to any release or a specific build via tags. Stable releases are tagged "release-x.y.z". ===
- home_screen @guide
- custom profiles, save folder access, mod browsing tags ("gamedata"). * [[version:2.0]]: Home screen re... ed game profiles, new multiplayer server browser, packages list. * [[version:1.14]]: Multiplayer sessions