利用者:Crtke/Sandbox/3

提供: Minecraft Wiki
移動先: 案内検索
ショートカット
MCW:STYLE
MCW:SG

この記事では、Minecraft Wikiにおけるすべての記事が従うべきである包括的なスタイルガイドを提供することを目的としています。 どのスタイルルールまたは書式を使用するかについての議論がしばしばあるため、公式のスタイルガイドはこれらの議論を解決し、合意に至るのに役立ちます。

ウィキペディアでは既に、より一般的な表記ガイド英語版を提供していますが、具体的なMinecraft特有のガイドラインが必要となります。よって、ここではMinecraft Wikiとその基本となる書式の規則に関するガイドラインのみが含まれています。

注意事項[編集 | ソースを編集]

ショートカット
MCW:NOTABILITY

メインの名前空間での記事は、以下の基準を満たす場合にのみ作成することができます。基準に合わない記事は、予告なしに削除される場合があります。

一般的な注意事項
  1. 記事には、ページ全体の正当性が保証されるだけの十分な情報が含まれていなければなりません。内容が不十分である場合は、他の類似した記事へ統合する必要があります。
  2. 記事は、何らかの形でMinecraftに直接関連しているものでなければなりません。
  3. 人物に関する記事は、その人物がMinecraftの開発者である、またはMojang ABの一員か深い関係にある場合にのみ作成することができます。
  4. 現在ゲーム内に存在しない要素については、言及された要素で記述しなければなりません。
    1. ただし、ゲームから削除された要素や、開発中のバージョンに存在する要素はこの限りではありません。それらの要素により影響を受ける記事、および関連するバージョンの記事に、その要素についての記載がある場合があります。
  5. Minecraftのバージョンに関する記事は、リリースされたEditionごとに作成し、各開発版に関する記事も別の記事として作成しなければなりません。
    1. リリースされていないバージョンに関する記事は、原則作成することはできません。そのようなバージョンは、計画中のバージョンの小節として追加されるべきです。ただし、そのバージョンに関する重要なソースが存在する場合は、記事を作成することができます。このソースには、開発版や次のアップデートでの要素に関する情報源が含まれます。
    2. Legacy Console Editionのバージョンに関する情報は、Legacy Console Edition/更新履歴に記載すべきです。ただし、PlayStation 4 Editionのバージョンに関する記事は、1.82(他のLegacy Console Editionの更新が終了したバージョン)以降は個別に記事を作成します。
    3. Minecraftのランチャーのバージョンに関する情報は、Minecraftのランチャー#歴史に記載すべきです。更新履歴が長くなる場合、または開発ビルドが多く存在する場合には、「Minecraft Launcher」をタイトルの冒頭に付けて、そのバージョンに関する記事を個別に作成することもできます。複数のバージョンが存在する場合は、番号が異なる部分を「x」に置き換えます。
コミュニティの注意事項
  1. ゲームの攻略情報やガイド、ハウツーなどは、チュートリアルの下位記事にしなければなりません。
    1. Pages containing a list of miscellaneous builds the user can make are not to be considered a tutorial. They are to be kept in the userspace. This includes user-created activities and challenges.
  2. Mojang ABがMinigames are only allowed to be added if Mojang AB claims to have played them.
  3. Modに関する記事は、Modの下位記事にしなければなりません。
    1. Articles about custom server modifications/topics should be sub-articles of their main article.
    2. Articles containing information about client mods are only allowed when the client mod cannot contribute to cheating or griefing in multiplayer.
  4. Articles regarding custom servers are only allowed when the server is released to the public.
Wikiの規則
 4.  パロディ、コメディ、ナンセンス、デマ、推測の記事、およびプレイヤーを誤解させるような記事は作成してはなりません。
 5.  特定のサーバーや他の製品を宣伝する目的の記事は作成してはなりません。
 6.  ファンコミュニティに関する記事は、広告上の問題があるため作成してはなりません。

ただし、「利用者」の名前空間内の記事は、これらの注意事項のガイドラインから免除されており、その他のWikiの規則に従う限り、どのように使用しても構いません。

リダイレクト[編集 | ソースを編集]

Redirects are exempt from the normal notability, but must redirect to an article that fits the notability guidelines. If a redirect leads to another wiki, it must use {{soft redirect}}. Redirects can be created if they fit one of the following:

  1. Alternate spelling of the title, such as "Armour" for "Armor".
    1. Incorrect spelling, typos, and irregular formatting are not allowed.
  2. Alternate or shortened name, provided the name is common usage, such as "Duck" for "Chicken". Previous in game names are also allowed, such as "Workbench" for "Crafting Table".
    1. This includes first names or handles for Mojang employees, such as "Nathan" or "Dinnerbone" to "Nathan Adams".
    2. This also includes names from alternate English language packs, with the exception of joke languages such as "Pirate Speak" and "Lolcat".
  3. Previous article title, including if the article was moved to another wiki.
    1. An exception is if the previous title was not commonly used.
  4. Alternate capitalization or form, including changing the title to plural case.
  5. A part of a merged or multi-topic article, such as a potion or a mentioned feature.

