Documentation

[ouned]

• reflists
• API
• clientside cvars
• external http downloads
• dynamic glow shaders
• MVAPI_LOCATE_GAME_DATA
• ui_menulevel
• ingame_setup_modoptions
• ent's recording options (all cmds and cvars are documented already)
• MVF_NOSPEC, MVF_SPECONLY
• MVAPI_DISABLE_STRUCT_CONVERSION

[aufau]

Undocumented clientside cvars:

• com_busyWait
• r_ext_texture_filter_anisotropic
• s_sdl* cvars
• New r_* cvars from SDL
• New in_* cvars from SDL
• r_ext_multisample (OpenGL doesn't load when I set it, is it ready?)
• r_fontSharpness
• New net_* cvars
• r_textureLODBias
• r_consoleFont
• con_height
• con_scale
• con_timestamps
• cl_autoDemo
• cl_autoDemoFormat
• cl_drawRecording
• … more? Feel free to edit this post and add them.

Probably too ambitious for 1.2.
I propose to keep the wiki page in alphabetical order.

[ouned]

i wouldn't go for documenting all of them as some are pretty obvious anyway

[TriForceX]

+1 for @aufau
i think all new cvars need to be documented, not ingame, just in documentation (wiki, readme, etc...)

[aufau]

Maybe their meaning is obvious, but their existence is not for someone who has been using jk2mp.exe previously. We don't stick consistently to mv_ prefix and it doesn't make it any easier.

[aufau]

And client commands:

• saveDemo
• saveDemoLast
• minimize
• Alt+Enter bind

[aufau]

I pushed CVARS.rst with full list/description of new and modified cvars. Left some undocumented (but listed!) as they are not really worth documenting. Please update it when you change something. I think client/server cvars should stay split in the wiki as they are now.

[ouned]

what about avi recording? I think it should documented, too

[aufau]

• avi recording
• VM profiler

[ouned]

• API Level 2

[aufau]

• API Level 3

[ouned]

• ent files