Category Edit

I like the idea of categories, but that functionality could have been added {{Patched}} without the need for 100+ new templates that are not in sync with each other. Just Alerting You Small Howbizr(t·c) 4:42 PM, 6 Oct 2009 (EDT)


  • about Template:Patched
    • about the new system
  • add new patch by figuring out where to put it in Template:Patch
    • add a new patch by copying an existing patch template
  • Template:Patched has become hard to maintain, with code for special cases that is not obvious
    • With a template for each patch, one category of special cases (the 1.1 vs. 1.10 issue) is eliminated, and special cases have their coding where they are needed, not in the central template (see Template:Patch 4.0)
  • long switch statements are inefficient
    • two short templates with no flow control logic are efficient in terms of memory and CPU usage
  • Template:Patched is transcluded on more than 5000 pages, all of those need to be updated when a new patch is added, creating unnecessary server load
    • Since adding a new patch means creating a new template, only those pages need to be updated that are actually affected by the patch
    • The "WhatLinksHere" on the patch template can be used to quickly find all pages affected by a certain patch
      • This functionality could be fitted to Template:Patched by auto-cateorizing articles
        • This would require extra logic to not create categories for unknown or invalid patch numbers, thus making that template even more complicated
        • adds a lot of categories for some pages, thus cluttering the category list
  • Everything is in synch if you only use one template
    • The display uses Template:Patch for all but a few special cases, and as such is in synch as well
  • Easy to maintain because everything is in one place
    • Easy to maintain because templates are short and clear

In short, using several templates is more efficient; a new patch template can be easily added by copying one of the old ones and adjusting the obvious info, rather than editing a template that requires a higher level of understanding of template code to use correctly.

--◄mendel► 17:04, October 6, 2009 (UTC)

I note that {{patched}} is not in this category. However, it requires a bit more intestinal fortitude and interest than I have to edit Patched (and thus the myriads of pages dependent on it). I find the new scheme simple/elegant, but I can echo the distress at the explosion of individual templates. --Eirik Ratcatcher (talk) 19:32, October 6, 2009 (UTC)
If you've seen one, you've seen them all. ;)
Template:Patched is not in this category because it doesn't work like the templates in this category. (And neither is Template:Patch).
I agree that what's missing from my list is the (organizational) cost for editors to adapt to the new scheme. --◄mendel► 22:33, October 6, 2009 (UTC)
True, but if you've maintained one, you've not maintained them all. You do blow off the "now you have to edit 90-some-odd templates" as a down side for maintenance. --Eirik Ratcatcher (talk) 17:30, October 7, 2009 (UTC)
The maintenance that is certain to be done on this system is to extend it with each patch, and that process is becoming a lot more stable with the new system. --◄mendel► 00:07, October 8, 2009 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.