I don't know who this vandiril's person is and neither did you provide a link for your source. According to google, every video he has made about Cho'Gath is over year old so you really think they are reliable as sources?
What you are doing makes no sense. It totally lacks consistency with the others Season masteries, and in the near future (Season 2017) might become an unnecessary problem.
Example: We are in the beginning of Season 2017, new Mastery Talents are here. One of this Mastery is named Veteran's Scars. By following LoLwiki logic, this mastery shall be named Veteran's Scars (Season 2017 Mastery) and not simply Veteran's Scars. With the pages that we have right now, it will certainly create conflicts and ambiguous situations.
So I'm asking you kindly to undo your edits and leave the Season 2016 Mastery with the atribute (Season 2016 Mastery).
I wrote a long post about how the present system is against MoS and how mastery pages have their own non-consistent way of handling patch changes thus they are against MoS. Instead this great platform ate my response and send it to /dev/null.
Accroding to MoS and its extension DAB  article names should contain disambiguation only when to make the articel unique from other article's of the same name. In case of mastery pages 'Season YYYY Mastery' is contains redundant information and making hyperlinks more complex than needed. 'Article_name (YYYY)' would instead reflect better the article naming.
When looking information about the game people are most of the time interested about the present state of the game thus there is a prime topic. In light of that the mastery pages that are reflecting the present state of the game should not include any DAB in their article name thus simply e.g. Veteran's Scars.
Other articles in the wiki contain patch section where changes are logged but mastery pages have sneakily developed their own kind of achievement system. Seems like every season gets its own article. To follow the consistency there should be patch section and features that are no longer present in the game are achieved or moved to C:History.
I agree that the naming used might (will) bring problems but for quite different reasons. Should the LoLWikiLogic MoS be followed then mastery pages should have their patch section added instead of creating achievement system working around multiple articles instead of just one. As by its present form it's not consistency with rest of the wiki nor up to speed with MoS.
You bring a real issue to the table. The older seasons masteries. Over seasons some masteries may have the same name, but a new season will require the creation of a new page for the the mastery.
I understand your point of view, and I'm also for the usage of patch history (I'm the person who added Patch History to the Mastery pages).
To solve this problem, we can merge Mastery pages with the same name (but different Season), and merge the patch history ; if this is done properly, this will considerably reduce the number of mastery pages (not counting #REDIRECT).
By doing so, it might also sadly damage the navigation throw older season mastery tree, because for example, if you click on Veteran's Scars of Season Three, you will end up on the Veteran's Scars of the current Season. This is why I think older mastery pages should redirect to the mastery name but displaying (somehow) the Season Three version.
Alright, I applied what you told me to. And ding, I just learned what __TOC__ and __NOTOC__ meant :D (Table of Content), I'm adding this to my tutorial right now !
I'm trying to find a way to enhancify, make more beautiful the presentation of the Patch History over the different seasons, something really significative that show that the patch V22.214.171.124 is only about the Season Three version of this mastery. I don't know how to proceed.
Same thing goes for the "Older versions": what is better for the eyes than a simple Hide/Show tabber?
FFS it did it again. fuck this, I am not wasting any more time for long and detailed answer.
According to teh anynomus numberings,
1. Strict definition will make silly pages. Either they have empty sections or too short sections. Rather use best practice of the article types and let the mlive as needed.
2. My previous post covered that already. Follow the MoS and remove the unnecessarily DABs from articles that clearly are top articles.
3. Linking templates have little to do with the mastery articles. They are fancy but hardly have impact how the pages should look or work. Those templates adapts on the article, not the otherway around.
4. Having a picture with links is quite enough. Make it fancier and you steal articles purpose.
5. Category page shows nicely articles against MoS in regards of DAB.
Thumb or rule, the fancier pages made, the less editors around.
@Tylobic, it's cool.
What about idea of merging patch history and old versions to one section. Then each season section having corresponding patch history. When season changes, then just move old info under new header and start keeping track of that seasons patch impact on that mastery.
A discussion in the Wiki discussions and announcements board might be necessary here to decide if this is going to be the future mastery pages.
Looks nice although I am no fan of pages that bury their own data behind (several) templates. If any of the masters info would change, one should follow the template jungle and fix it somewhere else than in the actual article. The nagain patch history IS collected and archived in the article itself. It's the way those with power in the wiki want to do it and I am done fighting (organization) development windmill's without pay, just saying it's a short sighted policy in a wiki placed platform.
For the structure part I say it again, combine the Patch History and Older versions to one section. As now the patch history section describes in words what is show in length and pictures in the older versions section.
For making a bigger discussion and show about issue is kinda pointless. If it has any (real) issues, then it can be changed. Be bold and go forth. Although I understand your hesitation. The people in power in this wiki rarely want to listen to reasoning. As long it is cool and exactly as Riot has said it has to be The Way®. Never mind how a normal human observes the articles or wiki.
I've removed it. I don't think it's conducive to any good atmosphere here to personally collect every instance of an insult. That being said, if a user is repeatedly demonstrating their inability to positively interact with the people around them, we can do something about that.
It is not offending anyone and it is simply a counter to keep up who is "repeatedly demonstrating their inability to positively interact with the people around them" so that when the 'cup is full' I have easily reference where to point to the admin for the repeating pattern.
If you don't want me editing your personal page, don't come editing mine without grounds.
My own profile page is as non-public/private as it gets. If they get agitated from it I don't see why. It is something that has happened, there is proof where and when, they can't change that. Their following actions determine what is going to happen.