Redirects in the user namespace may lead anywhere, except to an article that does not exist or another redirect.

記事のタイトル[編集 | ソースを編集]

Article titles should be in the singular form to maintain consistency.

Articles should follow a general naming format based on the type.

  • Articles about blocks, items, and entities in game should use the in game name capitalized as it appears in game.
    • If the feature does not have an in game name, it should follow the same format as other articles of the same type. For example, the mob Spider Jockey.
    • If the article is about multiple things in the game, the title should equally represent all the titles. For example, an article about wooden and iron doors would be called Door.
  • Articles about people should contain the first and last names, rather than their Minecraft or Twitter handle.
  • Java Edition versions should be named using the version name, such as 1.8, 14w02a, or 1.8-pre1.
    • Redirects should be created from, e.g., Java Edition 1.8 to 1.8. Java Edition pages are currently in the process of being moved and details are still being worked out.
  • Pocket Edition versions should be prefixed with the words "Pocket Edition". For example, the update "Alpha 0.9.0" would be titled "Pocket Edition Alpha 0.9.0"
    • Pocket Edition Alpha development builds should first contain the parent version title, then the lowercase word "build" followed by the build number. For example, build 2 for "0.9.0" would be titled "Pocket Edition Alpha 0.9.0 build 2"
    • Pocket Edition development builds should first contain the lowercase word "alpha" followed by the version number. For example, "1.1.0.1" would be titled "Pocket Edition alpha 1.1.0.1"
  • Bedrock Edition versions should be prefixed with the words "Bedrock Edition". For example, the update "1.2.1" would be titled "Bedrock Edition 1.2.1"
    • Bedrock Edition development builds should first contain the lowercase word "beta" followed by the version number. For example, "1.2.0.9" would be titled "Bedrock Edition beta 1.2.0.9"
  • Other versions should be prefixed with the edition. For example, the update "1.0.27" for Education Edition would be titled "Education Edition 1.0.27"
  • Disambiguation articles should only contain "(disambiguation)" if the title without the word is used by an article.
  • If the article's type is unlisted, it should use the most relevant title in sentence case, not title case, unless it is a proper noun.

書き込み[編集 | ソースを編集]

As this wiki's purpose is to document facts, you should always avoid speculative and unsourced information. Generally speaking, information does not require sources if they can directly be seen in-game or are otherwise obvious. Other information however, such as quotes from Mojang employees and information that is not widely known, must be sourced with a proper reference. The {{citation needed}} template should be placed after any information that requires a source. Do not add content to an article if you cannot find a proper source.

Articles in the main namespace should always be written in the third-person perspective and without terms referential to the reader. Try not to use abbreviations of words either. For instance, sentences like "You shouldn't come close to creepers because they'll explode and kill you." should be written as "The player should not come close to creepers as they will explode, potentially killing the player.".

To emphasize points, italics should be used, not bold or ALL CAPS.

Tutorial information should only be within tutorial articles, which includes navigational features of blocks or textures. Tutorials may be linked from other articles if relevant though.

Mod information should not be contained on articles not about mods. Mods should also not be linked from articles not about mods.

記事を簡潔かつ最新の状態に維持する[編集 | ソースを編集]

ショートカット
MCW:UPTODATE

In short, articles should only contain information that is up to date, i.e., implemented in the latest full version of the game. Anything that is outdated should be moved to the History section of the article. When something changes, note the change in the History section and remove the outdated information from other sections of the article. It is unnecessary to mention when a particular feature was implemented; this is once again reserved for the History section of the article. Sentences such as "Trading, which was implemented in 1.3.1, is a feature that allows players to exchange emeralds (previously rubies) for other items." should be written as "Trading is a feature that allows players to exchange emeralds for other items."

Here's an example of how to not write a good article. It uses a previous version of the Log article, which at the time was called Wood. This is the full introduction. Highlighted in yellow is the redundant information, and in pink the history information.

Wood (previously known as log) is a type of block first seen in Minecraft Creative mode 0.0.14a They have a skin resembling bark on the four side faces, and a crosscut face on top and bottom. Only the normal oak logs are available in chunks generated before the Beta 1.2 update and all previous versions, whilst pine and birch will generate in newer chunks. Wood is greatly abundant in naturally-generated maps, as it is used as the foundation for trees. Wood can be chopped by hand, but using an axe is faster. Wood is also flammable.

