Fulltext results:
- readme_macos @guide:2.2
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. (The variable ''Config.resource.r... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- doomsday @guide:2.2:man
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. (The variable ''Config.resource.r... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- readme_windows @guide:2.2
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. (The variable ''Config.resource.r... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- readme_macos @guide:2.3
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. (The variable ''Config.resource.r... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- doomsday @guide:2.3:man
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. (The variable ''Config.resource.r... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- readme_windows @guide:2.3
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. (The variable ''Config.resource.r... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- configuration
- e default settings are reasonable for most users. Doomsday has many configuration options if something is no... signed to run on VGA 320x200 resolution displays. Doomsday is able to run in any display size, but depending... try reducing the pixel density setting to enlarge Doomsday's pixels. This is preferable to reducing your mon... e enabled in the Input Settings via the Task Bar. Doomsday comes with a couple of //game controller presets/
- task_bar_and_console
- toggle the prompt between Quake-style console and Doomsday Script modes. This is mostly of use to advanced users an... ented messages. ===== Config menu ===== Most of Doomsday's [[configuration]] settings are found in the ⚙️
- readme_macos @guide:2.1
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. * The configuration file //~/.d... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- readme_windows @guide:2.1
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. * Environment variables DOOMWAD... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- doomsday @guide:2.1:man
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. * The configuration file //~/.d... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- doomsday @guide:2.0:man
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. * The configuration file //~/.d... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- readme_macos @guide:2.0
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. * The configuration file //~/.d... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- readme_windows @guide:2.0
- user interface, for instance when you first start Doomsday. Its value can also be manipulated in the Doomsday Script command prompt. * Environment variables DOOMWAD... utton next to the command prompt. **Interactive Doomsday Script prompt.** [[Doomsday Script]] is a fully-fledged Python/Ruby-like scripting l... ch release. The command prompt can be switched to Doomsday Script mode by right-clicking the ">" prompt menu button... ng entered into the command prompt is then run as Doomsday Script. This mode is intended only for developers. ===
- persist.pack
- the name of the special resource package where [[:Doomsday 2]] keeps all persistent application data. The pa... 's runtime folder. The package uses the standard Doomsday resource package format (ZIP/PK3 with [[modding:I... ta]]. ==== modules/Config ==== The ''Config'' [[script:record|namespace]] contains settings such as: *