...
I agree with your sentiment about CB, but you are missing the point in quoting me. What I tried to make clear to you is that the post you were quoting is referring to the tracking behaviour only, not CB itself. So please if you use this post as a basis for response, then refer only to the tracking as well because that is the main (only?) thing I was referring to. I am also not connected to Sanders or the balance team at all, and again you are referring to CB in general which I tell you now for the third time was not my point at all.
For all we can assume the tracking is difficult to abuse and an overall rare event. Please provide some reasoning why you think this occurs so often. My reasoning is that in almost all cases Allied barrages fire for so long that the LeFH will turn and CB trigger before the unit has left the cone. And even less likely be back in base.
The Elefant is not related. Even at 320 damage, it was working as intended. It is just stupid design. The tracking is not working as intended. The Elefant is - if at all - related to CB itself, which again was not the focus of my post.
And one note repeating what I already said: The tracking does not make CB stronger in a sense that CB is suddenly stronger this week in contrast to pre patch or before. The feeling of strength of CB that you get when using or receiving it is exactly the same. It's more akin to finding out the Riflemen nade had increased damage on every 100+th nade thrown. It were a stupid bug that should not happen in the first place. Yet having this knowledge did not make the nade suddenly stronger. If the ability is seen as too strong it is not due to something bugging out once every blue moon (slight exaggeration for clarity). If the ability is seen as overall bad design it is also not due to something bugging out once every blue moon. The ability had the same strength before and after gaining knowledge of the bug.
Divorcing CB and the tracking bug implies no status on either of these.