![]() This property is effective only if its GAMEINFO equivalent is set to "", or is not used entirely.Urm, I'll explain politely, how things work here. This property is effective only if its GAMEINFO equivalent is set to -1, or is not used entirely. Possible values are:Ĭontrols loading of game_widescreen_gfx.pk3 file. -1: leaves the option of loading the file to the user (default).Ĭontrols loading of brightmaps.pk3 file.0: prevents the file from being loaded.Note that cheat codes are still usable if the allcheats console variable is set to true.Ĭontrols loading of light.pk3 file. This probably isn't very useful for stand-alone games.ĭeleteLumps = "FONTB01", "FONTB02", "FONTB03", "FONTB04", "FONTB06"ĭisables cheat codes. Used to delete certain "placeholder"-style lumps in the BigFont used by Heretic and Hexen. This probably isn't very useful for stand-alone games.Įffectively ignores the specified IWAD lumps while loading the game. Ignores the "(C)WILVxx" graphic lumps used for level names in all of the official Doom IWADs so that they can be properly localized by LANGUAGE. Used by Strife for VOICES.WAD, and by Hacx for GZDoom-specific data. Specifies another archive to be auto-loaded alongside the current game. Probably not enormously useful for standalone games. Use the game's name string, not its filename! ![]() If that game does not exist, this game will not appear on the IWAD list. Specifies that another game is required for this game to work. "Stairs" ( Compatibility flag used for TNT: Evilution)."Shorttex" ( Compatibility flag used for all Doom IWADs)."Extended" (Used for Heretic: Shadow of the Serpent Riders)."Teaser2" (Used for the "new version" of the Strife Teaser demo)."Shareware" (Used for shareware versions of games)."Poly2" ( Compatibility flag for polyobjects in MAP47 of Deathkings of the Dark Citadel)."Poly1" ( Compatibility flag for polyobjects in MAP36 of Hexen)."NoTextcolor" (Used to disable text colouring in Chex Quest 3 due to bad TEXTCOLO lump).These probably aren't very useful for stand-alone games. Optional and presumably the same as the GAMEINFO implementation. Ignored in custom lumps, which describe the file containing them. Only used in the internal lump to validate external files by verifying they have the expected content, and to resolve ambiguity when different IWADs can use the same name. Otherwise, you may wish to inherit from one of the default GZDoom definitions. If you've defined everything in your MAPINFO's gameinfo block, this is optional. Specify a base MAPINFO lump to load before your game's MAPINFO lump (if present). Only used in the internal lump to identify files that do not have the custom. or you can use a pre-existing game's name to use their settings. You can use a completely stand alone name to completely separate your game from pre-existing configurations. Similar to AutoName, but for keybinds etc. If in doubt (or if your game has no ties to any of the original games) just use Doom. "Doom.M圜ustomGame" is okay - "Doom.id.Doom1" is not. Otherwise, your resources will be overwritten by internal engine assets. from a pre-existing game while allowing separate configuration specific to your game.ĭo not use an already existing internal name for your AutoName - you must use a different name. The name used for your game in the ini files. This appears in the game selection list, as well as acting as the window title in windowed mode when i_friendlywindowtitle is enabled. Note that standalone games will not process GAMEINFO, as this other lump is only scanned for files loaded as mods. ![]() IWAD files without this extension (such as doom2.wad for example) are not scanned for presence of an IWADINFO lump and therefore rely on GZDoom's internal list.Ĭustom IWADINFO lumps and the lump in game_support.pk3 follow a similar syntax, except custom IWADINFOs are expected to only define one IWAD and not include a file list. ipk3 extensions for the presence of an IWADINFO lump. The engine comes with its internal IWADINFO lump (in game_support.pk3) to detect the classic games, but games created for GZDoom can now feature their own custom IWADINFO to declare themselves as standalone games. Detected games will be listed in the IWAD selection box on startup. IWADINFO allows the engine to identify data files that serve as stand-alone games ( IWAD), rather than mods. ![]()
0 Comments
Leave a Reply. |