Of the current wood types, birch is the rarest type. They are often used to make plants, trees and wooden cabins. In Survival Test, wood blocks drop 3-5 wooden planks when mined. In Indev, Infdev, Alpha, and Beta, mining a wood block will drop a wood block instead. This allows the use of wood as a building material and is craftable into planks.

Wood's only crafting use is to be made into four wooden planks. In addition, wood can be burnt in a furnace to make charcoal as a substitute for coal.

As of the Minecraft Beta 1.2 update on January 13, 2011, there are now four kinds of wood. One is the normal wood (oak), another resembles the wood of silver birch trees, yet another type resembles the normal wood, but it is darker and appears in pine/conifer trees that grow in colder biomes, the fourth type is similar to the oak wood, however there are some color differences and it is tilted to one side. These wood blocks still produce 4 wooden planks when crafted. Wood from different types of trees will not stack in the inventory, but their planks will. Planks made from different kinds of trees are completely identical. Birch trees have slightly duller colored leaves than regular trees, pine trees have pine needles, and jungle leaves are leafy with fruit looking shapes on them.

The fourth type of wood was introduced in Snapshot 12w03a, solely occurring in Jungle Biomes, and comprising trees exclusive to them. The tallest trees have this type of wood in 2x2 dimensions instead of the normal 1x1.

The issue with this is that old information is scattered with new information. The introduction should state the current description of the block with the current release. History information is good, but for clarity, it should be described in the chronological order in a single place: the History section of the article.

今後[編集 | ソースを編集]

ショートカット
MCW:FUTURE

Content added in future updates may be added to the article in the main content, provided the features are marked using {{upcoming}} and have appeared in development versions. If the update contains major changes to the article, then the content may be noted as a subsection of a main section, or as its own section called Upcoming. Upcoming features must be noted as well in the history section using the proper upcoming header.

Upon the release of the update, all content that is now outdated must either be moved to the history section or removed, and any usage of {{upcoming}} may be removed.

Spelling[編集 | ソースを編集]

Pages on the wiki should use American English unless the in-game name is British English. For instance, "colour" should be "color" and "centre" should be "center".

Capitalization[編集 | ソースを編集]

ショートカット
MCW:CAPS

In-game items should be treated as common nouns and as such should not be capitalized, unless they start a new sentence. This includes fictional items, such as prismarine. Proper nouns, however, such as the Nether or the Overworld should always be capitalized.

Structures and biomes

In-game structures and biome names should not be capitalized. Examples:

Underground, there are randomly generated mineshafts.
A desert pyramid contains precious loot.
Blazes spawn in fortresses.
In deep ocean biomes, monuments can generate.
A stronghold is home to an end portal.
Mobs

Any instance of a mob should be treated as a common noun, except where the mob is referred to using a proper noun. If the word "the" is used before the mob name, it should not be capitalized unless it is at the beginning of the sentence.

Examples:

One of the most feared mobs is the ghast.
A cave spider can poison its prey.
The player has been referred to as Steve.
Enchantments

Enchantment names should always be capitalized.

Example:

In order to have ice drop an item, you need a tool enchanted with Silk Touch.
Status effects

Status effect names should be capitalized, except where they are used as an adjective.

Examples:

Magma cream is required for a potion of Fire Resistance.
Wither skeletons may inflict Wither on the player.
An invisible spider may rarely spawn.
Editions

"Snapshot" and "pre-release" should not be capitalized. "Pre-release" should always be hyphenated. Development phases should be capitalized.

Editions should only be capitalized when used as nouns.

Examples:

Minecraft officially came out of Beta on November 18, 2011
The cyan flower was introduced in Pocket Edition Alpha 0.1.
Of all the editions of Minecraft only the Pocket and Pi Editions have cyan flowers.
Game modes

The name of game modes should be capitalized.

Examples:

In Hardcore mode the game acts similar to Survival mode except the difficulty is permanently set to Hard.

セクション(節)の見出し[編集 | ソースを編集]

ショートカット
MCW:HEADINGS

Article main sections should start with level 2 headers (two equal signs) and increase by one for subsections. Never use level 1 headers (one equal sign).

Follow sentence style capitalization, not title style, so only the first letter of the heading and proper nouns are capitalized.

There should be one space between sections as well as one space between the equal signs and the section name for ease of editing. If any "main article" links or thumb images are used, place them immediately under the section header, and then a space after those before the section content.

Do not add blank sections.

