分房系统详解 毛子想得还是很周到的
Helloeveryone, So,you’ve seen the MM video, right? If you haven’t, you should, because this postrefers to it. In order to repeat what was in the video though: 嗨熊孩子们，你们已经看过有关分房的视频了，对吧?如果你没看，你该去看看，因为以下内容都是与之相关的 - there is a possibility of the MM to create non-standard teams. The amount ofsuch battles should not exceed 5 percent from the sum of all battles, but inconcrete situatios this number can vary in accordance with the theory ofprobability. For example, if you played 10 battles with IS-3 in a row and in 3of these battles you encountered a breach of the “first 5 slots” rule (tiers oftop 5 vehicles were not equal), it’s not a MM error and it most likely won’trepeat itself in next 10 battles. - 有可能分出一个不标准的队伍，这种情况应该不会多于总场次的百分之五，但总的来说，这种情况的数量变化是符合概率论的。举个栗子，如果你连续打10场-3，其中3场违反了“前5槽”原则(前5槽原则，排在队伍最前面的5辆车级别应该相同)，这并不是分房系统的错误，并且在接下来的10场里它不会重复(这样的分房) - the MM tries to align the team composition with the current state of queue, sothat in cases, where the team composition is non-standard, the template forselection of tanks into teams can be significantly different from the defaulttemplate (used when the server is started) (SS: if you remember the video, itis stated there that “weird” battles happen for example shortly after serverrestart, but in fact before the templates, based on the queue are formed, theserver uses a “default” template for team building). - 分房系统试着从等待队列里选出匹配的对战队伍，所以，有时候会出现“不标准”的分房，选择坦克进队伍的模板和服务器的最初模板(在服务器刚启动的时候采用)有很大的不同。(SS：如果你还记得那段视频的话，它说在服务器重启后的一小段时间里，分房会变得非常的诡异。在等候队列形成之前，服务器用的是默认建队模板) - Statistics of played battles does influence the default template from the firstminutes and as soon as in 30 minutes, the template corresponds to the currentcomposition of the queue and “keeps track” of the changes in it. For example,on the test server the queue might be filled with vehicles of one type theplayer joing the queue with and it’s possible to notice that there are more andmore of these “popular” tanks and their waiting time gets lower and lower. - 在第一分钟到大概第三十分钟，已经结束的战斗数据确实会影响默认模板，模板根据目前等待队列里的车辆成分做出响应，并“追踪”相应的变化。举个栗子，在测试服里，队列里充满了某一特定车辆，分房系统就有可能注意到了队伍里有越来越多的热门车辆，同时缩短他们的排队时间。 -If the vehicle stands in queue for more than one minute, the matchmaker triesharder to push it into battle, reducing the team composition requirements. Butthere are 30 vehicles entering the battle (2 teams with 15 players), so even ifyou wait less than one minute, you can still get into the battle, in which theteam is composed in order to push the long waiting player in. -如果某一车辆在队伍里等待超过了1分钟，分房系统就会更努力的把他丢到战场上去，此时就会降低队伍组合的需求。但是一场战斗要30辆车(两队，一队15辆)，所以即使你没等到1分钟，你也能被拉进战场，因为系统急于让那个等了很久的人开始打。 - There is one more reason forthe appearance of non-standard teams: platoons. If the platoon consists ofvehicles of one type (for example three tier 7 heavies), the MM easily picks ateam for such a platoon. And if the platoon is a “trollplatoon” consisting ofone tier 10 and one tier 2 tank? The MM can correctly handle even thissituation, but the composition of both teams will likely be non-standard. - 还有一种出现“不标准”分房的原因：组队。如果是同一类型车辆组队(举个栗子，三个7级ht)，分房系统很容易对付。如果是逗比组队呢?比如一个10级车带一个2级车?分房系统仍然能正确的处理这种情况，但是会使得双方的队伍成分看起来都“不标准” - And there is one more type ofplatoons, for which the MM can make non-standard teams: platoons that haveartillery or scouts in them. These classes of vehicles have their own MM rulesand platoons with them should not break the MM rules. - 还有一类组队导致不标准分房：队伍里有火炮或者侦查车。这类车辆有自己的分房规则，即使组队也不能破坏这个规则 (侦察车基本上包括4级和4级以上的所有轻坦，除了美国的M5斯图亚特、法国的AMX 40、苏联的T-80和英国的所有轻坦。)
|
本资讯及文章仅代表发表厂商及作者观点，不代表叶子猪本身观点！
