Person8880
Reactions
Comments
-
It is already possible for server admins to configure shuffle to occur automatically before a round starts. However there is currently no way to vote to disable it if they do so.
(Quote) This is actually for the most part intended. Each playe… -
(Quote) For sanity's sake, here's exactly what I did (and what the code also did):
4351 + 3989 + 3610 + 2579 + 2447 + 2253 + 1775 + 1179 + 1099 = 23282
23282 / 9 = 2586.88888888888888888888888...
Not sure how you're gettin… -
I don't usually like to get involved in yet another Hive/shuffle thread, but I want to explain the behaviour you're seeing.
(Quote) The average that is calculated is correct. Sum the values in a calculator and divide by 9, you'll get 2586.9 r… -
(Quote) That's a little too small team sizes for it to work well with. It would also depend on whether teams started like that, or whether the players were distributed differently before the shuffle occurred. If they start like that, it won't cha…
-
@Ixian Not sure why you disagreed with me. I wasn't saying "shuffle's teams feel better", I mean shuffle literally produces statistically better teams than what he po…
-
(Quote) Spolier alert: Shuffle comes up with a better composition than you have here.
-
Not sure if this will end well, but I think people are again misunderstanding how the shuffle system works.
(Quote) This punishes players who disconnected legitimately, for example having to go AFK for a few minutes, game crashed, temporary c… -
(Quote) I can do this when I get time, though I'd need to make sure it doesn't clash with NS2+'s scoreboard change.
-
(Quote) I think people will still troll even with the queue. By leaving the game and reconnecting, they throw balance out the window for their team while rejoining and queuing back in.
I don't want to sound dismissive of your ideas at… -
Shine's shuffle already handles most of your points at the start through various options. It can ignore commanders, spectators and move AFK players into the ready room before balancing. It can even be set to automatically shuffle right before a game…
-
That still won't 100% stop the game from potentially starting with only 1 commander.
If you want there to always have to be 2 commanders, disable the pregame plugin completely (shine/BaseConfig.json file, "ActiveExtensions" -> "pregam… -
I will publish an update (when the Steam workshop lets me) that adds the command "sh_alltalklocal_cl" which will allow you as a client to choose whether you can hear local voice chat from the other team.
Just enter "sh_alltalklocal_cl fa… -
The change I made has no impact on commander space bar functionality. It literally changed the voice filter that determines who can hear who, and that's all.
I started a listen server with just Shine installed, and I could use the space … -
The next update to Shine will have a new option under the base commands plugin for this, called "AllTalkLocal", and the command "sh_alltalklocal" to toggle it.
-
(Quote) That means the server you're on is not using the Hive skill mode for shuffling. There's a few legacy modes alongside Hive skill (KDR, score and pure random) which that server's probably using one of instead. It should say when votes are m…
-
(Quote) It is impossible to build a sorting algorithm where the basis is that the data may be flawed. It has to work on the assumption that the data is correct because otherwise there's no point in the entire Hive system. The more edge-cases and …
-
(Quote) I don't understand what you think the difference is between how it works now, and what you propose. A true rookie is going to be a player with a low skill value. Low skill value players will be distributed evenly between both teams, becau…
-
(Quote) This is admittedly a problem. However, the shuffling will output the averages for both teams and I can change it to also output the standard deviation of both teams too. That way, you'd only have to look out for values that seem very far …
-
(Quote) That's exactly how the code is written to work, and tested to work. Have a look for yourself if you don't believe me. Th…
-
(Quote) They'll always be spread evenly, as they're allocated after the players with meaningful skill values have been allocated out. These 0 skill value players fill up the remaining slots loosely based on which team they'll benefit more by past…
-
(Quote) It's the other way round. It will never ignore a swap that lowers the difference in average skill, but it will allow a swap that might increase the difference in standard deviation by a small bit if it still reduces the difference in aver…
-
It's just looking at the current average (and standard deviation) of both teams, and checking whether swapping each possible pair of players reduces the difference in average skill (and the difference in standard deviation if possible). By differenc…
-
I'd like to clear up a few things I read often about team shuffling.
Firstly, there's two kinds you've probably seen. The game's "Force Even Teams" vote, and the "Shuffle" vote. The "Shuffle" vote is from Shine's team balancing plugin (w… -
I've built what I think is the system you were describing. Have a read of this and let me know if it's what you had in mind.
-
Actually, the setting for when both commanders are in their seat is called "CountdownTime", and it's in the plugins/PreGame.json file.
The "StartDelay" option is for after a map change. It forces the first round start to wait for the giv… -
The problem is an oversight in the way the game's checking the config.
Specifically:"auto_team_balance":false
compared to the default:(Quote) It waits 30 seconds after a player has loaded before it starts to measure anything. So their ping should have settled by then.The map vote plugin is an unfortunate victim of feature overload. People just kept requesting more features and the configuration options kept growing.
I have tried to improve the documentation page on the wiki for it, let me know if the…In the console:clear_binding M
That will get rid of the votemenu bind.
Then if you want to rebind the vote menu:I am pretty sure I know why it broke, and it's not an engine problem at all.
In build 263, the function NS2Gamerules:UpdateScores() was removed when the scoreboard networking was overhauled. That function was responsible for updating the…