Difference between revisions of "Editor's information"

From Valve Cut Content
Jump to: navigation, search
oldwiki>Livelong2
(inc implementation)
oldwiki>Livelong2
(please stop being shit Editor's inforfuck)
Line 1: Line 1:
This page is intended to serve as a reference for VCC Wiki editors, and provide information useful for both newbies and veterans alike.
+
<!-- Old EI is a dumpster fire, going for a more wikipedia-inspired approach -->
 +
==What is the VCC Wiki?==
 +
VCC Wiki is a wiki dedicated to the documentation of Valve's Cut Content. It was created in response to a perceived absence of this documentation in the more "generalist" Valve wikis.
  
==Getting Started==
+
As a result of this, our primary focus is on Valve's cut content, and the community surrounding it.
Welcome to the VCC Wiki! Before you begin, there's a few different things we need to go through.
+
===Why Not Edit?===
===Subject of the Wiki===
+
Notice a factual error somewhere? See a formatting issue that nobody seems to have noticed? Try your hand at editing it!
{{SITENAME}} focuses on primarily what its name is. Cut content of valve games, such as Half-Life, Portal, Left 4 Dead. It also focuses on the more documentable aspects of the Cut Content community, such as mods and patches.
 
  
What sets it apart from the Combine Overwiki is that it specializes in leaks, and doumenting the advanced details of cut content.
+
Even if you don't do the job correctly, all that will happen is that someone will come over and fix it, perhaps telling you how to do it correctly the next time.
Where the Overwiki focuses on the various aspects of the final version of the [http://combineoverwiki.net/wiki/Overwatch_Soldier Combine Soldier], leave a brief section about how it changed "Behind the Scenes", VCC Wiki exclusively focuses on how it evolved with "[[Combine Soldier (Evolution)]].
 
  
===Neutral Point of View===
+
Don't be afraid to edit. Nobody blames an editor with good intentions.
Neutral point of view is essential for a writer of Wiki articles to understand.
+
===Page Philosophy===
 +
Let's face it - we're not going to have a universal set of standards for everything, considering our weird and varied subject matter.
  
On the {{SITENAME}}, one of the main goals is to provide useful, complete, and accurate information. To provide the highest quality of information, one must be neutral and without any bias or opinion. This is what is called '''Neutral Point of View''', or '''NPOV'''.
+
When doing something new, don't approach it with a bunch of pre-thought-out header structures in mind. Think to yourself, what would work best? Often, that's the way that gets the best results.
 
+
==Subpages==
====What is it?====
+
It's helpful to look over these pages before editing:
NPOV is when an editor writes or edits articles with a completely neutral point of view. This means that there is no bias or opinion from one author. This also includes to not use the word "I", or other [[wikipedia:Wikipedia:WEASEL|weasel words]].
+
*[[Editor%27s_information/Neutral_Point_of_View|Neutral Point of View]]
 
+
**A quick overview of Neutral Point of View, and how to use it.
====How do I do it?====
+
*[[Editor%27s_information/Formatting_Conventions|Formatting Conventions]]
To follow NPOV, simply write or edit articles without the use of opinionated words such as ''I, think, like, believe, hate," etc. Using weasel words, such as ''some argue'', ''many people thought'', and ''experts say'' are also against the NPOV.''
+
**A list of standardized formatting conventions.
 
+
*[[Editor%27s_information/Categorization_Guide|Categorization Guide]]
Advertising is also strictly against the NPOV. Advertising is defined as the promoting (or slander) of specific mods or users. Advertising is strongly advised against, as it severely degrades the quality of the article and makes the author seem biased.
+
**A list of actively-used tags, and when they should be used.
<!--
+
*[[Editor%27s_information/Useful_Stuff|Useful Stuff]]
====What if I don't do it?====
+
**An index of files and programs that are extremely useful to have when editing on this wiki.
NPOV is not required on some pages. Obviously, users should not follow NPOV on any user or user talk page. NPOV is also not required on article talk pages or in "tactics" sections.
+
*[[Editor%27s_information/Template_Guide|Template Guide]]
 
+
**A guide on how to use templates, and a list of the templates VCC Wiki makes usage of.
Following these rules greatly helps to improve the quality of information on the {{SITENAME}}, but if you really, truly ''cannot'' follow the NPOV guidelines, this is not a major issue. Edits can be modified or reverted in a short time; nothing is permanent.
+
==Page Structures==
 
+
A list of semi-standardized page structures. They might fit with what you are trying to write.
However, blatantly disregarding NPOV will force better-qualified users to "pick up the pieces", instead of using their time to create or better other articles. If it continues long enough, it can even be considered as vandalism, with the associated penalties resulting.
+
The bullet point levels are representative of the header levels.
I get the idea threatening people about this isn't a very good one
+
===<b>"Evolution" Structure</b>===
-->
 
<i>[http://danball.wikia.com/wiki/Dan-Ball_Wiki:Neutral_Point_of_View Source]</i>
 
 
 
===Formatting Conventions===
 
*When referring to a specific directory, put it within <nowiki><code></code</nowiki> tags. Example: <code>/materials/brick/</code>
 
*When creating a texture gallery, have the caption of each refer to the original VTF's, TGA's, etc.'s name in quotations. For example:
 
<!-- Shamelessly plagiarized from the OICW article-->
 
<gallery widths="300" orientation="none" spacing="small" bordersize="none" captionposition="below" hideaddbutton="true">
 
reciever.png|"reciever.vtf"
 
scope.png|"scope.vtf"
 
</gallery>
 
*The Leak is in reference to the [[The 2003 Leak]], and should be capitalized.
 
*When referring to Half-Life, make sure to specify <i>which</i> to help avoid confusion.
 
**Also: It is Half-Life, not "Half Life".
 
*When using level 4 headers (====Header====), either italicize or bold them to make sure that they are not overlooked as regular text.
 
 
 
===Editing Philosophy===
 
VCC Wiki is a wiki that values innovative approaches to page structure above most (if not all) else. We're not going to comply with a set of one-fits-all standards for articles, since there aren't any for the diverse and difficult array of topics that are documented. Try out what you think would work best for your article.
 
 
 
===Header Structures===
 
This is a quick outline of various pre-existing header structures. You might find one of them useful for you.
 
<!--
 
Template for these:
 
====<b>Title of structure</b>====
 
 
 
<b>Overview:</b>
 
 
 
<b>Works best with:</b>
 
 
 
<b>Examples:</b>
 
 
 
-->
 
====<b>"Evolution" Structure</b>====
 
  
 
<b>Overview:</b>
 
<b>Overview:</b>
Line 78: Line 46:
 
*[[Metropolice (Evolution)]]
 
*[[Metropolice (Evolution)]]
  
====<b>"Timeline" Structure</b>====
+
===<b>"Timeline" Structure</b>===
 
<b>Headers:</b>
 
<b>Headers:</b>
  
Line 94: Line 62:
 
*[[Timeline_of_Leaks_(Facepunch-Era)]]
 
*[[Timeline_of_Leaks_(Facepunch-Era)]]
  
====<b>"Weapon" Structure</b>====
+
===<b>"Weapon" Structure</b>===
 
<b>Headers:</b>
 
<b>Headers:</b>
  
Line 124: Line 92:
 
*[[MP5K (SMG1)]]
 
*[[MP5K (SMG1)]]
 
*[[XM29 OICW]]
 
*[[XM29 OICW]]
 
===Image Standards===
 
*Don't reuse images from other wikis. Grab your own renders and/or pictures, where possible.
 
*When capturing images, try to maximise the resolution possible.
 
*When capturing renders using hlmv, take the time to remove the background.
 
**Also, setting the background to an obnoxious, clearly distinct color, like hot pink or lime, can make removing said background much easier, and prone to less accidents.
 
==References==
 
These are intended to be used by veteran editors as a reference.
 
===Infoboxes===
 
* The current custom "Infobox" panels are:
 
{| class="article-table"
 
!Purpose (For documenting)
 
!Template name
 
|-
 
|Cut enemies
 
|[[Template:Cut Enemies]]
 
|-
 
|Cut Maps
 
|[[Template:MapInfoBox]]
 
|-
 
|Cut weapons
 
|[[Template:Weapon_infobox]]
 
|-
 
|Mods
 
|[[Template:Mod_InfoBox]]
 
|-
 
|Shitposts/memes
 
|[[Template:Game_Infobox]]
 
|-
 
|Vehicles
 
|[[Template:Vehicle_Template]]
 
|}
 
 
<span style="font-weight:normal;">Please consider if the current ones are a good fit for your article before creating another.</span>
 
===Linking===
 
There are several different sorts of linking that may be needed in certain situations.
 
*If the text you are linking is the same as the page title, use two sets of brackets.
 
**Example:<nowiki>[[Metropolice (Evolution)]]</nowiki>
 
*If the text you are linking to is different from the page title, use two sets of brackets, and put down the exact page title, with "|" at the end. Then, put down the text from which the link will be displayed.
 
**Example:<nowiki>[[Metropolice (Evolution)|Police]]</nowiki>
 
*If the text you are linking is outside the wiki, first put down the link of it. Then, put down (with no separating characters) the text you wish to display.
 
===Tagging===
 
This is a list of the currently-used tags. If you feel another should be added, feel free to - this system isn't perfect by a long shot.
 
 
<b>Games</b>
 
 
*[[:Category:Half-Life|Half-Life]] (General series tag)
 
**[[:Catecory:Half-Life 1|Half-Life 1]]<br />
 
**[[:Category:Half-Life 2|Half-Life 2]]<br />
 
 
*[[:Category:Portal|Portal]] (General series tag)
 
**[[:Category:Portal 1|Portal 1]]<br />
 
**[[:Category:Portal 2|Portal 2]]<br />
 
 
 
*[[:Category:Team Fortress Classic|Team Fortress Classic]]<br />
 
*[[:Category:Team Fortress 2]]
 
**[[:Category:Team Fortress 2 (BoA)|Team Fortress 2 (Brotherhood of Arms)]]<br />
 
**[[:Category:Team Fortress 2 (Invasion)|Team Fortress 2 (Invasion)]]<br />
 
**[[:Category:Team Fortress 2 (Final)|Team Fortress 2]]<br />
 
 
*[[:Category:Left 4 Dead|Left 4 Dead]](General series tag)<br />
 
 
*[[:Category:Conuter Strike|Counter Strike]](General series tag)
 
**[[:Category:Counter Strike 1.6|Counter Strike 1.6]]<br />
 
**[[:Category:Counter Strike Source|Counter Strike Source]]<br />
 
**[[:Category:Counter Strike GO|Counter Strike GO]]
 
 
<b>Leaks</b>
 
 
*[[:Category:Portfolio Releases]]<br />
 
*[[:Category:Leaks]]<br />
 
General tag, used for leak documentation articles, does not involve articles relating to specific parts of leaks.
 
 
Use tags below when tagging articles about a specific part of them.<br />
 
*[[:Category:1997 Press Disc]]
 
 
*[[:Category:2003 Leaks]]<br />
 
*[[:Category:WC Mappack]]
 
 
*[[:Category:2007 Particle Benchmark]]
 
 
*[[:Category:2016 Leaks]] (Depending on the date of the leak)<br />
 
*[[:Category:2017 Leaks]]
 
 
<b>Type specifiers</b>
 
 
*[[:Category:Items]] (Including weapons)
 
**[[:Category:Weapons]]
 
 
*[[:Category:Vehicles]]
 
 
*[[:Category:Non-Player Characters]]
 
 
*[[:Category:Allies]]
 
**[[:Category:Humans]]
 
 
*[[:Category:Enemies]]
 
**[[:Category:Combine]]
 
 
*[[:Category:Maps]] (Used for maps.)<br />
 
*[[:Category:Locations]] (Used for locations. Should not overlap with maps.)
 
 
<b>Article Types</b>
 
 
*[[:Category:Evolution]]<br />
 
*[[:Category:Unused Visgroups]]<br />
 
*[[:Category:Eras]]
 
 
<b>Miscellaneous</b>
 
<!-- rename to anonhl2 patches? -->
 
 
[[:Category:Beta Patches]]
 
 
==Useful Files==
 
Various files and tools helpful for the investigative editor.
 
===Generally Useful===
 
[http://nemesis.thewavelength.net/index.php?p=26 VTFEdit], a powerful texture editor<br />
 
[http://nemesis.thewavelength.net/index.php?p=25 GCFScape], a good tool for browsing GCFs and VPKs<br />
 
[https://www.wunderboy.org/valve-hl2source-sdk-tools/#vtf_shell VTF Shell Extensions], a tool that allows you to see thumbnails for <code>.vtf</code> files
 
===Beta Stuff===
 
[http://valvearchive.com/archive/Other%20Files/Leaks/2003%20-%20Whole%20Valve%20Servers%20Compromised/ ValveArchive folder for the 2003 leak]<br />
 
[https://drive.google.com/file/d/0B7JIKUn-ZBIvR2NfT1lONHkwcXc/view?usp=sharing Pack of beta model viewers and decompilers]<br />
 
[https://drive.google.com/file/d/0B7JIKUn-ZBIvaUxYLWMwRkdlYk0/view?usp=sharing Pack of decompiled models from ScarT's infamous decompiler]<br />
 
[https://drive.google.com/drive/folders/0B7JIKUn-ZBIvU3lpX3haSUJlUG8?usp=sharing Blackfox's reference docs. CSVs of sounds used in the maps, textures, versions, etc.]
 
<!--==Wiki Colors== -->
 
<!--
 
can't figure out how to right now
 
http://vcc.wikia.com/wiki/Special:ThemeDesigner
 
-->
 
 
==Useful Wiki Stuff==
 
<span style="font-weight:normal;">Two tips for removing the unnecesary stuff wikia likes adding:</span>
 
*For galleries: Include "hideaddbutton=true" to remove the add buttons
 
*For headers: Include "<nowiki>__NOEDITSECTION__</nowiki>" anywhere in the article to remove header edit buttons.
 
===Template Index===
 
<!--
 
{| border="0" cellpadding="0" cellspacing="0" class="article-table" style="float: left; width: 100%;"
 
|-
 
! scope="col"|Template Name
 
! scope="col"|Usage
 
! scope="col"|Info
 
|-
 
|<nowiki>{{Toc-right}}</nowiki>
 
|<pre>{{Toc-right}}</pre>
 
|Place it anywhere on the page to have the table of contents align to the right.
 
|-
 
|<nowiki>{{clear}}</nowiki>
 
|<pre>{{clear}}</pre> directly over the incorrectly-formatted element.
 
|
 
|}
 
-->
 
*To have a ToC box that aligns to the right of the page, use <nowiki>{{toc-right}}</nowiki>.
 
*To format text to go past photos, use "<nowiki>{{clear}}</nowiki>".
 
 
Example:
 
[[File:Stephane-gaudette-ctf-badlands-bluebase010038-2.jpg|left|thumb|220x220px]]{{Clear}}Woo! This is below the picture!
 
 
*To create a TCRF-esque subpage box, use this -
 
{{subpage|Temporary|image=Stephane-gaudette-ctf-badlands-bluebase010038-2.jpg|text=And thus, the latin testing text was disgraced, removed, and executed.|width=75|min-width=75|pic-align=left|align=left}}
 
 
[[Category:Editor Documents]]
 
[[Category:Editor Documents]]

Revision as of 20:55, 21 January 2018

What is the VCC Wiki?

VCC Wiki is a wiki dedicated to the documentation of Valve's Cut Content. It was created in response to a perceived absence of this documentation in the more "generalist" Valve wikis.

As a result of this, our primary focus is on Valve's cut content, and the community surrounding it.

Why Not Edit?

Notice a factual error somewhere? See a formatting issue that nobody seems to have noticed? Try your hand at editing it!

Even if you don't do the job correctly, all that will happen is that someone will come over and fix it, perhaps telling you how to do it correctly the next time.

Don't be afraid to edit. Nobody blames an editor with good intentions.

Page Philosophy

Let's face it - we're not going to have a universal set of standards for everything, considering our weird and varied subject matter.

When doing something new, don't approach it with a bunch of pre-thought-out header structures in mind. Think to yourself, what would work best? Often, that's the way that gets the best results.

Subpages

It's helpful to look over these pages before editing:

Page Structures

A list of semi-standardized page structures. They might fit with what you are trying to write. The bullet point levels are representative of the header levels.

"Evolution" Structure

Overview:

  • Second-level headers are used to divide into "sections" of the particular thing's evolution.
    • Third-level headers are used after, to show what we have of that particular revision.
  • Including final versions is optional, but usually beneficial.

Works best with:

Articles with a long and notable history. Otherwise, an early version might fit better as a "notable aspect" header.

Examples:

"Timeline" Structure

Headers:

  • Major events (or years) serve as level 1 headers, dividing events.
    • Individual days where events occur serve as level 2 headers.
    • Individual events are laid out below the days with bullet points.
  • At the very end, a header for references is included.

Works best with:

Large, multi-month events, with smaller bits scattered over multiple days.

Examples:

"Weapon" Structure

Headers:

  • First, a brief description of what the weapon is, with the weapon name in bold. I.E.:

The XM29 OICW is the effective predecessor to the OSPIR. It is still in use in the leak, and thus fully present.

  • Two level two headers:
    • Overview
    • Tactics
    • Further case-by-case headers, documenting notable aspects of the weapon. I.E.:
      • Older Texture
      • Cut Grenade Launching Function
      • Facepunch Leaks
  • Another level-two header gallery, with dividing subheaders something like this:
    • Screenshots
    • Renders
    • Textures
  • A header for references. (If used!)

Works best with:

  • Articles documenting weapons. The general idea of it can be applied elsewhere, though.

Examples: