Pikipedia:Glitch notes: Difference between revisions

m
Added info on the "what should happen" field.
m (Forgot this.)
m (Added info on the "what should happen" field.)
Line 34: Line 34:
*'''How to''': A brief guide explaining the steps required to execute the glitch.
*'''How to''': A brief guide explaining the steps required to execute the glitch.
*'''Notes''': Any sort of extra notes. These can detail version exclusivity of a glitch, ways to reverse its effects, ways to avoid it, etc.
*'''Notes''': Any sort of extra notes. These can detail version exclusivity of a glitch, ways to reverse its effects, ways to avoid it, etc.
*'''What should happen''': If the normal, glitch-less behavior is not obvious, it's normally pointed out here. This helps readers who are not familiar with the underlying mechanics to understand what makes the glitch an anomaly.
*'''Possible explanation''': A possible explanation to the glitch's causes, given by a member of the community with experience in video game development and programming. These explanations are '''speculative''', and only provide a theory on a possible cause for the glitch.
*'''Possible explanation''': A possible explanation to the glitch's causes, given by a member of the community with experience in video game development and programming. These explanations are '''speculative''', and only provide a theory on a possible cause for the glitch.


Line 53: Line 54:
| howto =  
| howto =  
| notes =  
| notes =  
| normal =
| explanation =  
| explanation =  
}}
}}
</pre>
</pre>
*Fill in the fields as described above. Their names should be 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.
**Use a "guide"-like style for the "how to" section, and optionally the prerequisites and notes sections, referring to the player with "you". On the effects and likely explanation sections, however, the player should be referred to as such.
**Use a "guide"-like style for the "how to" section, and optionally the prerequisites and notes sections, referring to the player with "you". On the effects and likely explanation sections, however, the player should be referred to as such.