` ===re: === Hi again. :*http://en.wikipedia.org/w/index.php?title=Template:Template_category&curid;=6753862&diff;=223660428&oldid;=223290251 :``Simplify, restore basic message without shortsighted and arrogant assumption of types. You were warned. NAVBOXES cannot be defaulted. too many other kinds`` #Why is treating navboxes as if they are a default ``shortsighted and arrogant``? Isn't ``NAVBOXES cannot be defaulted. too many other kinds`` flawed reasoning? #I didn't realize I was being given a ``warning``, only that you were trying to point something out to me. Is it okay to discuss the problem you've found? I'm still wondering why whatever you're trying to do requires fixed numbered parameters. If it can't use parameter names, perhaps a different, more flexible, more forward-compatible approach is needed?    ...  ===Shaking head=== :Why not use Whatlinkshere and SURVEY the many other kinds of categorised by types template pages there are that are NOT Navboxes. Infoboxes, Typing-aid templates, etc. Wikipedia administration templates... the lists go on and on. Defaulting to something NOT plain vanilla means 'instantly those pages are MADE wrong... CREATING WORK, information confusion, AT THE LEAST.  : The original plain vanilla template did a nice simple message... having a ``single overriding mission`` ``This is a Template Category Listing Templates``—that's the only mission that template has, all else is frills.'' All these tricks you installed are just play on your part. SORRY, but as an emperor, you have no clothes on on this matter...  *On flexibility, WHY? What rationale reason can you cite for the time you've already spent on a template whose sole purpose is to alert readers they aren't in a wikipedia category, but an administrative category of some sort. Look at the page history from genesis to last Fall/winter. Play with something that will help the project, forsooth!   *Sorry to seem shrill on this, but you've invested time in something that in the grand scheme of things really doesn't matter much, save for the primary mission, and your changes BREAK THAT and install confusion.   * Adopt this simple rule... if tempted to change a widespread template, change it solely so it still functions the way it was originally applied. See for example the test I did in  several days ago to restore equivalence in here  [I won't go into the fact your changes also broke portability needs to templates on other sisters.] simply because others broke that maxim... breaking original functionality and in the later case, portability. Even common.css changes do thatsometimes. In practice, that means you can usually add a parameter, and logic to handle the difference that parameter implements... but you shouldn't and can't make sweeping changes that make pages ``WRONG``. Particularly those that REQUIRE A PAGE TO CORRECTLY DEFINE A PARAMETER to make your changes operate correctly' You don't see anything wrong with your logic on that basis? God help you if you don't now! That by the way is what I meant by arrogant... perhaps just ignorant of the big pictiure? Hope so. Any more questions? //    `