You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Not an issue as such but a request as I am not a coder, so I don't have the skills to add this myself, but I do run some Quake Live servers and love this plugin. So big thanks for making this available to us server admins.
Is it possible that when there is a match in progress and there are open spots on each team waiting for two players to join the queue that the plugin checks those two players elo rating before moving them from spec to the match so that it puts the player with the highest elo onto the team with the lowest score?
It seems at the moment it simply puts the player that is number 1 in the queue into the game first and by default, of course, this just puts them to the team with the lowest score, but this person may have a higher elo than player 2 in the queue and it would be better for player 2 to go onto the team with the lowest score instead.
The text was updated successfully, but these errors were encountered:
Hi, Not an issue as such but a request as I am not a coder, so I don't have the skills to add this myself, but I do run some Quake Live servers and love this plugin. So big thanks for making this available to us server admins.
Is it possible that when there is a match in progress and there are open spots on each team waiting for two players to join the queue that the plugin checks those two players elo rating before moving them from spec to the match so that it puts the player with the highest elo onto the team with the lowest score?
It seems at the moment it simply puts the player that is number 1 in the queue into the game first and by default, of course, this just puts them to the team with the lowest score, but this person may have a higher elo than player 2 in the queue and it would be better for player 2 to go onto the team with the lowest score instead.
The text was updated successfully, but these errors were encountered: