FitzQuake and Enhanced GLQuake have a lot of limit breaking messages. Enhanced GLQuake has a lot of warnings about models and such.
What is a good "developer" cvar scheme to manage what someone mapping or modding or engine testing with some sort of clarity?
developer 1 or 0 is too simplistic.
Anyone know a good scheme or idea for controlling the type of developer messages that print to console that someone wants?
Someone doing QuakeC-only might want X, someone mapping might want Y, if you are testing network protocols you might want Z. Etc ...