Display title | Overclocking Attack |
Default sort key | Overclocking Attack |
Page length (in bytes) | 13,195 |
Namespace ID | 0 |
Page ID | 34412 |
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) |
Page image | |
Edit | Allow all users (infinite) |
Move | Allow all users (infinite) |
Delete | Allow all users (infinite) |
Page creator | prefix>Import Bot |
Date of page creation | 21:27, 1 November 2013 |
Latest editor | Looney Toons (talk | contribs) |
Date of latest edit | 20:06, 2 November 2021 |
Total number of edits | 12 |
Recent number of edits (within past 180 days) | 0 |
Recent number of distinct authors | 0 |
Transcluded templates (7) | Templates used on this page:
|
Description | Content |
Article description: (description ) This attribute controls the content of the description and og:description elements. | A popular strategy to destroy the Big Bad's big doomsday device is to overwork it until it blows up. Overclocking any Applied Phlebotinum, especially the evil kind, won't just shut it down but will cause it to explode beyond repair. But in this case, the "explosive" part of Explosive Overclocking is not the risk but the goal. Then your job is done, since, of course, there are No Plans, No Prototype, No Backup. |