Talk:Addoninfo.txt

So much useless data

This page, before i had modified it, contained a whole lot of useless data.
The entire "Specification" section was borderline useless. First it had to define what the words "shall" and "should" mean, instead of just using the words "you must" and "you should". Because that's english and everyone reading an english page understand what english words mean.
Nevermind that stuff like "You shall have at least one KeyValues block.", and "You should define the name of the first KeyValues block as AddonInfo." Yes, of course. Because that is literally what this file is about. That's all it has and all it does.
It would save way more space by just writing "Copy this example into a file and change the name and tags to your liking". And the "valid addon info keys" table that defined that the "addontitle" key is the title of the addon is redundant too. You could just have the example there and write the description as comment into the example. Oh wait, we already have that! Plus, why using external links to different websites to explain what "wchar_t" is, instead of just linking to our own string page?
I've also removed the code blocks around every god damned word. All these black boxes highlight things that have no reason to be highlighted made the page hard to look at. Why should addoninfo.txt be highlighted on its own page?
Maybe i'm just ranting, but there is no reason to write a whole awful lot of text that can be summed up in a single sentence. This is not an essay where you need to pad the word limit. In fact, the less data to read on this simple text file, the easier it is to understand. What this page should be is "This file must exist, copy paste this example and swap the name fields and tags". But instead we had "You must use the file with this name, encoded in this specific type, using keyvalue blocks of these specific names..." That's silly.
--MrFunreal (talk) 12:30, 13 March 2024 (PDT)