Template talk:Unreleased Content

Could this template possibly have optional parameters that say what generation the content in question was added to the game on overseas servers? I, for one, would like an estimate of when we will be getting some new things. --Aljo

I will try making that on other pages. --hawk400206

Suggestion for better redaction

This article Includes contents that may not be Implemented in North America. Some or All of the following contents may not be implemented in the North American client, and the article is based on Mabinogi oversea servers. Details may change before the release.

First line: "contains contents" is producing a monophony. Suggestion: "Includes contents"

Second Line: "Some of the contents" is not covering the entire article if it is future content. Suggestion: "Some or All of the contents"

Second Line: "may not inplemented" is missing part of the verb, "be". Suggestion: "may not be implemented"

Third Line: "before release" missing article "the". Suggeston: "before the release"

These are only suggestions ^^ don't go hard on me... --Sweetspot 17:04, 2 July 2009 (UTC)

Confusing

My suggestion:

This article includes content that may not be released in North America. Some or all of the following contents may not be officially released by Nexon America, and the article may be based on Mabinogi overseas. Details may change before the release.

Not all our contents are obtained from overseas servers. Some are just right in our client, either partially translated or fully translated (such as Friend Summon Capsule(100% Offical Name), which can be ruled as Implemented (in client and server), as the english name and description is done).--黄恒升 ^{☞ 评论 ☜} 18:22, 2 July 2009 (UTC)

I don't think we should consider something implemented in NA just because its info is in the client files. Remember, we want to make it as clear as possible what's available and what's not available for the average wiki user. ---Angevon 18:29, 2 July 2009 (UTC)

In that case, I changed it for compromise. The world 'client' seems to bother me the most, as I view it separately from 'server'.--黄恒升 ^{☞ 评论 ☜} 18:34, 2 July 2009 (UTC)

I also like the above user's suggestion so i will include it.--黄恒升 ^{☞ 评论 ☜} 18:41, 2 July 2009 (UTC)

That looks good. ---Angevon 18:59, 2 July 2009 (UTC)

So is it being changed in the main template? --Sweetspot 13:56, 6 July 2009 (UTC)

Okay, since no-one has replied to this for half a year, im assuming that nobody has any objections. I'm going to leave Angevon a message about it -Kotarou3 10:28, 18 April 2010 (UTC)

Ohwait, i just noticed it has already been changed -Kotarou3 10:40, 18 April 2010 (UTC)

since new skills are slated for August 2013, I'd hate to put at=G18 at August 2013

kinda want it to say "It is estimated that <pagename> will arrive at <generation patch> in <date>." but make the "in <date>" replaced by a period if there's no date announced o-o

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!