Hi Pat!
this is not really a bug... but at least it should be optimized/corrected.
// 0 = do not force (default)
// 50 - 300 = max frames per seconds
//set ex_maxfps "0"
// 0 = do not force (default)
// 20 - 100 = max packets
//set ex_maxpackets "0"
Theorecically, maxfps could be in the range of: 0-1000 (disabled = -1?)
The suggestion as "notice" should be the range: 40-333 fps.
The theorecally max_packets are dependends on the fps. If a player has wrong values here, the gaming can feel more laggy as it is.
Here is a list of supported max_package from the game, depends on the fps:
FPS: 333 -> max_package: 333,167,111,83,67,56
FPS: 250 -> max_package: 250,125,83,63,50,42
FPS: 200 -> max_package: 200,100,67,50,40,33
FPS: 166 -> max_package: 166,83,55,42,33,28
FPS: 142 -> max_package: 142,71,47,36,28,24
FPS: 125 -> max_package: 125,63,42,31,25,21
FPS: 111 -> max_package: 111,56,37,28,22,19
FPS: 100 -> max_package: 100,50,33,25,20,17
FPS: 90 -> max_package: 90,45,30,23,18,15
FPS: 85 -> max_package: 85,43,28,21,17,14
FPS: 75 -> max_package: 75,38,25,19,15,13
FPS: 70 -> max_package: 70,35,23,18,14,12
FPS: 65 -> max_package: 65,33,22,16,13,11
FPS: 60 -> max_package: 60,30,20,15,12,10
Under FPS60, it needs a 1:1 ration to max_package.
All other values are ingorned and forced to the next (higher or lower) value. But these can make lag.
Even not all "FPS" are really supported. You can add X as fps, but if's not supported, it is alsow forced to the next value.
Max packets should have a range of 30-100 instead of 20.
These would be "optimal". As "quicker" solution, just change it like:
// 0 = do not force (default)
// 50 - 333 = max frames per seconds
//set ex_maxfps "0"
// 0 = do not force (default)
// 30 - 100 = max packets
//set ex_maxpackets "0"