Panic - Revision history

Umbire the Phantom: /* Mechanics */ touch-ups

2024-02-19T10:16:35Z

‎Mechanics: touch-ups

SophiaMakoto: /* Mechanics */ Segaulting

2022-06-10T17:34:47Z

‎Mechanics: Segaulting

Ardub23: Broke first paragraph into shorter sentences; recast "Rumor" trivia section as extra paragraph in lead section

2021-10-02T05:11:02Z

Broke first paragraph into shorter sentences; recast "Rumor" trivia section as extra paragraph in lead section

Ais523: /* Variants */ new section

2019-11-14T02:50:11Z

‎Variants: new section

Quantum Immortal: split little summary, rumor

2016-04-15T13:02:38Z

split little summary, rumor

ChasonBot at 13:37, 20 December 2015

2015-12-20T13:37:23Z

Darth l33t at 16:18, 2 December 2013

2013-12-02T16:18:03Z

Tjr: link to individual bug

2013-03-09T08:24:12Z

link to individual bug

Bcode: to results -> to result

2012-06-04T14:17:43Z

to results -> to result

SGrunt: link to messages; refer to impossible

2012-04-19T23:46:51Z

link to messages; refer to impossible

@@ Line 4: / Line 4: @@
 ==Mechanics==
-It is very rare for a normal game to result in a panic; however, several [[bugs in NetHack 3.4.3]] revolve around panics, usually involving monsters or objects being destroyed under unusual circumstances; exceptions include [[C343-23]], "Dungeon collapses after vault guard fails to lead you out.", and [[bug#C343-383|C343-383]], "Applying a bullwhip while hero is at edge of map may cause a panic or crash."
+It is very rare for a normal game to result in a panic; however, several [[bugs in NetHack 3.4.3]] revolve around panics, usually involving monsters or objects being destroyed under unusual circumstances; exceptions include [[C343-23]] ("Dungeon collapses after vault guard fails to lead you out."), and [[bug#C343-383|C343-383]] ("Applying a bullwhip while hero is at edge of map may cause a panic or crash.").
 It is handled through the [[Source:end.c#line251|panic()]] function in [[Source:end.c]].
@@ Line 10: / Line 10: @@
 Less serious errors can result in an [[impossible]] message.
-In exceedingly rare circumstances, NetHack may [[Segfault]] instead, without any chance to continue.
+In exceedingly rare circumstances, NetHack may [[segfault]] instead, without any chance to continue.
 ==Variants==

← Older revision		Revision as of 17:34, 10 June 2022
Line 9:		Line 9:

	Less serious errors can result in an [[impossible]] message.		Less serious errors can result in an [[impossible]] message.
		+
		+	In exceedingly rare circumstances, NetHack may [[Segfault]] instead, without any chance to continue.

	==Variants==		==Variants==

@@ Line 1: / Line 1: @@
-NetHack '''panics''' when it reaches a state where it is completely impossible to continue the current session by terminating the game immediately with the messages "'''[[Source:end.c#line260|Oops...]] [[Source:end.c#line267|Suddenly, the dungeon collapses.]]'''", sometimes generating a backup [[Saving|saved game]] if the game can be recovered to a point where it is continuable.
+''NetHack'' '''panics''' when it reaches a state where it is completely impossible to continue the current session. Panicking terminates the game immediately with the messages "'''Oops... Suddenly, the dungeon collapses.'''"{{refsrc|end.c|260}} If the game can be recovered to a point where it was continuable, a backup [[Saving|saved game]] may be generated.
 ==Mechanics==
@@ Line 11: / Line 13: @@
 In [[NetHack 4]], [[NetHack Fourk]] and [[FIQHack]], a panic gives the player a choice of how to proceed. One option is to reload the game from a backup save (potentially allowing the game to continue, as long as the sequence of events leading up to the panic are not repeated). The other is to leave the save file in its current state, containing a record of all events up to the panic; this leaves the game unplayable in the short term, but may permit gameplay to resume from that point via playing on some future updated game executable in which the bug is fixed.
 [[Category:Bugs]]
 {{nethack-343}}

← Older revision		Revision as of 02:50, 14 November 2019
Line 7:		Line 7:

	Less serious errors can result in an [[impossible]] message.		Less serious errors can result in an [[impossible]] message.
		+
		+	==Variants==
		+
		+	In [[NetHack 4]], [[NetHack Fourk]] and [[FIQHack]], a panic gives the player a choice of how to proceed. One option is to reload the game from a backup save (potentially allowing the game to continue, as long as the sequence of events leading up to the panic are not repeated). The other is to leave the save file in its current state, containing a record of all events up to the panic; this leaves the game unplayable in the short term, but may permit gameplay to resume from that point via playing on some future updated game executable in which the bug is fixed.

	==Rumor==		==Rumor==

@@ Line 1: / Line 1: @@
-NetHack '''panics''' when it reaches a state where it is completely impossible to continue the current session by terminating the game immediately with the messages "'''[[Source:end.c#line260|Oops...]] [[Source:end.c#line267|Suddenly, the dungeon collapses.]]'''", sometimes generating a backup [[Saving|saved game]] if the game can be recovered to a point where it is continuable. It is handled through the [[Source:end.c#line251|panic()]] function in [[Source:end.c]].
+NetHack '''panics''' when it reaches a state where it is completely impossible to continue the current session by terminating the game immediately with the messages "'''[[Source:end.c#line260|Oops...]] [[Source:end.c#line267|Suddenly, the dungeon collapses.]]'''", sometimes generating a backup [[Saving|saved game]] if the game can be recovered to a point where it is continuable.
 It is very rare for a normal game to result in a panic; however, several [[bugs in NetHack 3.4.3]] revolve around panics, usually involving monsters or objects being destroyed under unusual circumstances; exceptions include [[C343-23]], "Dungeon collapses after vault guard fails to lead you out.", and [[bug#C343-383|C343-383]], "Applying a bullwhip while hero is at edge of map may cause a panic or crash."
 Less serious errors can result in an [[impossible]] message.
 [[Category:Bugs]]
 {{nethack-343}}

← Older revision		Revision as of 13:37, 20 December 2015
Line 6:		Line 6:

	[[Category:Bugs]]		[[Category:Bugs]]
		+	{{nethack-343}}

← Older revision		Revision as of 16:18, 2 December 2013
Line 1:		Line 1:
−	NetHack '''panics''' when it reaches a state where it is completely impossible to continue the current session by terminating the game immediately with the messages "'''[[Source:end.c#~~260~~\|Oops...]] [[Source:end.c#~~267~~\|Suddenly, the dungeon collapses.]]'''", sometimes generating a backup [[Saving\|saved game]] if the game can be recovered to a point where it is continuable. It is handled through the [[Source:end.c#line251\|panic()]] function in [[Source:end.c]].	+	NetHack '''panics''' when it reaches a state where it is completely impossible to continue the current session by terminating the game immediately with the messages "'''[[Source:end.c#line260\|Oops...]] [[Source:end.c#line267\|Suddenly, the dungeon collapses.]]'''", sometimes generating a backup [[Saving\|saved game]] if the game can be recovered to a point where it is continuable. It is handled through the [[Source:end.c#line251\|panic()]] function in [[Source:end.c]].

	It is very rare for a normal game to result in a panic; however, several [[bugs in NetHack 3.4.3]] revolve around panics, usually involving monsters or objects being destroyed under unusual circumstances; exceptions include [[C343-23]], "Dungeon collapses after vault guard fails to lead you out.", and [[bug#C343-383\|C343-383]], "Applying a bullwhip while hero is at edge of map may cause a panic or crash."		It is very rare for a normal game to result in a panic; however, several [[bugs in NetHack 3.4.3]] revolve around panics, usually involving monsters or objects being destroyed under unusual circumstances; exceptions include [[C343-23]], "Dungeon collapses after vault guard fails to lead you out.", and [[bug#C343-383\|C343-383]], "Applying a bullwhip while hero is at edge of map may cause a panic or crash."

@@ Line 1: / Line 1: @@
-NetHack '''panics''' when it reaches a state where it is completely impossible to continue the current session by terminating the game immediately with the messages "'''Oops... Suddenly, the dungeon collapses'''", sometimes generating a backup [[Saving|saved game]] if the game can be recovered to a point where it is continuable. It is handled through the [[Source:end.c#line251|panic()]] function in [[Source:end.c]].
+NetHack '''panics''' when it reaches a state where it is completely impossible to continue the current session by terminating the game immediately with the messages "'''[[Source:end.c#260|Oops...]] [[Source:end.c#267|Suddenly, the dungeon collapses.]]'''", sometimes generating a backup [[Saving|saved game]] if the game can be recovered to a point where it is continuable. It is handled through the [[Source:end.c#line251|panic()]] function in [[Source:end.c]].
 It is very rare for a normal game to results in a panic; however, several [[bugs in NetHack 3.4.3]] revolve around panics, usually involving monsters or objects being destroyed under unusual circumstances; exceptions include [[C343-23]], "Dungeon collapses after vault guard fails to lead you out.", and C343-383, "Applying a bullwhip while hero is at edge of map may cause a panic or crash."
 [[Category:Bugs]]