Pengguna:Dedhert.Jr/Uji halaman 06/3

Halaman ini adalah bagian dari pedoman gaya di Wikipedia bahasa Indonesia.
Isinya telah diterima luas oleh para pengguna dan dianggap sebagai standar yang harus diikuti oleh semua pengguna, meskipun sebaiknya dipahami dengan akal sehat, dan pengecualian dapat berlaku sewaktu-waktu. Segala penyuntingan substansial yang dilakukan di halaman ini harus menggambarkan konsensus. Jika Anda ragu, diskusikan terlebih dahulu di halaman pembicaraan.

Pedoman gaya permainan video merupakan sebuah Pedoman gaya yang dimaksudkan untuk memberikan petunjuk terkait penulisan ataupun penyunting artikel bertopik permainan video di Wikipedia. Untuk memulainya, ada hal-hal berikut yang harus diperhatikan:

Tata ruang

Pada bagian pedoman gaya ini, menjelaskan berbagai bagian-bagian tubuh pada artikel bertopik permainan video.

Tata ruang untuk permainan video

  • Bagian pembuka: Yang harus dilakukan pertama adalah menulis nama permainan yang dimiringkan, genre permainannya, tanggal rilis, platform, dan informasi yang teridentifikasi lainnya. Kemudian, tulis ringkasan pada seluruh tubuh artikel agar menjelaskan mengapa permainan video ini penting. Hal ini merupakan bagian terpenting dalam bagian pembuka, karena dapat menjelaskan gagasan utama yang akan dipakai melalui artikel.
  • Kotak info: Isi artikel harus melekat dengan dokumentasi templat.
  • Alur permainan: Suatu artikel bertopik permainan video harus menjelaskan bagian penting tentang bagaimana cara kerja permainan video tersebut. Hal yang harus diperhatikan saat menulis alur permainan adalah jangan menulis terkait panduan-panduannya.
  • Plot: Suatu plot pada permainan video dapat disatukan ke dalam alur permainan jika isinya tidak terlalu kompleks. Jika plotnya terlalu kompleks, tulislah atau buatlah bagian baru. Jika sangat diperlukan, bagian halaman dapat membuat subbagian baru mengenai kisah cerita, latar, dan karakternya.
  • Tanggapan: Suatu artikel harus menjelaskan bagaimana permainan video diberi sambutan atau tanggapan melalui kritikan.
  • Peninggalan: Jika permainan mempunyai dampak substansial tentang permainan, genre, datau industri permainannya, cobalah untuk membuat bagian yang menjelaskan tentang peninggalannya. Bagian ini dapat ditulis di bawah bagian sambutan, atau jika masih ada informasi yang cukup, cobalah untuk memisahkan bagian tersebut. Jika dampak utamanya hanyalah sekel atau adaptasi media, maka sangat dianjurkan untuk menulis bagiannya seperti "Media yang berkaitan", "Sekuel", dsb.
  • Referensi: Suatu artikel membutuhkan kutipan sumber. Jika Anda belum memastikan manakah yang perlu dimasukkan sebagai referensi, maka peninjauan, artikel berita, buku tentang instruksi permainan, dan panduan dapat dipakai sebagai kandidat referensi yang terbaik, silahkan lihat di Wikipedia:WikiProyek Permainan Video/Sumber.
  • Pranala luar: Ketika tersedia pranala-pranala luar, tulislah perusahaan dan situs permainnya jika situs perusahaan terpisah dari situs permainan. Selain itu, tulis semua situs terbitan yang relevan. Sumber-sumber yang tidak memenuhi syarat sebagai sumber tepercaya dapat dipakai jika tidak ada daftar-daftar situs yang perlu dihindari.

