![]() ![]() These values give some idea of how successful a faction is on average playing the individual maps. Some of the diagrams show the difference from the average win percentage for that faction. There seems to be an occasional hiccup on the server side when it comes to map selection, as discussed later in the article and in this thread. a grand total of 32 vetoes between all eight players, so a vetoed map could be chosen. In 4v4, however, there are 13 maps in the pool vs. This would mean that in 1v1s, you never play on a map that you veto. A map that received the least vetoes from all players in this match is selected.The matchmaking algorithm matches players based on their hidden ELO only, ignoring map vetoes.If that is the case, the scheme would work like this: Instead, I think it is more likely that "everyone" only includes the players that are in that game. The process is needlessly complex and yields a worse result.Unless everybody is vetoing the same maps, it would be a common occurrence to play a "vetoed map".In the same thread Kyle_RE says that it would be everybody currently searching the for a match. Unfortunately, he does not specify who "everyone" is. When creating a Match, the Automatcher will only select among maps that have the fewest amounts of Vetoes"īasically, the Server sums up the total number of Vetoes for each map for everyone, then generates the set of maps with the least number of vetoes, and randomly choose one of them. ![]() "A Veto counts as a single vote against a Map. ![]() Just because you have voted to veto a Map doesn't mean you will not play on that map. ! I think there may be a misunderstanding on how Map Veto actually works. Relic has given some information on the subject of vetoes in this thread. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |