A copy of text sent to the server console by the Quake 3 engine should also be sent to the game DLL.
Advantage: This would allow game DLLs to be able to tap into engine output, either to forward output to remote server consoles, or perhaps for fancier logging of error messages.
Disadvantage: None that I can think of.
Effort: Fairly easy - just add another function for the game DLL to export, something like: void (*ServerConsoleOutput) (char *text); Call this function every time an internal Q3 routine needs to write something to the server console. Game DLLs that didn't care about server console output could just to a no-op and return.
Comments: I think it would be important that this function is -only- called for text output that came from inside Quake3. Text generated by the DLL itself and passed to Q3 through something like gi.dprintf() shouldn't be echoed back through this function.
April 13, 1998, submitted by Barry Pederson.