Tata ruang untuk karakter dalam permainan video

  • Bagian pembuka: Yang harus dilakukan pertama adalah tulislah nama karakter atau seri (jika merupakan kumpulan karakter) dalam permainan video yang dimiringkan dan ditebalkan, nama perusahaan datau perancang yang mengembangkannya, dan informasi yang teridentifikasi lainnya. Kemudian, jelaskan mengapa karakter ini sangat penting. Hal ini merupakan bagian terpenting dalam bagian pembuka, karena dapat menjelaskan gagasan utama yang akan dipakai melalui artikel.
  • Kotak info: Artikel yang menjelaskan satu karakter harus mempunyai infobox karakter, namun artikel yang menjelaskan kumpulan karakter tidak perlu menggunakan infobox.
  • Konsep dan rancangan: Pada bagian ini, jelaskan isinya tentang proses pada saat karakter sedang diciptakan dan dirancang.
  • Kehadiran: Pada bagian ini, kehadiran suatu karakter harus ditulis untuk setiap permainan dan bahas dengan singkat tentang perannya dalam permainan video. Biasanya, pada daftar atau artikel tentang kumpulan karakter, bagian ini digabungkan dengan sisa bagian karakter.
  • Dagangan: Bagian ini harus memuat isi tentang ketika karakter yang disukai penggemar tersebar luas dipakai sebagai barang-barang perdagangan. Jenis-jenis perdagangan harus ada di bagian ini, dan tulis tanggal beserta daerah barang dagangannya, jika memungkinkan.
  • Tanggapan: Bagian ini harus menjelaskan secara detail tentang bagaiman karakter menerima oleh kritkan. Biasanya, kritikan tentang permainan tersendiri dihilangkan karena artikel tersebut menjelaskan tentang karakter.
  • Sumber: Suatu artikel membutuhkan kutipan sumber. Jika Anda belum memastikan manakah yang perlu dimasukkan sebagai referensi, maka buku tentang instruksi permainan, panduan, peninjauan, dan wawancara dapat dipakai sebagai kandidat referensi yang terbaik.
  • Pranala luar: Ketika pranala-pranala luar tersedia, tulislah situs permainannya. Namun, jika yang diterbitkan dahulu merupakan selain negara yang menggunakan bahasa Inggris, tulis pula situs negara aslinya. Sumber-sumber yang tidak memenuhi syarat sebagai sumber tepercaya dapat dipakai jika tidak ada daftar-daftar situs yang perlu dihindari.

Tata ruang untuk latar permainan video

  • Bagian pembuka: Yang harus dilakukan pertama adalah menulis nama latar atau dunia fiksi dalam bentuk huruf miring dan tebal, nama perusahaan datau perancang yang dikembangkannya, dan informasi yang teridentifikasi lainnya. Kemudian, tulislah sebuah rangkuman artikel dengan singkat. Terakhir, jelaskan mengapa latar permainannya penting. Hal ini merupakan bagian terpenting dalam bagian pembuka, karena dapat menjelaskan gagasan utama yang akan dipakai melalui artikel.
  • Kontak info: Hampir semua artikel tidak memerlukan kontak info.
  • Konsep dan rancangan: Pada bagian ini, jelaskan isinya tentang proses pada saat karakter sedang diciptakan dan dirancang.
  • Isi dalam permainan: Bagian ini harus menjelaskan informasi terkait latar permainan ketika diterapkan dalam permainan. Kemudian, bahas dengan singkat tentang perannya dalam permainan dan setiap aspek dari dunia permainan yang dianggap memiliki fakta penting. Namun, bagian ini tidak harus menjelaskan detail secara berlebihan tentang plot permainan, deskrpisi tentang latarnya, ataupun informasi mengenai panduan permainan.
  • Tanggapan: Bagian ini harus menjelaskan dengan detail mengenai bagaimana latar atau aspeknya diterima melalui kritikan. Biasanya, kritikan terkait permainan tersendiri tidak diperlukan karena artikel tersebut hanya menjelaskan latar permainan.
  • Sumber: Suatu artikel membutuhkan kutipan sumber. Jika Anda belum memastikan manakah yang perlu dimasukkan sebagai referensi, maka buku tentang instruksi permainan, panduan, peninjauan, dan wawancara dapat dipakai sebagai kandidat referensi yang terbaik.
  • Pranala luar: Ketika pranala-pranala luar tersedia, tulislah situs permainannya. Namun, jika yang diterbitkan dahulu merupakan selain negara yang menggunakan bahasa Inggris, tulis pula situs negara aslinya. Sumber-sumber yang tidak memenuhi syarat sebagai sumber tepercaya dapat dipakai jika tidak ada daftar-daftar situs yang perlu dihindari.

Isi artikel

Gaya penulisan

Wikipedia adalah ensiklopedia, maka dari itu artikel harus ditulis secara formal, tidak seperti situs tanya jawab, situs penggemar, atau situs panduan bermain. Selain pedoman gaya yang umum, ingatlah pedoman gaya berikut.

Format penulisan pada nama permainan video

Sudut pandang netral

Penamaan dalam artikel

Penulisan judul dalam bahasa Jepang

Jargon dalam permainan video

Metadata

Article title

Title Wikipedia articles by the subject's common name: The name most commonly used in English-language reliable, secondary sources and best balance of the five naming criteria: recognizability, naturalness, precision, conciseness, and consistency. Secondarily, use Wikipedia:Naming conventions (video games) to reference common formatting and disambiguation terms for video game topics.

Short description

 
How short descriptions appear in the Wikipedia App

Mainspace pages should be tagged, if possible, with a short description, a brief summary of the topic of the page, which is used as part of the Wikipedia App and aids in how Wikipedia is seen on the semantic web. This is done by using the template {{short description}} near the top of the page, prior to the lead prose, hatnotes, and infobox templates. The short description should be, as self-evident, short, just enough to help to distinguish the topic from any possible close matches.

  • For video games, a typical format would be "<year of release> video game". For example, for Resident Evil 4, 2005 video game; for God of War, 2018 video game.
    • If further disambiguation is needed, add the game's primary genre: "<year of release> <genre> video game".
    • If an article covers multiple video games and is not a video game series, such as the case with the article Pokémon FireRed and LeafGreen or Super Smash Bros. for Nintendo 3DS and Wii U, the year of the earliest release should be added. The general format should be "<year of release> video games". For those two examples, 2004 video games and 2014 video games should suffice.
  • For video game series or franchises, "Video game series" is sufficient.
  • For video game hardware, a short description of the type of hardware. For example, for PlayStation 2, home video game console; for Nintendo DS, handheld video game console; and for DualShock, video game controller.
  • For people in video games, use "<nationality> <primary job function(s)>". For example, for Gabe Newell, American businessman, and for Shigeru Miyamoto, Japanese video game designer.
  • For video game companies, similarly use "<nationality> <primary business type(s)>". For example, Nintendo, Japanese video game company; for Electronic Arts, American video game company, and for Remedy Entertainment, Finnish video game developer.

For any other case, use similar short terminology. The goal is a phrase shorter than 40 characters, specific enough to be clear to identify the topic if searching through a list of closely matched similar terms with these descriptions.

Infobox

Section-specific advice

First sentence

Avoid bloat in the first sentence. Restrict it to the most important aspects of the topic.

The first sentence should:

  • Include only the primary genre. Exclude themes and concepts. E.g., The Legend of Zelda: Breath of the Wild is a 2017 action-adventure game, not The Legend of Zelda: Breath of the Wild is a 2017 third-person open-world action-adventure game.
  • Include the original release year as part of the introduction to the topic. Other dates, or more specific dates, may appear elsewhere in the lead but should do so only as part of summarizing the topic.
    • Label unreleased, pre-release, and early access games as "upcoming".
  • Only use a parenthetical foreign language equivalent when the game/topic is not primarily known by a Latin alphabet title. Move the parenthetical to a footnote if the non-English name is not critical to understanding the topic.
  • Avoid "commonly known as" and "stylized as", unless the point of abbreviation or stylization has been made by a preponderance of reliable, independent, secondary sources. Wikipedia maintains a formal tone and, like newspapers and magazines outside the gamer niche, uses brief phrases instead of abbreviations. For example, the name Ocarina of Time would be an acceptable shorthand for The Legend of Zelda: Ocarina of Time, but OoT would not, and likewise applies with Global Offensive for Counter-Strike: Global Offensive, but not CS:GO. There are some occasions where using the full name of the game is the only appropriate option, such as Team Fortress 2 instead of TF2.

Gameplay

Genre

  • For both the lead, infobox, and "gameplay" sections of an article about a video game, make sure to indicate the game's genre or genres.
  • Avoid using more than two genres, or more than one hybrid genre (like "action-adventure") in listing the genres. Simply borrowing parts of a genre does not necessarily make the game of that genre, and instead can be said to be using elements of that genre in the lead and gameplay prose. For example, BioShock is a first-person shooter with role-playing game customization and stealth elements... rather than BioShock is a role-playing, stealth first-person shooter...
  • Use standard genres (those defined in {{Video game genre}}), and avoid developer/publisher-created ones in these sections, though one can subsequently describe how the developer or publisher describes the game. For example, Dead Cells is properly classified as a roguelike-Metroidvania by most sources, but mention is made of the developer's "roguevania" self-description as a mashup of these genres.
  • Do not include narrative genres and gameplay mechanics, such as "science fiction" and "open world", alongside a game's genre. These can instead be used later in the lead or in the gameplay/plot section.
  • Similarly, unless a game is strictly a first-person shooter (like Doom) or a third-person shooter (like Gears of War), these perspectives are not defining genres that should be included, though can be used to describe the gameplay aspects. For example Portal is a puzzle-platform video game... and not Portal is a first-person puzzle-platform video game....

Plot

  • The article's plot coverage should be proportional to the plot's importance in the game, as determined by its weight in the article's source material. For example, plot is a major aspect of Final Fantasy game reviews but a minor aspect of 2D platformer reviews.
  • Include the plot within the gameplay section unless there is cause to distinguish it.
  • Straightforward plot summary is assumed to be sourced to the game itself and thus does not require sources. Any conclusions inferred by interpretation, however, do require reliable, secondary sources. Add secondary sources whenever reasonable to (1) reliably verify the cited fact, and (2) prove that the plot detail was sufficiently non-trivial to pass the source's editorial discretion. Primary sources, such as the instruction manual, are of limited use, as a self-published source about itself.
    • The plot should summarise content that every player would be expected to see on a playthrough of a game. Avoid including elements that require the player to follow side quests or visit secret areas, unless that information is deemed critical to understanding the plot. If such information is included, it should be referenced in a way to explain how the player would discover it for verifiability requirements. For example, BioShock Infinite references specific messages from optional collectibles to support plot elements outside the player's frame of observation.
    • For games with divergent narrative paths, including multiple endings, consider how to summarize these to the simplest level of detail. The summary should explain that the narrative branches, but it is not necessary to enumerate exactly how to obtain each branch or events along each. Focus on divergent narratives that have the greatest impact on the story. For example, the plot summary of The Walking Dead (video game) omits many of the possible story choices, but retains the final decision and its consequences the player makes due to its impact on the narrative.
  • Write about story elements from a "real-world perspective". Do not use a perspective from within the game world ("in-universe") or describe fiction as fact. E.g., not "It is the end of the Zelda timeline and thousands of years after Link defeated Ganondorf", but "Breath of the Wild is set at the end of the Zelda timeline, thousands of years after the events of previous games".
  • To retain focus, generally limit plot summaries to 700 words or fewer.
    • For episodic video games, plot summaries of no more than 300 words per episode should be presented either in the plot section as prose or in a table using {{Episode table}} and {{Episode list}}. If appropriate, these articles could instead include a prose plot summary of no more than 700 words per season instead of an episode table, but an article should not have full plot summaries in both an episode table and a plot section. A brief one sentence plot synopsis is permitted in the table for articles with both, such as Tales of Monkey Island.
    • For narrative downloadable content (DLC), plot summaries of no more than 300 words per content should be presented in the main plot section or as an additional sub-section (such as Final Fantasy XV). If appropriate, larger narrative DLC may be split into its own article if it receives significant independent development and reception coverage, such as The Last of Us: Left Behind. Split articles should follow the main plot guideline of 700 words.

Development

  • In describing development elements related to the release of a game, it is often easy to fall into the use of proseline on trivial details, repetitive sentences or list items in a form like "On such-and-such date, the company teased the release of their game via a Twitter message." Both proseline and this type of detail are generally inappropriate. Consider what secondary sources state about the game's pre-release information to determine what is appropriate to include. The use of release teasers, trailers, and social media is common throughout the industry, so specific details on these elements are generally unnecessary unless the nature of their presentation is something noted by sources. Exact dates for announcements are rarely necessary and only a rough time estimate is needed: a month/year for most games, or for those unveiled at conferences like E3 or GDC, referring to those conferences.

