Display title | Unwinnable by Mistake/Video Games/World of Warcraft |
Default sort key | Unwinnable by Mistake/Video Games/World of Warcraft |
Page length (in bytes) | 8,073 |
Namespace ID | 0 |
Page ID | 130736 |
Page content language | en - English |
Page content model | wikitext |
Indexing by robots | Allowed |
Number of redirects to this page | 0 |
Counted as a content page | Yes |
Number of subpages of this page | 0 (0 redirects; 0 non-redirects) |
Edit | Allow all users (infinite) |
Move | Allow all users (infinite) |
Delete | Allow all users (infinite) |
Page creator | m>Import Bot |
Date of page creation | 21:27, 1 November 2013 |
Latest editor | Robkelk (talk | contribs) |
Date of latest edit | 18:12, 25 March 2022 |
Total number of edits | 8 |
Recent number of edits (within past 180 days) | 0 |
Recent number of distinct authors | 0 |
Transcluded templates (4) | Templates used on this page:
|
Description | Content |
Article description: (description ) This attribute controls the content of the description and og:description elements. | World of Warcraft, being an open ended MMORPG, is not subject to unwinnable situations as a whole (it's more of an Endless Game). But there have been numerous occasions when specific quests or dungeons have been broken because of scripting failures or other issues. In most cases, these have to be fixed by a game patch. Notorious ones: |