Fun - Most Obscure Quake Bugs

[mh]

I thought it might be fun to list the most obscure Quake bugs you've ever seen; just things you've noticed while playing around with the source code.

The more harmless the better; I mean the kind of bugs that don't actually make the engine crash & burn, or that don't really affect gameplay, but just shouldn't happen. The kind of bugs that would get shoved so far down the bottom of the priority list in any professional project that it goes beyond being not even funny and back to being funny again.

I'll start:

SCR_CenterPrint - the server sends a blank string from time to time. I noticed this a few months ago while playing around with putting a textbox around the string, and was bemused (and amused) to see loads of small empty textboxes popping up on my screen here and there. The obvious solution is to check for if (!str[0]) at the start of the function, but sometimes I wonder if fixing this takes away from the rickety charm of Q1.

[LordHavoc]

[MauveBib]

[Urre]

[LordHavoc]

[mh]

[LordHavoc]

Here's one:
tracebox - the builtin exists but has no code (except in enhanced engines).

[KrimZon]

[mh]

[LordHavoc]

[mh]

Fine but it ain't a newline, it's an actual empty string (str[0] == 0) and it happens a lot even in ID1.

Unless I'm missing something here...

[LordHavoc]

[MeTcHsteekle]

i think mh is talking about when your walking along in a map shooting things in the face, and suddenly you hear the chat beep, so you bring down the console, and if the engine dosen't outline centerprint messages [assuming it records centerprint message] that it will have a blank space at the bottom, but if it does, you will have 2 lines..shall i call them dividers on the console

wait, now im confused :S

[mh]

[Chris]