Teamswitching & Specing Before Joining A Team
UCBPikachuOfLove
Join Date: 2003-08-23 Member: 20108Members
Hey. I don't know if this has been brought up yet, but I'd like to reference it again with 2.1a on the horizon!
A nasty habit I've seen from certain players who are bad sports on both my server network and a couple of server networks I play on are players who F4 out and join the other team once their team starts to lose.
Back in 1.04, you had to 'retry' and manually rejoin the server in order to join another team. Could we get that re-implemented? Most players I've run into are either too lazy/ignorant to know you have to do that to join another team, and I think that might clear at least 50% of the problem.
Additionally, I have seem some unethical players spec at the very beginning of the map, see the Alien starting hive (though I know the comm can 'listen' for the hive still) and what resource nodes they're running towards, then join the marines and spill the beans. Is there any way to implement something such as, when you F4 from speccing back into the RR, you either need to rejoin the server to wait for at least 15-20 seconds before it'll allow you to join a team? That way, your newfound 'intelligence' isn't as recent anymore.
Cheers,
Pika
PS I really wish things would default back to the 1.04 setting where you can't join a team that already has more than one player than the other team (eg., a margin of -/+1). This -/+2 margin, in my opinion, is too large. Not as big a deal for 24+ player servers, but it hurts on a 20 player server.
A nasty habit I've seen from certain players who are bad sports on both my server network and a couple of server networks I play on are players who F4 out and join the other team once their team starts to lose.
Back in 1.04, you had to 'retry' and manually rejoin the server in order to join another team. Could we get that re-implemented? Most players I've run into are either too lazy/ignorant to know you have to do that to join another team, and I think that might clear at least 50% of the problem.
Additionally, I have seem some unethical players spec at the very beginning of the map, see the Alien starting hive (though I know the comm can 'listen' for the hive still) and what resource nodes they're running towards, then join the marines and spill the beans. Is there any way to implement something such as, when you F4 from speccing back into the RR, you either need to rejoin the server to wait for at least 15-20 seconds before it'll allow you to join a team? That way, your newfound 'intelligence' isn't as recent anymore.
Cheers,
Pika
PS I really wish things would default back to the 1.04 setting where you can't join a team that already has more than one player than the other team (eg., a margin of -/+1). This -/+2 margin, in my opinion, is too large. Not as big a deal for 24+ player servers, but it hurts on a 20 player server.
Comments
<a href='http://www.unknownworlds.com/forums/index.php?act=ST&f=8&t=42490' target='_blank'>http://www.unknownworlds.com/forums/in...=ST&f=8&t=42490</a>
nsrandomteam
<a href='http://www.unknownworlds.com/forums/index.php?act=ST&f=8&t=18466&st=23' target='_blank'>http://www.unknownworlds.com/forums/in...8&t=18466&st=23</a>
locked_spectate
<a href='http://ns.punkassfraggers.com/plugins/index.shtml' target='_blank'>http://ns.punkassfraggers.com/plugins/index.shtml</a>
And its the admin fault if you dont use it. Whine anywhere else.
Anyway, I'd find it much more convenient if it were defaulted into NS, which is why I'm bringing it up here. I know that my server network isn't the only one that prefers to keep the plug-ins to a minimum.
Just for the record, I do not think that turning all portals into random team is a good idea. If I want to play as a marine, I'll play as a marine. If I want to play as an alien, I'll choose to play as an alien. I have found very few players who like being 'told' by the server what team they must join. Counter-strike doesn't force you to randomize your guns; if the entire team feels like AWPing, that's legitimate. There are far less extreme solutions to teamstacking issues.