9,959
edits
Pikipedia:Glitch notes: Difference between revisions
Changed "danger" to "consequences", reflecting the change on Template:Glitch
(Update for the new format.) |
(Changed "danger" to "consequences", reflecting the change on Template:Glitch) |
||
| Line 11: | Line 11: | ||
All glitches have a table at the top, like so: | All glitches have a table at the top, like so: | ||
{|class="wikitable" | {|class="wikitable" | ||
!Reproducibility !! | !Reproducibility !! Consequences !! Versions !! Demonstration !! Other demonstrations | ||
|- | |- | ||
| <Reproducibility level> || < | | <Reproducibility level> || <Consequences for performing> || <Version exclusivity> || <external demonstration> || <other demonstrations> | ||
|} | |} | ||
| Line 21: | Line 21: | ||
**"Medium" means the glitch can't always be executed on command, but it's not necessarily difficult to do so. | **"Medium" means the glitch can't always be executed on command, but it's not necessarily difficult to do so. | ||
**"High" means the glitch can almost always be executed by following the indicated steps. | **"High" means the glitch can almost always be executed by following the indicated steps. | ||
*''' | *'''Consequences''': How good or bad the consequences for performing the glitch are. | ||
**"Harmful" means that the glitch can cause problems if not handled carefully. | **"Harmful" means that the glitch can cause problems if not handled carefully. | ||
**"Harmless" means the glitch has no side-effects, and normally, its effects are purely cosmetic. | **"Harmless" means the glitch has no side-effects, and normally, its effects are purely cosmetic. | ||
| Line 49: | Line 49: | ||
*Give your glitch a name. This name should reflect the glitch's effects well, and it should be relatively short. Read other glitch names for a general idea. | *Give your glitch a name. This name should reflect the glitch's effects well, and it should be relatively short. Read other glitch names for a general idea. | ||
*Add a sub-section for it in the correct section, ''in its correct spot, alphabetically''. If you do not feel the glitch fits into any existing section, feel free to create your own, but try to make it so that more glitches can fit into that section as well: single-glitch sections are frowned upon. | *Add a sub-section for it in the correct section, ''in its correct spot, alphabetically''. If you do not feel the glitch fits into any existing section, feel free to create your own, but try to make it so that more glitches can fit into that section as well: single-glitch sections are frowned upon. | ||
*Copy and paste the skeleton '''[[Template:Glitch# | *Copy and paste the skeleton '''[[Template:Glitch#Skeleton|here]]'''. | ||
*Fill in the fields as described above, and remove the unneeded ones. Their names are self-explanatory, but if you need help understanding the template's fields better, read [[Template:Glitch|this]], or base yourself on the wikitext of existing glitches. | *Fill in the fields as described above, and remove the unneeded ones. Their names are self-explanatory, but if you need help understanding the template's fields better, read [[Template:Glitch|this]], or base yourself on the wikitext of existing glitches. | ||
**The explanation bullet point is optional. Unless you have experience with video game development, you should leave this empty. In time, a member with sufficient experience will add a brief explanation theory to the article. | **The explanation bullet point is optional. Unless you have experience with video game development, you should leave this empty. In time, a member with sufficient experience will add a brief explanation theory to the article. | ||