Difference between revisions of "Glitch Theories"
m (Adding a posting section.) |
(Adding sigs reminder.) |
||
| Line 19: | Line 19: | ||
*... | *... | ||
*... | *... | ||
| + | |||
| + | (Theorized by: Glitching Legacy) | ||
| + | (Posted by: [[User:Glitching Legacy|Glitching Legacy]] ([[User talk:Glitching Legacy|talk]]) 18:06, 23 December 2013 (EST)) | ||
Here's how it should be formatted: (Note that when typing it, you don't insert the parenthesis) | Here's how it should be formatted: (Note that when typing it, you don't insert the parenthesis) | ||
| Line 33: | Line 36: | ||
(===) Notes (===) | (===) Notes (===) | ||
(List the notes, if any) | (List the notes, if any) | ||
| + | |||
| + | (Theorized by: (user)) | ||
| + | (Posted by: (user)) | ||
__FORCETOC__ | __FORCETOC__ | ||
= Theories = | = Theories = | ||
Revision as of 23:06, 23 December 2013
Contents |
Guidelines
This is where users can post theories for possible glitches. These possible glitches must be useful in at least 1 way, but they don't have to be speed run legal. They just need to be fun! That's all! Here's an example:
Twilight Princess: Example
Instructions
- Do this.
- Do that.
- Then this.
- Then that.
- Finally, ...
Possible Results
This might happen, which might cause this. And so on...
Notes
- ...
- ...
- ...
(Theorized by: Glitching Legacy) (Posted by: Glitching Legacy (talk) 18:06, 23 December 2013 (EST))
Here's how it should be formatted: (Note that when typing it, you don't insert the parenthesis)
(==) (Game the theory is for) : (Name of theory) (==)
(===) Instructions (===) (List the instructions for testing the theory)
(===) Possible Results (===) (Type what may or may not happen and, if known, why it may or may not happen)
(===) Notes (===) (List the notes, if any)
(Theorized by: (user)) (Posted by: (user))
