Gaijin matches must contain 0-4 top BR players on each side. Does your model accomodate that?
Gaijin matches need to accomodate squads, obeying the rule above.
But what about not so suitable players? How long does a player have to wait for a match? Are they all matched or do they stay in the pool for longer. Did you track all your players in the queue process?
Why do you think different matchmakers lead to fictitious performance and armor values, and other fictitious things? Well, is your point that as soon as Warthunder stops using a ±1.0 matchmaker, the whole game will be full of fictitious information very quickly?
Also, here’s a question you keep avoiding: if a plane will only fight with planes of the same BR as it, do you think that’s fair?
You also admit that until we play those matches with that decompression, we can’t know for certain. So please at least give players a chance to try, at least this request is reasonable, even if it’s on a DEV server?
I think a more compressed matchmaker leads to more compression because the VAST majority of vehicles are perfectly balanced 1.0 BR apart.
Like over 90% of the aircraft in the 7.0 - 8.0 range are balanced to each-other’s capabilities. [The 8.0 Migs and Sabres are part of the minority.]
You’d have to change the BRs of over 2000 vehicles to accommodate your idea, whereas with decompression you only have to change the BRs of a minority of vehicles.
It does alot of the work of decompression, but in much less time.
I think that it is a worse solution than proper decompression, but it takes much less time and effort. Gaijin has shown us repeatedly that they do not want BR decompression, so we need to find other ways to achieve similar results.
A Mig-17 shouldn’t be able to face Meteors/Vampires, but it also shouldn’t be facing supersonic aircraft with missiles that it can’t dodge. A flareless supersonic plane without missiles shouldn’t be facing something like a Mig-21MF. An F-4S shouldn’t go from facing harriers at 11.0, to facing Su-27s/F-15As/Aim-120s. And those 13.0 planes shouldn’t be facing Eurofighters and Rafales.
I agree, but do you really think Gaijin will do that? That also doesn’t solve the rest of the BR compression in the 8.7-10.3 range.
“Gaijin matches must contain 0-4 top BR players”, in my opinion this situation needs to change. The ideal state is that all aircraft in the lobby have the same BR. Gaijin has overturned many things in the past, I believe this is not a big deal, the BVVD era and the Anton era are very different, Anton used to say that there would be no modern vehicles.
In addition, I don’t know what you mean by suitable.
To address your concerns about the number of players remaining in the matchmaking queue, I ran another test:
I tested the number of people remaining in the matchmaking queue after 100 battle matches with the ±1.0 and ±0.7 matchmakers. Since the players are random, I tested each five times
±1.0: 35 11 28 39 18 AVG: 26.2
±0.7: 9 47 31 30 31 AVG: 29.6
±0.3: 60 38 56 58 31 AVG 48.6
±0: 90 115 152 135 101 AVG: 118.6
It can be seen that there is no significant advantage or disadvantage between ±0.7 and ±1.0. At least I think these changes are acceptable. The number of people remaining in the queue is not significantly different when using ±0.3 matchmaker, there are many players who have difficulty matching when using ±0, which is consistent with my previous point of view on the waiting time record. This is also why I first mentioned using 0.7 instead of 0.3/0 in the post title
Do you think the performance gap is bigger among all aircraft between 7.0 and 8.0, or is it just the aircraft within 8.0 that have a bigger performance gap? In fact, it is obvious that the difference between 8.0 aircraft is smaller. 7.0-7.7 aircraft are weaker than 8.0 in most cases. Maybe the difference between them is not big, but we cannot ignore this objective difference.
This situation is amplified a lot in the top tier. Does anyone like to use 12.7/13.0 aircraft without fox3 to fight against 13.7/14.0 aircraft?
Is that on the 10 commandments or did you make that up?
How should I know? You used the word in the text I quoted. Be more precise if you want to prove things.
But that wasn’t my concern. I was asking about the longest time an individual will have to wait, because that is what matters to players. I don’t care how many others wait as long as I wait but I care how long do I wait.
But that isn’t the question in the first place. And that can’t be part of a proof, because there is no agreement on this. I did actually quit modes due to it.
Gaijin’s rule coexists with the ±1.0 matching method. Since we are changing the matchmaker, this rule may also need to be changed appropriately. As for why we need to change the matchmaker, I think I and other players have said enough, including how to prove that changing the matchmaker does not bring a lot of time cost.
In addition, have you read my code? This code can guarantee 0-4 top BR players in most cases.
This is a very intuitive performance. For example, F15A vs F15A and F15A vs I-15, which one is fairer? The closer the BR, the closer the performance, and the fairer the battle. If the closer the BR, the greater the performance gap, the more unfair the battle, or the similar BR cannot determine whether the battle is fairer, then what does BR represent and what is the meaning of BR?
You said “But what about not so suitable players?” Sorry, I just don’t understand what this specifically means.
But what about not so suitable players?
I conducted a new experiment, with other conditions unchanged, to test the average of the maximum and minimum player waiting times in 10 battles. The data are as follows:
±1.0
Average Max Wait Time: 0.931285374832153
Average Min Wait Time: 0.00005259
±0.7
Average Max Wait Time: 1.050368881225586
Average Min Wait Time: 0.00005068
±0.4
Average Max Wait Time: 1.5777560472488403
Average Min Wait Time: 0.000252532958984375
±0
Average Max Wait Time: 3.10342538356781
Average Min Wait Time: 0.0015446662902832032
From the data, we can see that the maximum waiting time from ±1.0 to ±0.7 has only increased by 10%. Do you think this is acceptable? At least I think it is completely fine. There is almost no difference between 10 seconds to enter the battle and 11 seconds.
To be honest, sometimes I want to be more tactful in speaking and not too direct. But I still want to share it with you that he is famous for arguing and opposing with some confusing reason in our language net community.
My point is: You didn’t prove anything, because you didn’t even try to model the current MM rules. Then nothing can be deduced. All you proved is that there are different game algorithms with different results.
You actually proved none of this because you did not include the current model in your analysis.
There is nothing to “read” as your code is undocumented. You know that code usually is documented if to be read by others?
Welcome to the club. Define your variables. When you read your own terminology, you don’t understand it.
If this discussion is to make any sense, you need to clearly state what you actually measure! Throwing numbers with vague meaning around will not be insightful.