27 replies to this topic

[R.E.M.]

I've noticed from the thread that people don't have a problem with off-classing,  its more of a problem with constant off classing or off-classing in excess.  I think i good way to mitigate part of the problem would be by having the 6s config limit off classes to 1 each.  This would allow for forward-spawning and off-classing as required and hopefully cut down on off-class only defense.

 

That's sort of the case already. All classes have a limit on them imposed by the config. I don't think there's a way to limit classes so that only 1 pyro or heavy or sniper can exist at the same time you can only limit them to numbers of each (as far as I'm aware anyway).

[The Once and Future King]

 

I've noticed from the thread that people don't have a problem with off-classing,  its more of a problem with constant off classing or off-classing in excess.  I think i good way to mitigate part of the problem would be by having the 6s config limit off classes to 1 each.  This would allow for forward-spawning and off-classing as required and hopefully cut down on off-class only defense.

 

That's sort of the case already. All classes have a limit on them imposed by the config. I don't think there's a way to limit classes so that only 1 pyro or heavy or sniper can exist at the same time you can only limit them to numbers of each (as far as I'm aware anyway).

 

 

Isn't 1 a number?

[R.E.M.]

Isn't 1 a number?

 

Perhaps I wasn't clear. What I mean is you can't make it so there cannot be a sniper and a pyro at the same time or a pyro and a heavy at the same time etc. You can limit people to one pyro per team and one heavy per team but not one pyro or heavy per team.

[naknak]

You can limit people to one pyro per team and one heavy per team but not one pyro or heavy per team.

You can't do it with cvars on a stock server.  

 

TF2C can do it, with the data it already receives, either by twiddling class limits in response to class changes, or by kicking.

[R.E.M.]

TF2C can do it, with the data it already receives, either by twiddling class limits in response to class changes, or by kicking.

 

Well if the developers know how to do it then that's great, I can only comment about using cvars since that's where my experience lies.

[Mahmoud]

there's a new way of griefing going on lately: some1 joins one of the unpopular spots: engie/medic heavy and then disconnects right when the lobby launches or the game starts, and since the replacement for these classes is extremely hard to find the lobby is most likely going to fail!

[Mahmoud]

now im pretty sure there are alots of griefers doing this on purpse. it happens on daily basis

some engi/heavy or medic disonnects right after the game starts, boom flobby!

it's not about the lobby itself it's about all that waste of time waiting for a game to launch!

[TheShortcutButton]

or some kind of enhanced rep that highlights consistently useless teammates.

 

 

 

 

That would make way for players to spot out the bad players that are playing cookie cutter and use this enhanced rep, defeating the purpose of TF2Center. And knowing the 6v6 community they would do it.