Tweak

I looked at the Upcoming Content category and saw that the auto-category-sorting feature of the template wasn't really getting much use anymore. The only one that survived was Upcoming Content at G14.

I don't know the nitty-gritty of MW templates (acronym duality!) but IMO we should drop the custom category label feature, leave "Upcoming Content" and split the 'at' parameter into two. ('prep', 'when')

This may be the cunning linguist in me complaining about reading "at June 22, 2011" on the Dragon pages but it seems a lot more versatile in my head i.e.

We don't know when we're getting something: {{FutureContent}}
There's an event we've got info on happening again: {{FutureContent|on|Feburary 34rd, 2952}}
For features in an upcoming patch whose release date is unknown: {{FutureContent|with|[[Generation 25]]}}, {{FutureContent|in|the [[Generation 25]] update}}, etc.

Edit: and because you're probably thinking by now that changing the template is a horrible, horrible idea and would muck up pages all over the place, single-parametered usage could remain backwards-compatible while you'd be able to write new pages with the prep/when syntax.

Or that could be a horrible idea altogether and a better one would be to just let the template user take care of the preposition (with a teensy-tiny edit). Either way I think the auto-category is probably past its time though.. Whee, rambling. Good to be back.

Sounds good to me. Although, I think this might be a simpler solution:

{{FutureContent|at=February 34rd, 2952|Category=n}}

I'm not sure if we'd have a multi-generation gap between NA and KR again, but it is a possibility. (An unlikely one.)

Honestly the vast majority of cases where the template is used are on item pages from overseas servers where there aren't any plans to bring them over. (And looking briefly at the category page, I see some cleanup I could do! :D)

The template works fine, parameterless, for anything without a known date. So that's not an issue. And we're caught up to KR for the moment, which is why I think it's a good idea to make the template accommodate pretty much any point in the future (whether that maps to a calendar date or not), and maybe if there's enough content coming at once that it warrants a category (i.e. a generation update) a "clone" template could be used (FutureContentG15, for example).

Mooooar rambles!