Inner Mysteries of Quake: key_dest, console

[Baker]

1. Menu.c does something heinous. If you exit the menu, it sets keydest = key_game. At first thought, it should return you to whatever the keydest was when you entered the menu. That actually isn't perfect either ... you could be playing a demo and the demo ended or you could have been connected to a server and got disconnected somehow.

Either of those, I think cause a CL_Disconnect. So CL_Disconnect should tell the menu whether or not the game has ended and menu.c should, upon exit of the menu, return the keydest to the previous state if (and key_game if the game is still running otherwise do key_console).

2. The Loading Plague.

Mysteriously, you can't do this if not ca_connected. I bet DarkPlaces does. Particularly noticeable with the FitzQuake protocol loading a gigantic map.

3. The stupid between map showing of the console for a split second in DarkPlaces. I get this in my engines too. It occurs, for example, between the start map and e1m1. I see it for just a microsecond, it annoys me. I'll track down why it happens.

4. Spike thinks engines shouldn't write configs in gamedirs. I agree. Furthermore, I don't think engines shouldn't support -game from the commandline at all But at the moment I can't remember my reasoning. Instead it should be +gamedir <whatever>. [But not for an engine like DarkPlaces/FTEQW that supports games radically far from the Quake tree.]

5. MH said something about how he didn't like his cvar support of hipnotic/rogue/quoth/nehahra. MH ... what was the shortcoming about that if you don't mind explaining?

[6. Why isn't there a stock add "Nehahra support to an engine tutorial" or was there once upon a time maybe in the form of the Nehahra engine?]

[revelator]

[Baker]

[andrewj]

[Spike]

[revelator]

[qbism]

[Baker]

[revelator]

[r00k]

[Chip]