Vendor wrote:Not really sure where is the best place to ask about this.If anybody has server admin access to the RBI CTF server, is it possible to get the "respawn delay" countdown thing turned off (or at least considered). My reasons for asking are:
1. It is hard to see why the delay is there.
2. Nexuiz is normally quite a fast-paced game, but hanging around looking at blank(ish) screen for 5 seconds kills the pace of the game very badly. As a player that has rubbish aim, I tend to attack mostly, and get fragged a lot as a result. Keeping the right rhythm for attacks is extremely hard with this delay, and spending a couple of minutes every game listening to "5..4..3..2..1.." is enough to drive anyone nuts!
3. When the teams are slightly imbalanced it throws the balance even further off - the stronger players on the weaker team have to work harder than normal, and thus get fragged more often, and then they have to wait, leaving the weaker team BADLY weakened.
4. I feel like a right idiot frantically pressing my respawn key while the other team waltzes to an easy cap!
My understanding was that this feature was temporarily being tested, and that
once 2.2.3 was out, the server would return to normal, no-delay settings.
Well, that feature was suggested by Morphed. The "pro" points are:
- spawn camping gets much less effective: freshly spawning players come in waves and not all at once; thus a spawn camper has a hard time taking them out one by one. Chances are higher that someone on Face can enter his own base or be on an attacking route while the spawn camper is occupied with the others who spawned at the same time.
- capturing gets actually possible without killing the very same defender TWO or even THREE times. If you're dead, you're dead. Currently it does not make any sense to even shoot at your enemies - you run into the base, grab the flag, and get out as quickly as possible. Anything else is wasted ammo and health, as defenders you killed will be in your way a second time anyway. A higher respawn delay fixes this. Especially affected map: ctf_hydronexb3.
Please use the attached poll for some simple options, or discuss the topic here. Morphed, you too!
Another option could be deciding for a default and letting mappers decide if the values are to be changed on their map. Future Nexuiz releases will have a cvar g_respawn_mapsettings; if set, mapcfgs that set g_respawn_mapsettings_delay or g_respawn_mapsettings_waves will be honored. To otherwise change the values, look at the g_respawn settings in default.cfg; they can be set game mode dependent.
Now, which route should future Nexuiz development go?