Difference between revisions of "Talk:Corpse"

From NetHackWiki
Jump to navigation Jump to search
(corpse generation odds)
Line 1: Line 1:
 
==time to rot /food poisoning==
 
==time to rot /food poisoning==
 
It says here corpses start to rot after 30 turns, source-diving over at [[Food poisoning]] results in 60 turns. So what is the matter - is 30 turns just a "safe lower bound" in case some monsters leave pre-aged corpses, do player and monster turns count separately and make up the factor 2, or is 30 plain wrong? -[[User:Tjr|Tjr]] 22:21, 22 May 2009 (UTC)
 
It says here corpses start to rot after 30 turns, source-diving over at [[Food poisoning]] results in 60 turns. So what is the matter - is 30 turns just a "safe lower bound" in case some monsters leave pre-aged corpses, do player and monster turns count separately and make up the factor 2, or is 30 plain wrong? -[[User:Tjr|Tjr]] 22:21, 22 May 2009 (UTC)
 +
:30 turns is too old to sacrifice, 60 makes you sick, IIRC. --[[User:AileTheAlien|AileTheAlien]] 20:06, 13 February 2011 (UTC)
  
 
Do not know if this is a bug, but once I tried to eat the corpse of newt told me that the corpse is rotten, but dead body was very fresh (2-3 turn). The corpse was not cursed, I tested it on the altar. Someone else happened to you was on something?
 
Do not know if this is a bug, but once I tried to eat the corpse of newt told me that the corpse is rotten, but dead body was very fresh (2-3 turn). The corpse was not cursed, I tested it on the altar. Someone else happened to you was on something?
Line 14: Line 15:
 
::Is the 33% reduction correct? I thought it was 1/9 if killed by the player, and 1/3 if killed by monsters or traps. --[[User:Tjr|Tjr]] 07:45, 25 January 2011 (UTC)
 
::Is the 33% reduction correct? I thought it was 1/9 if killed by the player, and 1/3 if killed by monsters or traps. --[[User:Tjr|Tjr]] 07:45, 25 January 2011 (UTC)
 
:::I added information based on mon.c, line 26. It contains a #define used in functions corpse_chance (what I was looking at, as it is where I also got the regular corpse generation odds) and also xkilled. xkilled is the function called when the player kills a monster, so yes the 1/3 chances do stack: 1/3rd chance of the corpse not being generated in xkilled and another 1/3 of the corpse not being generated in corpse_chance. Interestingly, if a monster is killed in a pit with a boulder over it, no corpse is generated either. -- [[User:Qazmlpok|Qazmlpok]] 13:15, 25 January 2011 (UTC)
 
:::I added information based on mon.c, line 26. It contains a #define used in functions corpse_chance (what I was looking at, as it is where I also got the regular corpse generation odds) and also xkilled. xkilled is the function called when the player kills a monster, so yes the 1/3 chances do stack: 1/3rd chance of the corpse not being generated in xkilled and another 1/3 of the corpse not being generated in corpse_chance. Interestingly, if a monster is killed in a pit with a boulder over it, no corpse is generated either. -- [[User:Qazmlpok|Qazmlpok]] 13:15, 25 January 2011 (UTC)
 +
 +
== Acid Blob Corpses ==
 +
The info in the Special Corpse Behavior section says that acid blob corpses are always safe to eat. Is this specific to Vanilla? IIRC, I've been food-poisoned by eating old acid blobs in SLASH'EM. --[[User:AileTheAlien|AileTheAlien]] 20:06, 13 February 2011 (UTC)

Revision as of 20:06, 13 February 2011

time to rot /food poisoning

It says here corpses start to rot after 30 turns, source-diving over at Food poisoning results in 60 turns. So what is the matter - is 30 turns just a "safe lower bound" in case some monsters leave pre-aged corpses, do player and monster turns count separately and make up the factor 2, or is 30 plain wrong? -Tjr 22:21, 22 May 2009 (UTC)

30 turns is too old to sacrifice, 60 makes you sick, IIRC. --AileTheAlien 20:06, 13 February 2011 (UTC)

Do not know if this is a bug, but once I tried to eat the corpse of newt told me that the corpse is rotten, but dead body was very fresh (2-3 turn). The corpse was not cursed, I tested it on the altar. Someone else happened to you was on something?

There are 3 meanings of rotten: 1) corpse makes you confused, blind, or unconcious, 2) gives food poisoning, 3) corpse disappears spontaneously. Yes, you can get number one right away, and yes, that's a bug. In the same vein, if you continue eating the partially eaten comestible, you will never get the effect, but if you eat something in between, you always do. --Tjr 10:44, 25 January 2011 (UTC)

corpses, wishes and genocide

may I wish for a corpse of a race I have genocidedNdwolfwood 04:35, 20 December 2010 (UTC)

You get a random (non-genocided) corpse. Wish#Wishing_for_a_monster_type. --Tjr 10:28, 20 December 2010 (UTC)

corpse generation odds

This section doesn't include how graveyards affect undead corpse generation. It should probably list all levels with a similar effect (eg. castle).--Noims 17:02, 24 January 2011 (UTC)

Done. -- Qazmlpok 17:44, 24 January 2011 (UTC)
Is the 33% reduction correct? I thought it was 1/9 if killed by the player, and 1/3 if killed by monsters or traps. --Tjr 07:45, 25 January 2011 (UTC)
I added information based on mon.c, line 26. It contains a #define used in functions corpse_chance (what I was looking at, as it is where I also got the regular corpse generation odds) and also xkilled. xkilled is the function called when the player kills a monster, so yes the 1/3 chances do stack: 1/3rd chance of the corpse not being generated in xkilled and another 1/3 of the corpse not being generated in corpse_chance. Interestingly, if a monster is killed in a pit with a boulder over it, no corpse is generated either. -- Qazmlpok 13:15, 25 January 2011 (UTC)

Acid Blob Corpses

The info in the Special Corpse Behavior section says that acid blob corpses are always safe to eat. Is this specific to Vanilla? IIRC, I've been food-poisoned by eating old acid blobs in SLASH'EM. --AileTheAlien 20:06, 13 February 2011 (UTC)