Since Servers nowaday keep having some bad configuration in some areas, here a cleanup and advice:

-Maps
Whats a good map and a bad map? Basically the map rotation shall bring difference and balance in game. A map that has a room you only have to hold as team can not be much good. Same goes for map that support long range camping. Long range is kinda critical in q3, since the netcode isn't that exact. Also long range supports camping since as farer away the camper is, as less is the chance to recognise him in time. Another thing are to small maps, which are really ruining team balance. Callvote nextmap doesn't help against people being unable to vote due to bugs and incompetence.

Some examples:
Ospra3map1 - to wide distances, buggy looking through ceilings.
Q3dm3 - Teams have to be equal on this one, as soon as a Team has +1, it gets 100% more difficult for the other team due to pure map control.
Q3dm12 - To many hallways, a person could hide over 2 Minutes on that map.
Q3dm17 - Spacemaps are only for FFA and TDM, using them in Freeze is a ludicrous Idea, because bad Players are kinda causing -1 for a team. Same Problem as on dm3.

-Weapon Config
Basically I already wrote about balancing of weapon configs in another topic, however the Problem is they get updated in way to late. Basically you can Update a Weapon config every week to smarttune it. Nothing of that is happening.
Especially since tactics like fog camping on Overkill exist since years.
Most configs have the fog problem, or weaponswitch problem or weapons people use for moving are overpowered. best balanced config is QL ftag one, since it is most simple.

-Server enforcing settings
Servers can enforce settings since PB is around, basically there is one thing about using such possibilities - Never make it piss of players - the Godfather rule of hosting >_> :
NEVER block people using default quake3 settings. This only causes problems and kills public servers. The default settings were made to grant playable settings for all people running the game. Enforcing 25k rate and 125 maxpackets cause the traffic to go above 12.8kbit Upload on asynchronous DSL, causing every player with a small DSL or DSL light (Sup polish and russian players, that was your guys past.) to be unable to play due to ping 999. Me included.
Basically every Player should be free to pick his settings as long as it isn't negative for any other player. Considering most Servers run sv_fps 30, 30 snaps, 20-25k rate and 42 maxpackets should be minimum. Since 42 lags very slightly 63 is minimum in any cup. Enforcing Com_maxfps is basically a very good idea, since people can lag at will with very low maxfps. However some Players like playing with vsync and other stuff, others have bad settings. Ergo should the range be within 60 up to 125.

Whats up with 125 Anyways? (Only read if you don't know).
The q3 engine is bound to the real time clock, therefor it renders only up to 500 fps, under special circumstance 1000. Above the clock gets problem with the numeration of frames which would instantly crash the game.
Basically physics is mostly calculated client side and it turned out that 125 is the most stable fps amount every computer basically can reach. 125 allows you to jump 48 units high, 333 would allow 56 units. 125 is also synced to any normal USB port. 125 Maxpackets are synced to the maxfps, if your fps drop lower, you don't send 125 maxpackets. settings maxpackets to 63 is also synced to 126, which basically allows sending 2 frames mashed up into 1 packet. THIS DOES NOT MAKE YOU ANY HARDER TO HIT OR BRING ANY ADVANTAGES. If someone enforces 125 maxpackets, you can bypass that by enforcing 111 maxfps. If someone forces both, you can vsync down to 120 or less. Which basically means you can NOT enforce people sending 125 maxpackets under any circumstances. It is just a pain in the ass for the player.

Why I am writing all this?
Basically just pissed about people making wrong decisions. Don't get me wrong, everyone is allowed to do an own decision, as long as he understands the technical background and the practical problems they cause. It is a very big problem in this community that people do not discuss. Basically there isn't much to discuss because people calculated every stupid thing about q3 since 99. Even the floating point hack has been analysed very precisely. So anything people are arguing about has mostly been dicussed already.

PS: Pls don't call me nerd for thi post becaue it is like, everything known roflz.