For information on which sections should be in which order, see the Article layout section of this style guide.

斜体[編集 | ソースを編集]

Any instance of "Minecraft " should be in italics. Any instance of the name of a videogame should also be in italics. For instance: Team Fortress 2. Official Minecraft edition names, such as Java Edition and Bedrock Edition should be in italics; unofficial edition names, such as "Legacy Console Edition", should not.

画像[編集 | ソースを編集]

ショートカット
MCW:IMAGES

When adding screenshots to an article, make sure the screenshots use vanilla textures and UI. Screenshots that use custom texturepacks, UI mods and other custom content are not allowed. This does not apply to articles covering mods.

Image captions should not have periods at the end, unless the phrase is a full sentence.

Images added to articles should fit the following guidelines:

  • Images should showcase an attribute of the article's topic.
    • Images should not show unintended strange or humorous behavior, such as mobs "sitting" on stairs.
    • Images should not have the sole purpose of showcasing a bug, instead report the bug on the official tracker.
    • Images showcasing usage of specific features for decoration should be avoided.
  • Articles should only have one image showcasing an individual attribute of the articles content. For example, a zombie wearing armor.
  • Images should showcase the most up to date version of Minecraft available for the content.
    • Images that are outdated are subject to be removed.

リンク[編集 | ソースを編集]

For a complete guide to linking, please refer to Wikipedia's Manual of Style for links, although do note that some of the policies about linking listed there are different than many here.

The use of links is a difficult balance between providing the reader enough useful links to allow them to "wander through" articles and excessive linking which can distract them from their reading flow.

Underlinking can cause the reader to become frustrated because questions may arise about the article's contents which can only be resolved by using the search option or other sources for clarification, interrupting and distracting the reader.

Overlinking may distract the reader because links are usually colored differently causing the eye to shift focus constantly. Additionally, if the same word is linked multiple times in the same paragraph it can cause the reader to question if the links are directing them to different articles or not.

The guidelines for linking are:

  • No more than 10 percent of the words in an article are contained in links.
  • Unless it affects the sentence's wording and readability in a negative way, two links should not be next to each other in the text so that it looks like one link.
  • Links for any single term should not be excessively repeated in the same article. Excessive linking is defined as multiple use of the same term, in a line or a paragraph, which will almost certainly appear needlessly on the viewer's screen. Remember, the purpose of links is to direct the reader to a new spot at the point(s) where the reader is most likely to take a temporary detour due to needing more information.
  • Duplicating an important link distant from a previous occurrence in an article may well be appropriate. If an important term appears many times in a long article, but is only linked once at the very beginning of the article, it may actually be underlinked. Indeed, readers who jump directly to a subsection of interest must still be able to find a link. But take care in fixing such problems, the distance between duplicate links is an editor's preference, however if in doubt duplicate the term further down the article.

Linking to a redirect is preferred over using a piped link except in templates and other pages that will be transcluded. When a piped link is unavoidable, it should not point to a redirect. If a redirect can be avoided using a suffix on the link, that is preferred. E.g. Using [[Creeper]]s instead of [[Creepers]] is desired.

日付の書式[編集 | ソースを編集]

The Minecraft Wiki is an international community. That is a good thing in general, but it makes a problem for numeric abbreviations of dates, such as "12/10/11": while most countries abbreviate dates as day/month/year, some Asian countries use year/month/day, and the US uses month/day/year. So the above date could represent any of three different dates. To avoid this problem, most dates should be written in "Month DD, YYYY" format, e.g. "December 10, 2011". Do not use superscripts or suffixes such as "April 23rd" or "4th of May". If a numeric or terse date is needed (such as in a table), then use YYYY-MM-DD, always with 2 digits for month and day (e.g., 2011-12-10 or 2012-05-04). Besides being the ISO standard, dates in this format will naturally sort properly, say if the table column is later made sortable.

レッドストーン構造物[編集 | ソースを編集]

Write-ups for redstone circuits and mechanisms should follow a single convention on the wiki.

記事のレイアウト[編集 | ソースを編集]

ショートカット
MCW:LAYOUT

For the sake of consistency, all articles of a specific type should follow a general layout.

  • At the very top, applicable flags and templates, such as {{snapshot}} for anything not yet in the full release, {{Block}} for blocks, and so on.
  • Introduction with a general description.
  • Article body, starting with first header.

Be smart when adding a message box: too many boxes at the top of a page or a section is not useful. If there is already one, move the ones that are not necessary for the reader lower on the page, for example in a relevant section or at the very end.

If an article does not contain a layout currently, one can be proposed on the talk page; otherwise, attempt to use a layout that follows a similar style to an existing layout. Current article layouts include: