*Reminder* Too many pk3s in path cause trouble/server crash
Update: This file is kept as reminder - we can’t fix this
You should get a warning at start when pk3 limit is reached.
I’ve had a crash when I did start a listen server by the menu. This happens when game pathes are populated with tons of pk3 files.
Actually there is a direct known limit: the size of CS1 (8192)
CS1 stores all the pk3 information and when this info size is over 8192 chars we are in trouble. I my case the pk3 including our campaigns wasn’t loaded. Since we don’t know in which order all the pk3 info is put into CS1 and any other pk3 might be affected too - this error is flexible. For example: A missing shader data pk3 info will cause gfx glitches.
Print a warning/don’t start the game when the real used size of CS1 is reaching our limit
Add an additional CS when CS1 is overloaded ... This increases the configstring in general (network!) and might break 2.60 compatibility.
#1 Updated by Mateos about 5 years ago
I’d go for Option A, localhost crash happens with not that many PK3s, but when you have even more it can crash the client on a map load...
Basically "couldn’t reopen <insert main game or mod PK3 file>".
Regarding option B, I don’t think it’s a good idea, but exclude any file without a BSP or SCRIPT file?