Spring RTS Engine

On an autohost, when there are too much specs, the last one arriving is kicked. It is also then case when that player was playing the last game. It's quite unfair if you compare to players that keep specing the all day. Do you think it's possible to have a queue of specs and to kick first the ones that never play ?

nrv wrote:On an autohost, when there are too much specs, the last one arriving is kicked. It is also then case when that player was playing the last game. It's quite unfair if you compare to players that keep specing the all day. Do you think it's possible to have a queue of specs and to kick first the ones that never play ?

You mean that when max spectators count is reached and a player tries to spec, then it would kick one of the spectators to let the player take a spec slot? This would be open to abuse. For example, players could spec (an unspec just after) just to kick a spectator randomly.

bibim wrote:You mean that when max spectators count is reached and a player tries to spec, then it would kick one of the spectators to let the player take a spec slot? This would be open to abuse. For example, players could spec (an unspec just after) just to kick a spectator randomly.

No, I mean kicking first people that don't play (based on any citeria : time, % of last games played, ...)

nrv wrote:

bibim wrote:You mean that when max spectators count is reached and a player tries to spec, then it would kick one of the spectators to let the player take a spec slot? This would be open to abuse. For example, players could spec (an unspec just after) just to kick a spectator randomly.

No, I mean kicking first people that don't play (based on any citeria : time, % of last games played, ...)

It doesn't change anything. Players that play often could spec/unspec quick just for the fun of kicking a spectator who plays less than them.

bibim wrote:It doesn't change anything. Players that play often could spec/unspec quick just for the fun of kicking a spectator who plays less than them.

Then just add a 5 sec timer between spec and unspec they'll loose their spot in game if they try

nrv wrote:

bibim wrote:It doesn't change anything. Players that play often could spec/unspec quick just for the fun of kicking a spectator who plays less than them.

Then just add a 5 sec timer between spec and unspec they'll loose their spot in game if they try

1) The battle isn't necessarily full (spec slots full != player slots full)
2) Hosts can't prevent unspec, they can only re-force spec.

What about when there is maxplayers/specs in a lobby... And one of the players specs, he gets kicked. Meanwhile his playerpot gets filled by a spec/outside player. And he cant join because someone else joined the room and its locked now. This can make people hesitate to spec or just annoy them.

My suggestion is that when a player specs, give him some grace seconds before a kick gets applied? Cancel the kick when his old player spot has been filled by one of the other specs.

Floris wrote:My suggestion is that when a player specs, give him some grace seconds before a kick gets applied? Cancel the kick when his old player spot has been filled by one of the other specs.

I hate spec limit. Can't understand why Zero-k have not player and spec limit and BA have such a brutal rules.

Floris wrote:My suggestion is that when a player specs, give him some grace seconds before a kick gets applied? Cancel the kick when his old player spot has been filled by one of the other specs.

So a spec could avoid being kicked just by unspec'ing/spec'ing regularly every few seconds in the battle?
Honestly I don't think this delayed kick feature worths the time required to implement it handling all side-effects...