Fulltext results:
- pk3 @fs
- le named [[info]] in the root of a PK3 package, [[snowberry]] will treat it as a [[metadata_configuration_file]]. This is equivalent to the [[info]] file in [[bundle]]s. ====== See also ====== * [[automatic_file_mapping_in_pk3]] ====== Footnotes ====== <refe
- readme_macos @guide:2.2
- arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[guide/configuration|syntax of the file]] is documented in the wiki.
- doomsday @guide:2.2:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[guide/configuration|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- readme_windows @guide:2.2
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime files are stored in a folder called //AppData\Local\De
- readme_macos @guide:2.3
- arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[guide/configuration|syntax of the file]] is documented in the wiki.
- doomsday @guide:2.3:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[guide/configuration|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- readme_windows @guide:2.3
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime files are stored in a folder called //AppData\Local\De
- runtime_directory @guide
- Frontend\runtime\'' | | Windows XP| ''C:\Program Files\Doomsday\Snowberry\Runtime\'' | | Mac OS X 10.4-8| ''/Users/''//''<u... able viewing of hidden directories exists in your file manager).</note> ===== See also ===== * [[Readme]] * [[Configuration]]
- readme_macos @guide:2.1
- ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[guide/configuration|syntax of the file]] is documented in the wiki.
- readme_windows @guide:2.1
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime files are stored in a folder called //AppData\Local\De
- doomsday @guide:2.1:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[guide/configuration|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- 2.0 @version
- -01,2.0,build2281~@# ===== Highlights ===== {{ file:home_screen_v2.jpg?320}} **Home Screen replaces the front-end app.** The Python-based Snowberry launcher application was created in 2005 and has ... called "ring zero") replaces its functionality. Snowberry's design and features did not evolve greatly in i... due. Integrating game profile management and all configuration settings into Doomsday's own UI makes for a more
- doomsday @guide:2.0:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[Configuration#Unix_system-level_config_files|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- readme_macos @guide:2.0
- ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The packages will not be copied or m... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[Configuration#Unix_system-level_config_files|syntax of the file
- readme_windows @guide:2.0
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The packages will not be copied or m... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ed in Audio Settings (see <html><a href="#config">Configuration</a></html>). ; ''-verbose'' | ''-v'' : Print ... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime