From Quake Wiki
Quake Standards Base is a project which aims to raise the bar of basic Quake modding and mapping. The goal is to push engine devs to support features which are very specific to making mods and maps for Quake (such as increased map and entity limits, external textures and new builtins), rather than user-features (such as a better server browser in the menu, nicer particle effects and an FPS counter).
The spec is still a work in progress!
- LordHavoc for dpextensions.qc, most features people seem to want were listed and described here
- Spike for the FTE Wiki
- frag.machine for the engine limits list
- Spirit for the Engine Limits page
- Everyone who's shown support, contributed with ideas and discussion
- Discuss the current suggested extensions listed below
- Should QSB care about network protocols?
- What about QuakeWorld and specific QuakeWorld features?
Increased Engine Limits
QSB will require some increased limits to bring engines to a more modern level of capability. This is still an ongoing discussion, as some of the limits are incompatible with the default Quake network protocol.
|Limit name||Old limit||New limit||Note/Category|
|MINIMUM_WIN_MEMORY||0x01000000 (16Mb)||0x02000000 (32Mb)||Engine|
|MAXIMUM_WIN_MEMORY||0x04000000 (64Mb)||0x08000000 (128Mb)||Engine|
|CON_TEXTSIZE||16384||262144||Engine (maybe not relevant)|
|MAX_EDICTS||600||8192 (*)||Map limit|
|MAX_MAP_LEAFS||8192||32768 (**)||Map limit|
|MAX_MAP_CLIPNODES||32767||65535 (**)||Map limit|
|MARKSURFACES||32767||65535 (**)||Map limit|
|FACES||32767||65535 (**)||Map limit|
|NODES||32767||65535 (**)||Map limit|
|MAX_DLIGHTS||32||128||Rendering (might be best left alone)|
- (*) = requires new network protocol
- (**) = should be implemented in a non-hacky way (replacing short values with 32-bit ints)
- (***) = Hardware-rendering specific
- (****) = See FitzQuake README.TXT about multiplayer games sticking to 1400 bytes due network limitations
QSB will support the checkextension system, to bring engines which don't already support it up to speed, hence all features will be listed as either existing extensions or new ones will be suggested.
Extensions are listed with descriptions within (sometimes stolen from their respective authors), and a description next to it if the extension differs from the requirement of the standard.
Extensions which make the engine incompatible with the default Quake network protocol are noted with a warning, as this is still an ongoing discussion at the time of writing.
|DP_CL_LOADSKY||pcx with quake palette minimum for software engines, no limit on texture size and texture sizes do not need to match within the same skybox, loads from $game\env\|
|DP_GFX_SKYBOX||pcx with quake palette minimum for software engines, no limit on texture size and texture sizes do not need to match within the same skybox, loads from $game\env\|
|DP_GFX_EXTERNALTEXTURES||required for engines with hardware accelerated rendering, optional for software, attempt to load tga before pcx, pcx before lmp, lmp before wad, loading _diffuse _gloss _norm _bump and _luma are optional|
|DP_LITSUPPORT||required for engines with hardware accelerated rendering|
|DP_EF_ADDITIVE||required for engines with hardware accelerated rendering (ALTERS NETWORK PROTOCOL)|
|DP_EF_FULLBRIGHT||this includes support for fullbrights on textures in maps and on model skins (ALTERS NETWORK PROTOCOL)|
|DP_ENT_ALPHA||full range required for engines with hardware accelerated rendering, software engines round off to the nearest of 25%, 50% and 75% alpha, based on a lookup table. This also includes r_wateralpha support. Bmodels with a water texture and an .alpha value will override r_wateralpha, and use its own value instead, like in FitzQuake. For hardware accelerated engines this includes support for textures with alpha channels on bmodels and model skins. (ALTERS NETWORK PROTOCOL)|
|DP_ENT_SCALE||(ALTERS NETWORK PROTOCOL)|
|DP_MONSTERWALK||(this one is a maybe, because it doesn't make a lot of sense without SV_PlayerPhysics)|
|DP_QC_FINDFLOAT||(note, includes findentity)|
|DP_QC_TRACETOSS||(it seems odd to me that this one needs an existing entity to base on, why?)|
|DP_SND_FAKETRACKS||(is this useful without OGG Vorbis or mp3 support?)|
|DP_TE_STANDARDEFFECTBUILTINS||(depending on type of engine)|
|DP_VIEWZOOM||(ALTERS NETWORK PROTOCOL) (can be implemented as a stat to avoid altering network protocol)|
|FRIK_FILE||the DarkPlaces type, reading inside $game and $game/configs/ is prohibited, writing is restricted to $game/data/|
|FTE_STRINGS||(this one's a maybe, is it overkill?)|
New Suggested Extensions
Some engines already support some of these features, but as they don't exist as extensions, new ones are suggested. Even engines already supporting the features would need to list them as extensions.
Some required features can't be categorized under anything else, they are listed below.
Allows the user to specify multiple mod paths to read content from, with the last in line being the one loaded for play.
Example commandline: -game quoth -game mymod
This would make "mymod" be the current mod in play, but extra content is loaded from "quoth". Extra content is sounds, models, sprites, textures, maps, more?
- Higher precision origins and angles
Use floating point for origins and shorts for angles (ALTERS NETWORK PROTOCOL)
- Render liquid textures of other sizes than 64x64 correctly
- Allow sky textures of 4x2 and higher
- Fix rendering of models with large bounding-boxes disappearing at edges of screen