| Display title | Gameplay Derailment |
| Default sort key | Gameplay Derailment |
| Page length (in bytes) | 24,755 |
| Namespace ID | 0 |
| Page ID | 99179 |
| 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 | 1 (0 redirects; 1 non-redirect) |
| 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 | 12:53, 8 October 2020 |
| Total number of edits | 14 |
| Recent number of edits (within past 180 days) | 0 |
| Recent number of distinct authors | 0 |
| Transcluded templates (5) | Templates used on this page:
|
Description | Content |
Article description: (description)
This attribute controls the content of the description and og:description elements. | When a game is made, it usually undergoes extensive testing, to ensure that the gameplay goes smoothly. Unfortunately, then it goes into the hands of the public, enters what is effectively the largest and longest playtesting period ever. And it usually picks up what the normal testers didn't catch. Any glitches, combinations, or exploits the game testers or programmers missed, you can be sure that the players will find it, sooner or later. |