Thread: Server questions and suggestions

First, a question/suggestion:
Is damage spread on? And if so, is this a requirement for being on the "Play now!" list? And if it is on and not a requirement for being a registered server, could we possibly consider turning it off? I see it as just another element of randomness that detracts from skillful play (like crits).


Second thing, a suggestion:
Could we change the vote keys from the numbers 1-5 to 4-9? I often accidentally vote for a map that I didn't even notice because I happened to be switching weapons at the time (even though my weapon switch keys are bound to the mouse, oddly enough), and I don't always have the luxury of stopping to revote.

This change would ideally apply for all votes (I assume it's part of the same plugin).


I don't know anything about server cfgs, so I have no idea if what I'm asking for are reasonable things. Feel free to let me know if they are not.

To your first question:

"Servers should be running as "vanilla" as possible. In particular, these server tags (sv_tags) will disqualify a server:
friendlyfire
respawntimes
nocrits
norespawntime
nodmgspread
highlander
noquickplay"

It would take us off the "play now" list if damage spread was on.

To your second, the ability to /revote is there for that reason.

To add to what Pimp explained above, damage spread was discussed and debated during the same time we set up a no-crit server about 2+ years ago.

The decision, at that time, was that nodmgspread would not be put into place.

Thanks EBF, it'a always a good day when I have an excuse to look up this thread.

http://www.teamplayergaming.com/game...deo-games.html

Originally Posted by Pimp Trizkit

To your first question:

"Servers should be running as "vanilla" as possible. In particular, these server tags (sv_tags) will disqualify a server:
friendlyfire
respawntimes
nocrits
norespawntime
nodmgspread
highlander
noquickplay"

It would take us off the "play now" list if damage spread was on.

Well, that's unfortunate.

As for the voting, part of the reason I suggested the vote number change is because I've seen it implemented in other servers, so it's certainly possible. That's also the way it's implemented officially by Valve (Voting - Official TF2 Wiki | Official Team Fortress Wiki), although Valve's version uses the F1-F5 keys. I personally prefer keys 4-9, especially since I have my loadout changes bound the the F1-F4 keys.

While the option to revote is certainly helpful, I don't often have an opportunity to revote, such as if we're in the middle of a big push. I have missed the revote window more than once this way.

I suggested it because, if it were a simple change, I think the benefits (of much rarer accidental voting) are much greater than the costs (looking the vote number).

Originally Posted by judedeath

Thanks EBF, it'a always a good day when I have an excuse to look up this thread.

http://www.teamplayergaming.com/game...deo-games.html

Hahaha, bigdog certainly doesn't seem to have an vocal opinion on TF2.

Allow me to summarize the five pages I have read so far: "I don't like it, so it must be dumb."
Now that's an argument I've never heard before. No wonder people were calling him a troll.

Originally Posted by Vulcan30

EBF, I have tried several times over the years for the numbers to be switched from 1-4 to 5-9. It seems everyone is happy with the current system tho...

Not necessarily true. We just havent found a suitable plugin to change the numbers. I believe its just a hack of the core SM plugin as I have seen it on other servers, its just a matter of finding it.

We wont go to Valve's voting system because we lose the versatility of having any other voting through SM.

And FYI, dmg spread will never be changed...

Originally Posted by enf

And FYI, dmg spread will never be changed...

Haha, was this a conclusion from bigdog's thread? I stopped reading after about 7-8 pages.

No, this was the conclusion from several admin discussion considerably longer than and more recent than that thread by people who played the game quite excessively.