Is it feasible to adjust the BR float to ± 0.7?

Because both options are trying to solve the same issue, so logically most people pick one or the other as otherwise you just end up with the worst of both worlds.

WoT still has +/-2 MM spread, what change did they make to prove your point?

Having a nice round number 1.0 is simply more intuitive, you can just add or subtract 1 to your current BR to tell what you fight; yet lots of new players still don’t get it.

By comparison 0.7 feels more arbitrary. It’s also inconsistent. If you have a 5.7 vehicle your actual BR spread is -0.7/+0.6 unlike 1.0 which is always consistent.

Will experienced players have a problem understanding it? Probably not. But if new players struggle to get their head around 1.0 spread the. 0.7 spread certainly won’t make it any easier

3 Likes

I am quite certain they limited it to +/-1 but back when I played it was +/-3 so it is still smaler than WT`s even if I am mistaken.

ok that is true, but changing a number around like that is also not much work.

lol . . that is not how it works at all, the MM’er can only work with what the players have in queue, it cannot “make up” teams with vehicles/line ups that are not in the queue, a game that consists of 7.0 - 7.7 is a 7.0 - 8.0 BR 1.0 spread game. Just because there are no 8.0’s in that particular game merely means that the MM’er found others, of different BR’s to fill out the teams and started a game. It in no way means that it made a 0.7 game . . . c’mon. I understand your desire for a smaller “spread” but going completely off the rails because you “want it” will not help anything or even make it happen. I play games with a 4.3 line up in AB Air and see games with just 4.0’s & 4.3’s in them from time to time . . reason? A lot of players queue up those line ups at times and it happens, it is not by any “design” it’s just luck of the draw. The MM’er is pretty basic or even simple programming, but it has to have limitations . . . again, there is only so much it can do within the parameters it is set to. Trying to rationalize your wants/desires is not really a strong or valid point to use for making changes, making “demands” doesn’t work very well either. Maybe try listening to/looking at others point of view and possibly find a working, common ground. I don’t care if they lower the spread or not, I can manage it as it is now, but if they made it better, I’d go for that too. Just basic common sense . . . it’s a game, if you have soooo much trouble with the uptier/dowtier stuff, maybe it’s no your kinda game. Just go out & shoot the red guys and try to have fun . . . pretty simple.

1 Like

Most of the time when I debate 0.7 BR spread with people their answer is along the lines of “Gaijin have refused to meaningfully decompress BRs, so we should seek 0.7 BR spread as a simpler alternative”.

It is that sentiment I was responding to (not from you personally - notice how I wasn’t replying to you).

It is currently +2/-2 and as far as I can remember has been that way for the 10 years I’ve been playing.

No. That is not true. As I stated it existed like that in the groudn beta years ago.

if the spread is 0.7 in a match then it is a 0.7 match… Like come on.

Any MM is just a numberdrawer by design. They usually consist of less than 100 lines individual of code. more often around 50 if they have to work with just one singular form of number as is the case in WT. The base model for it can be found on GitHub and I am fairly conmvinced gajin used such a model because everyone else does. As I said changing it from a 1.0 to 0.7 is literally changing a single line of code.

Every single day i see people quit when they are bottom tier (I do as well in most cases). Every single day I see people showing why their tank should not meet x y or z +1BR higher than tehir tank. Every day I face enemies I never should face. Every day I get to slaughter 5.7s in my T26E5 which can not go to 7.0 because of its piss poor gun for that BR.

And every single time The conclusion is the same. many don`t struggle with tanks 0.7 above them unless they are like the T26E5 or Maus, but many do with the +1BR.
Gajin has been moving tanks up by 0.3 killing off half the swedish and british techtree so zje lower end 0.3 would not suffer any longer.
All of that could be fixed by 0.7 or a two step MM spread instead of the +/-1 or three step one we have now.
Taking the next BR changes as an example. Every 0.3 increase would not need to happen or could be 0.7 increase. the O.7 increases could be further divided in 0.3;0.7 or even 1.0 increases making it all less bunched up. This would significantly decrease the amount of vehicles in need of change. freeing up gajins power to also look at 9.0 to 11.7 and extending that range to not simply shift the compression up but actually decompress the trees for once.

That is why I am bringing it back up now. Because right now would be the ideal time to implement such a change. gajin is already looking at decompression so why not do it right and use all means we have. What is done now only created a mega compression at 8.0 to 10.0 the likes of which we have never seen.
Gajin needed to move tanks which should never meet 9.0 tanks to 8.0 because these tanks caused havok in 6.3 and 6.7 games. And having now moved their claimed 300+ vehicles (I have not counted) around left no room for the 9.0 to 11.7 vehicles which will follow probably in another 6 or so months.

and where is that relevant to the matchmaking spread. Everything you listed is still fully in the game even afte rlimiting the spread it has nothing to do with it whatsoever in this case.

but you will have no more than 1 vehicle per BR once done. good job preserving the lineups and diversity of a game when between 21.0 and 22.0 the US has 1 abrahams germany has one leo 2 and russia has a T90 while everyone else has nothing until 20.0 and 22.0

Why? Gajins official marketing numbers are and I quote “Over 2000 playble ground,air and naval vehicles for you to play”

Hä?

No

  1. You can either: Write a script, fill a spread sheet with numbers based on your stats from the game and then click a button to change the numbers according to the spread sheet.l Then you repeat every three months from scrathc as you hope your script still works
  2. Or You change a single line of code. Monitor like you always did and change stuff around every thre months like you always did.

I see no real difference in the work load but option two is much more profound and attacks more issues at once.

Ignoring the stupidity of your statement, as retaining good features of an older system is infact a positive point when integrating new stuff. It is not less percise. You still have 100% the same tools as before just not as many variables to consider making the process of decisionmaking easier and more streamlined. So it has 100% the same tools but is more efficient to use. So it gets better.

Space remains unchanged. we will still have the 1.0 to 11.7 BR range with all normal steps. a 0.3 change in BR is just as fine, if not finer than before. Why would it not be? If a vehicle performs to well against its lower spectrum of the MM you move it up and thats it. How is that less percise? Where is a move from 6.7 to 7.0 to remove 5.7 from the MM pool more percise than moving from 6.7 to 7.0 to avoid a vehicle meeting 6.3?

where am i jumping half steps? Nothing about the BR`s changes. Not a single vehicle will need to be touched with the change. In fact no vehicle should be touched for a short while after the change top gather data.

As stated it is not more delicate it can not be.

Look at the post again and just try to use simple multiplication by 10. Than have long though about what you wrote.
You might as well look at the spreadsheet provided and again think about it.

Because right now you are failing in math from primary school.

No I do not think so.

Yes you are. Think really hard about the ±10 and 120 example I provided.

I will now have 8 hour or so break and I will respond in detail then.

1 Like

you mean your stupid argument that you can have the exact same balancve by giving the game a 120BR range? To which I obviously answered that you would destroy every single lineup, or even the concept of a lineup by doing so?

Man this only hurts.

All this “Argument” confirms is that just increasing the BR`s will lead to this exact issue. The narrowing of the MM wants to avoid destruction of lineups as much as possible while also fully adressing the compression issues. Your entir point proofs that we need a more narrow matchmaker

3.7 gets into 3.0 and 4.3, simple. and it’s not a perfect 0.3 increment anyway, .3+.3 isn’t .7 dingus.

Look, here’s the argument for 0.7 base matchmaking you are so blatantly fail to understand.

there’s a big gap of performance between 10.7 plane and 11.7 plane, between these two, one has AIM-9B / R60 stock and basic lock radar with minimum sweep range and speed, while the other has AIM-9E / R60M stock and pulse-doppler radar and SARH launching capability.

limitting the matchmaking to 0.7 maximum for up and downtier ensure that these 10.7 plane doesn’t have to face off with 11.7 hellspawn with different technology altogether, so is the 9.7 plane without flare and tier 4 missile modification doesn’t have to face 10.7 plane with AIM-9B stock and CM pods and afterburning J79 or R11 against their weak ass J47 or VK-1.

3 Likes

10.7 & 11.7 can face each other rather fine, there’s barely a gap.
You should’ve mentioned 9.3 where compression actually is.

Adjust BR float to 0.7 can solve most of the overperforming/underperforming problem. Now the playerbase is more than enough to support this change without much lengthen the matchmaking. (While Gaijin still unwilling to do this, maybe because this would influence the selling of prem packs)

1 Like

BR 1.0 is required for decompression.

I think you haven’t understood what we’re talking about yet. we are talking about IN-GAME MATCHMAKING BR FLOOR AND CEILING, not OVERALL BR FLOOR AND CEILLING.

Sure we need a 15.0 BR ceilling, agreedm everybody love that. But we also need matchmaking that limit the enemy / friend BR limit to just .7 to prevent an entirely new technology that was developed with more knowledge of legacy technology + Implementation + Battlefield performance + years of development to pubstomp weaker vehicle.

The spirit of decompression is to prevent vehicle from advanced generation to fight vehilce from previous generation, and while BR ceilling increase is a correct way to fight it, more need to be done to actually address the problem that -+1.0 BR brings to in-game match where it’s matter. the .7 matchmaking increments is aimed to precisely fix the specific problem of 1.0 matchmaking BR ceilling brings to the game.

1 Like

Let me lay this out for you.
Let’s say 4 BRs are compressed, and 8 are not.
Under a 0.7 system, you have to compress 8 BRs into a worse matchmaking system.
It causes compression.

OR you could just decompress the 4 BRs and move on.
In reality, it’s closer to 2 total BRs that are compressed out of the 12 total, maybe up to 3 tho I’ve yet to see math that proves that.

You can just add more BRs to prevent entirely new technologies from facing F-104A.

Compression affect around 4-ish BR range starting from 8.0, from there they will absolutely forced to fight misileer with afterburning jet engine 1.0 BR above them.

How to fix? just literally just limit matchmaking to .7 BR, 8.7 can only face up to 9.3, 8.0 doesn’t have to face 9.0 missileer, 9.7 doesn’t have to face 10.7 CM and SARH, 10.7 doesn’t have to face pulse doppler SARH and all-aspect.

simple as.

1 Like

That doesn’t fix anything, that causes less movement for balancing without solving the problems.

compression is when vehicle with far and wide performance gap is at 1.0 BR range, this is the case in all tier even starting with 1.7 BR.