mNo edit summary Tag: sourceedit |
|||
(22 intermediate revisions by 16 users not shown) | |||
Line 1: | Line 1: | ||
− | [[File:Third server crash.png |
+ | [[File:Third server crash.png|thumb|The old secondary world select menu during a blackout.]] |
⚫ | |||
+ | [[File:Offline world message.png|thumb|Message displayed when a player attempts to log into a world during a server blackout.]] |
||
A '''server blackout''' is the unexpected crash of a server, typically resulting in all players being logged out for an extended period of time. Blackouts usually affect most, if not all, game [[server]]s and may affect other ''RuneScape'' facilities such as the [[RuneScape Forums|forums]] and main website. |
A '''server blackout''' is the unexpected crash of a server, typically resulting in all players being logged out for an extended period of time. Blackouts usually affect most, if not all, game [[server]]s and may affect other ''RuneScape'' facilities such as the [[RuneScape Forums|forums]] and main website. |
||
− | + | Blackouts are generally caused by a technical failure on the part of [[Jagex]]. Players who suffer from blackouts can only wait until the problem is fixed by Jagex. In some cases, a rollback is necessary. A rollback is an operation that returns server databases to their previous state from before the blackout occurred. On rare occasions where a rollback is performed, any changes that occurred between the crash and the previous state are lost. This includes gained experience, trade transactions, quest progress, etc. Rollbacks typically revert the servers to the state they were in anywhere from 15 minutes to one hour prior. |
|
⚫ | |||
⚫ | |||
⚫ | |||
− | |||
− | In the following subpages, each notable blackout that has occurred during the history of ''[[RuneScape]]'' is documented, along with the reasons given for the blackout. All times are noted in UTC, unless otherwise stated. (Note that this is one hour behind British Summer Time, or BST, during the summer due to daylight savings.) |
||
− | |||
− | ==List of server blackouts in 2007== |
||
− | {{main|Server blackout/List of server blackouts in 2007}} |
||
− | |||
− | ==List of server blackouts in 2008== |
||
− | {{main|Server blackout/List of server blackouts in 2008}} |
||
− | |||
− | ==List of server blackouts in 2009== |
||
− | {{main|Server blackout/List of server blackouts in 2009}} |
||
− | |||
− | ==List of server blackouts in 2010== |
||
− | {{main|Server blackout/List of server blackouts in 2010}} |
||
− | |||
− | ==List of server blackouts in 2011== |
||
− | {{main|Server blackout/List of server blackouts in 2011}} |
||
− | |||
− | ==List of server blackouts in 2012== |
||
− | {{main|Server blackout/List of server blackouts in 2012}} |
||
− | |||
− | ==List of server blackouts in 2013== |
||
− | <!--{{main|Server blackout/List of server blackouts in 2013}}-->First blackout 11-1-2013 at roughly 18:40 GMT |
||
[[Category:Mechanics]] |
[[Category:Mechanics]] |
Latest revision as of 02:32, 13 August 2015
A server blackout is the unexpected crash of a server, typically resulting in all players being logged out for an extended period of time. Blackouts usually affect most, if not all, game servers and may affect other RuneScape facilities such as the forums and main website.
Blackouts are generally caused by a technical failure on the part of Jagex. Players who suffer from blackouts can only wait until the problem is fixed by Jagex. In some cases, a rollback is necessary. A rollback is an operation that returns server databases to their previous state from before the blackout occurred. On rare occasions where a rollback is performed, any changes that occurred between the crash and the previous state are lost. This includes gained experience, trade transactions, quest progress, etc. Rollbacks typically revert the servers to the state they were in anywhere from 15 minutes to one hour prior.
During an intentional server blackout, worlds on the select screen are listed as "OFFLINE", as opposed to displaying the number of players logged in. However, on an unexpected crash, the login server simply assumes that nobody is connected to that server.