What about giving it the correct seeker? Do you think trying to pull a fast one is really the correct action here?
“Different cooling” that isn’t even modeled in game I’d bet 💀
Please replace “Dutch” with “Belgian”…
I agree, it should be placed in the Benelux subtree.
Gaijin really needs to work on better representing subtrees in naval.
could you consider more about the aim54c+?it shouldnt as same as 54c
Yes, of course. More domestic French vehicles can always be expected for future updates.
Regarding why the F-16 was selected in the first place over a French example for the current Rank VIII premium, here is why: Dev Server Feedback Update - Heavy Cavalry - #72
Ive got my eye on y’all at gaijin with the Abrams
Done. Mixed up my Benelux lmao.
I think they already communicated clear enough that they need classified information…
Perhaps change is needed
Is there going to be any offical general feedback on the CR2 coming?
“modules were planned for everything weather it makes the tank complete unplayable crap or not” - smin probably
RIP everyone who thought it should bring a flakour motor, 50g, mica seeker and whatnot
@Smin1080p_WT is there any chance we see the Israeli ROCKS arm in this major update?(sorry for the notification)
Yeah pretty much, im stupidly surprised there wasnt any sort of buff along with these insane nerfs
With all due respect, France has vehicles like the Mirage 2000 variants that are sufficient to meet those requirements and are actually domestic designs.
Part of what makes this game so interesting is the unique feel of each tree, and A majority of BeNeLux additions have actively undermined that for the French tree. Furthermore, given that pack premiums show up very often in matches due to their ease of access, it further homogenizes games as we will more and more Dutch leopards 2a4’s and (now) Dutch F-16AMs instead of French designs.
I, like many players, don’t agree that the F-16AM is the ideal choice for the flagship French pack premium, and it makes the tree feel like an after thought reserved for the leftovers of other trees.
Clear example that all subtrees except south africa are a reason to easily dump coğy paste while ignoring or in this case, misplacing original vehicles. If they ever drop
Will Germany receive any helicopters equipped with MITL-guided weapons in this update?
Give them MICA and they would instantly be 14.0 and too high of a BR to be premiums, don’t give them MICA and they will be in the 12.3 area which isn’t a kind BR range.
With the Abrams being next weeks’ topic, can you guys revise T-90M (Arena-M)? It’s a T-90M sidegrade with no 4S24 bags instead an active protection system. Folding this variant with the current vehicle and if in the best case scenario making the Arena-M active protection system an modification alongside the additional explosive reactive armor would be much very welcome.
Also, an clarification regarding Yak-130 could help the players understand the massive capability gap between Yak-130 and its italian sibling M-356FA simply denying its air combat capability is unfair in my opinion and if Yak-130M is being considered for the short-term future, since both missiles and countermeasure pods are not present in the Dev Server vehicle but was been shown of these modules being present in the file vehicle.
South Africa has this problem too, with comments for BVVD on how they believed the UK didn’t need the AS-90 due to the G6.
The issues with all sub-trees have existed since South Africa; they just hide them behind being “unique”, despite that doing more harm than good.
We’ve needed something like this since day one of the sub-tree system: Subtree Rework - Nation Folders