Reception

  • Organize sections thematically to juxtapose similar comments from reviewers into a coherent narrative. For example, group reviewer comments on gameplay, technical audiovisuals, narrative, and other common themes of the reviews.
  • Signpost each paragraph with a topic sentence. A good opening sentence summarizes the paragraph, helps the reader anticipate what to expect from the paragraph, and has references to directly support the summary. Be careful to not make generalizations not substantiated by the sources. If Reviewers praised the game's art direction, say so, and add the references that support the statement, but avoid Most reviewers praised... and other phrases that make the subject ambiguous unless you have a source that makes a claim about "most".
  • Stack similar claims. When five reviewers write that the controls were clunky, write the claim as a single sentence with multiple refs. If the number of footnote refs following the sentence becomes unwieldy, mention all sources in a single summative footnote. Example: Templat:Oldid2
  • Vary sentence rhythm and avoid "A said B". Successive sentences in this pattern quickly become dull:
    • John Smith opined, "it's the best game of the year". Juana Pérez of Reliable Blog claimed it was "dry and boring" and lacked focus. (Variants include "A of B said C" and "A said that B".) Rephrase and recast sentences whenever possible to keep the content interesting. Try varying sentence length, direct and indirect claims, and types of summary. For more, see Wikipedia:Copyediting reception sections.
  • Minimize direct quotations. Prefer paraphrase whenever possible, both for Wikipedia's emphasis on minimizing use of copyrighted content and to massage the essence of the source into what best suits the section. Almost all reviewer sentiments can be rephrased without using the source's exact words/phrases. Use quotations only to illustrate that which cannot be said better than the source. Reception sections that consist purely of quotations are treated as copyright violations.
  • Reduce minutiae inappropriate for a general audience. For example, avoid scores and statistics in prose, which are hard for the reader to parse and often impart little qualitative information. A dedicated template exists for such a purpose.
    • Review aggregator Metacritic gave the PC version a score of 76 out of 100 based on 45 reviews from critics, while the Xbox 360 and PlayStation 3 versions received scores of 77 and 79, respectively. ... The first review was published by Official Xbox Magazine, which gave the game a 9.5 out of 10. IGN gave it 8.5.
  • Although not required, it is helpful to include the number of reviews GameRankings or Metacritic uses to calculate their scores, since it gives context and can help the reader understand how the score is averaged. The number can either be listed after Metacritic's qualitative summary in prose or footnoted in {{Video game reviews}}. Examples: Team Sonic Racing's reception section
  • Similarly, reduce clutter by removing reviewer names, publications, and dates when unnecessary to the point at hand.
    • Multiple reader polls ranked the game among the best of all time.[1][2][3], instead of The game was included in multiple top 50 games of all time lists, including that of Famitsu readers in 2006[1] and IGN readers in 2005[2] and 2006.[3]
  • Metacritic's qualitative summary often provides a satisfactory summary of a game's overall reception. As in the image to the right, The game received "mixed or average reviews", according to review aggregator [[Metacritic]]. Avoid summative claims that cannot be explicitly verified in reliable, secondary sources.
     
    Metacritic gives quotable language to summarize a game's reception.
  • "Mixed-to-positive" and "mixed-to-negative" imprecisely describe reception that skews slightly more positive or negative. "Mixed" means "scattered across the board", not "medium", so reviews cannot be both "mixed" and "positive". For precision, "mixed" alone is sufficient. Supplement with specific reviews to describe various positive and negative aspects.
  • Only consider including GameRankings in {{Video game reviews}} when a Metacritic score is unavailable (e.g., older games). But do not include aggregate scores when there are fewer than four reliable outlets used in the aggregate, which undermines the statistic. Round aggregator scores to the nearest whole number (e.g., 83.46%83%)(for more, see Template:Video game reviews/doc#Guidelines).
  • User reviews and other self-published sources are unreliable unless these are called to attention in secondary sources, such as if a game was review bombed. In such cases, cite the secondary source(s) describing the event, not the user review itself.

Awards

  • Noteworthy awards and nominations that contribute to the overall reception should be documented in prose in this section. Individual publications often use awards to distinguish a game's lasting impact. If a game has received more nominations than can comfortably be discussed without proseline (typically four or more), these should be placed in a table. For the table, only include awards where either the awards individually are notable (e.g. Seumas McNally Grand Prize) or the awards body as a whole is notable (e.g. The Game Awards); omit individual publication awards and ranked lists from the table.
  • Awards included in lists should have a Wikipedia article or be vetted by the community to allow for its inclusion to demonstrate notability. Examples of formatting such tables, typically consistent with accolades from film and television, can be found at God of War and Undertale. Tables with a large number of awards or nominations should be moved to a separate article only if the game article is approaching page size concerns. Examples can be seen with The Last of Us and Red Dead Redemption 2.