Farming - Revision history

Umbire the Phantom: pothole

2026-05-18T23:01:02Z

pothole

Umbire the Phantom: /* Kraken farming */ bleh

2025-07-02T17:26:00Z

‎Kraken farming: bleh

Umbire the Phantom: /* Kraken farming */ damnit all!

2025-07-02T17:25:27Z

‎Kraken farming: damnit all!

Umbire the Phantom: /* Kraken farming */ how lol

2025-07-02T17:25:12Z

‎Kraken farming: how lol

Umbire the Phantom: small copyedit

2025-07-02T17:24:56Z

small copyedit

Aximili: /* Pudding farming */ wording

2024-05-26T20:06:38Z

‎Pudding farming: wording

Umbire the Phantom: /* References */ var

2024-01-20T09:43:37Z

‎References: var

Umbire the Phantom: /* Throne farming */ paren

2024-01-20T09:40:13Z

‎Throne farming: paren

Umbire the Phantom: /* Throne farming */ typo, frac

2024-01-20T09:37:33Z

‎Throne farming: typo, frac

Umbire the Phantom: /* Death farming */ title for thread

2022-12-12T06:14:34Z

‎Death farming: title for thread

@@ Line 133: / Line 133: @@
 The result will be many thousand death-dropped items and a very high score. If the number of death-dropped items exceeds 32,767 on the same square, the game will probably crash,<ref>[http://groups.google.com/group/rec.games.roguelike.nethack/browse_thread/thread/3f97bcf24f034605/5f51813967ab27a8?q=#5f51813967ab27a8 RGRN thread: [BUG] menucolors patch segfaults]</ref> so periodically checking Death's square and redistributing the items (possibly by teleporting them away, or polymorphing them together) is necessary. This is because the number of items present on a [[square]] is stored in a [[signed variable|signed short]] when the items are listed.
-This method no longer works as of 3.6.0, because Riders can [[displace]] other monsters; thus, the jelly fort will not work to contain Death. It is still possible to kill Death (or other Riders) arbitrarily many times, but not with this method of automation. Additionally, revived monsters give diminishing experience points and score, down to {{frac|64}} of the base value, which means that it will take much longer to achieve billions of points.
+This method no longer works as of 3.6.0, because Riders can [[M3_DISPLACES|displace other monsters]]; thus, the jelly fort will not work to contain Death. It is still possible to kill Death (or other Riders) arbitrarily many times, but not with this method of automation. Additionally, revived monsters give diminishing experience points and score, down to {{frac|64}} of the base value, which means that it will take much longer to achieve billions of points.
 ==References==

@@ Line 77: / Line 77: @@
 ===Kraken farming===
-In 3.4.3, [[kraken]] can be killed trivially when on dry land, and their corpses can be revived using [[undead turning]]. This means you can continue killing the same monsters near-indefinitely, racking up a very high score with very little effort. To get the most out of such farming, you can trap kraken by digging walls in the following pattern:
+In 3.4.3, [[kraken]] can be killed trivially when on dry land, and their corpses can be revived using a [[wand of undead turning]] or the {{+ of|turn undead}} spell. This means you can continue killing the same monsters near-indefinitely, racking up a very high score with very little effort. To get the most out of such farming, you can trap kraken by digging walls in the following pattern:
 <div class="ttyscreen"><replacecharsblock rules="ttymap">
@@ Line 92: / Line 92: @@
 </replacecharsblock></div>
-This allows a farmer to repeatedly cast {{+ of|turn undead}} and {{+ of|finger of death}} along the diagonals with copy-and-paste&mdash;kraken are [[huge]] monsters, and so cannot squeeze diagonally between walls.
+This allows a farmer to e.g. repeatedly cast {{+ of|turn undead}} and {{+ of|finger of death}} along the diagonals with copy-and-paste&mdash;kraken are [[huge]] monsters, and so cannot squeeze diagonally between walls.
 NetHack 3.6.0 and later versions make this strategy vastly more dangerous, if not impossible: kraken will no longer revive while on land, and leaving them in water puts the hero at risk of instadeath by [[drowning]] attack.

@@ Line 92: / Line 92: @@
 </replacecharsblock></div>
-This allows a farmer to repeatedly cast {{+ of|undead turning}} and {{+ of|finger of death}} along the diagonals with copy-and-paste&mdash;kraken are [[huge]] monsters, and so cannot squeeze diagonally between walls.
+This allows a farmer to repeatedly cast {{+ of|turn undead}} and {{+ of|finger of death}} along the diagonals with copy-and-paste&mdash;kraken are [[huge]] monsters, and so cannot squeeze diagonally between walls.
 NetHack 3.6.0 and later versions make this strategy vastly more dangerous, if not impossible: kraken will no longer revive while on land, and leaving them in water puts the hero at risk of instadeath by [[drowning]] attack.

@@ Line 92: / Line 92: @@
 </replacecharsblock></div>
-This allows a farmer to repeatedly cast {{of +|undead turning}} and {{+ of|finger of death}} along the diagonals with copy-and-paste&mdash;kraken are [[huge]] monsters, and so cannot squeeze diagonally between walls.
+This allows a farmer to repeatedly cast {{+ of|undead turning}} and {{+ of|finger of death}} along the diagonals with copy-and-paste&mdash;kraken are [[huge]] monsters, and so cannot squeeze diagonally between walls.
 NetHack 3.6.0 and later versions make this strategy vastly more dangerous, if not impossible: kraken will no longer revive while on land, and leaving them in water puts the hero at risk of instadeath by [[drowning]] attack.

@@ Line 92: / Line 92: @@
 </replacecharsblock></div>
-This allows a farmer to repeatedly cast [[undead turning]] and [[finger of death]] along the diagonals with copy-and-paste - kraken are [[Physical size|huge]] monsters, and so cannot squeeze diagonally between walls.
+This allows a farmer to repeatedly cast {{of +|undead turning}} and {{+ of|finger of death}} along the diagonals with copy-and-paste&mdash;kraken are [[huge]] monsters, and so cannot squeeze diagonally between walls.
-.6.0 and later versions make this strategy vastly more dangerous, if not impossible - kraken will no longer revive while on land, and leaving them in water puts the player at risk of instadeath by [[drowning]] attack.
+NetHack 3.6.0 and later versions make this strategy vastly more dangerous, if not impossible: kraken will no longer revive while on land, and leaving them in water puts the hero at risk of instadeath by [[drowning]] attack.
 ===Pudding farming===
 {{main|Pudding farming}}
-In 3.4.3, a common tactic was to advance your character to the point where they could easily defeat [[black pudding]]s, then carefully use weak weapons to divide them without killing them; this allowed players to "farm" by killing as many puddings as they wish for [[death drop]]ped items, and their corpses can be [[sacrifice]]d for a variety of benefits. Players can continue this process (and even automate it) until they possess thousands of hit points, maximum [[AC]], and hundreds of [[wand of wishing|wands of wishing]]&mdash;at a point where a player is considering this and has the means to do so, the primary obstacle is the amount of effort they are willing to dedicate (which ironically proved an effective deterrent).
+In 3.4.3, a common tactic was to advance your character to the point where they could easily defeat [[black pudding]]s, then carefully use weak weapons to divide them without killing them; this allowed players to "farm" by killing as many puddings as they wish for [[death drop]]ped items, and their corpses can be [[sacrifice]]d for a variety of benefits. Players can continue this process (and even automate it) until they possess thousands of hit points, maximum [[AC]], and hundreds of [[wands of wishing]]&mdash;at a point where a player is considering this and has the means to do so, the primary obstacle is the amount of effort they are willing to dedicate (which ironically proved an effective deterrent).
 .6.0's changes rendered this method of farming completely ineffective by removing the majority of its benefits. One such major change is the <code>mcloned</code> bitfield that tracks cloned monsters, used to prevent them from leaving death drops of any kind. Another such change is the addition of [[glob]]s, which replace regular corpses as the remains of black puddings; these are left behind in a special method similar to [[golem]]s, and thus puddings can no longer provide any death drops or sacrifice material.

@@ Line 137: / Line 137: @@
 ==References==
 <references/>
-{{nethack-366}}
+{{nethack-367}}
 [[Category:Farming|*]]

@@ Line 105: / Line 105: @@
 Throne farming was once perhaps the fastest way in the game to generate lots of monsters, and the only method available without breaking any conducts; monster generation would also not use up a turn or risk any damage to the throne, allowing indefinite farming for whatever items you desire (from [[dragon scales]] to [[dragon scale mail|convert into mail]] to various [[potion]]s, [[wand]]s and [[scroll]]s. This is no longer possible as of 3.6.0, since confused looting now uses up a turn and has a {{frac|10}} chance of marking the throne as "looted", preventing further monster generation from that throne.
-For 3.4.3, earlier versions and some variants based on them, undiggable no-teleport levels work best to prevent monsters from ruining your setup; at most, you will only have to use up one charge from a wand of teleportation to send a troublesome monster off. Each [[quest]] home level generates the quest leader on a suitable throne - you can make them wander away if you move adjacent on a free turn, and then say no to the "really attack?" prompt. You might want to engrave concentric circles of [[Elbereth]] (as done when [[DSM#Acquiring dragon scales|farming dragon scales]] and/or use a boulder fort to protect yourself from ranged attacks. Illiterate conduct players can get a monster to read the [[scroll of earth]], then stand on a scroll of scare monster and confuse themselves, using a cursed [[unicorn horn]] if they did not start with a spell to forget.
+For 3.4.3, earlier versions and some variants based on them, undiggable no-teleport levels work best to prevent monsters from ruining your setup; at most, you will only have to use up one charge from a wand of teleportation to send a troublesome monster off. Each [[quest]] home level generates the quest leader on a suitable throne - you can make them wander away if you move adjacent on a free turn, and then say no to the "really attack?" prompt. You might want to engrave concentric circles of [[Elbereth]] (as done when [[DSM#Acquiring dragon scales|farming dragon scales]]) and/or use a boulder fort to protect yourself from ranged attacks. Illiterate conduct players can get a monster to read the [[scroll of earth]], then stand on a scroll of scare monster and confuse themselves, using a cursed [[unicorn horn]] if they did not start with a spell to forget.
 At this point, the only threat left is the potential of [[sickness]]; the chance of dying to terminal illness can be almost completely removed by [[polymorph]]ing into a [[ghoul]] to gain [[sickness resistance]] beforehand, or applying a preferably-blessed unicorn horn to cure it. Unattended copy-paste farming is only possible if you confuse yourself with an expired spell or are [[amulet of unchanging|permanently a ghoul]]; setting <code>[[option#menustyle|menustyle=traditional]]</code> in your config file can make the paste script execute the spellcasting faster.

@@ Line 103: / Line 103: @@
 ===Throne farming===
-Throne farming was once perhaps the fastest way in the game to generate lots of monsters, and the only method available without breaking any conducts; monster generation would also not use up a turn or risk any damage to the throne, allowing indefinite farming for whatever items you desire (from [[dragon scales]] to [[dragon scale mail|convert into mail]] to various [[potion]]s, [[wand]]s and [[scroll]]s. This is no longer possible as of 3.6.0, since confused looting now uses up a turn and has a 10% change of marking the throne as "looted", preventing further monster generation from that throne.
+Throne farming was once perhaps the fastest way in the game to generate lots of monsters, and the only method available without breaking any conducts; monster generation would also not use up a turn or risk any damage to the throne, allowing indefinite farming for whatever items you desire (from [[dragon scales]] to [[dragon scale mail|convert into mail]] to various [[potion]]s, [[wand]]s and [[scroll]]s. This is no longer possible as of 3.6.0, since confused looting now uses up a turn and has a {{frac|10}} chance of marking the throne as "looted", preventing further monster generation from that throne.
 For 3.4.3, earlier versions and some variants based on them, undiggable no-teleport levels work best to prevent monsters from ruining your setup; at most, you will only have to use up one charge from a wand of teleportation to send a troublesome monster off. Each [[quest]] home level generates the quest leader on a suitable throne - you can make them wander away if you move adjacent on a free turn, and then say no to the "really attack?" prompt. You might want to engrave concentric circles of [[Elbereth]] (as done when [[DSM#Acquiring dragon scales|farming dragon scales]] and/or use a boulder fort to protect yourself from ranged attacks. Illiterate conduct players can get a monster to read the [[scroll of earth]], then stand on a scroll of scare monster and confuse themselves, using a cursed [[unicorn horn]] if they did not start with a spell to forget.

@@ Line 131: / Line 131: @@
 In this example, Death is trapped between [[blue jelly|blue jellies]] and a [[boulder]]. He cannot move, but you can hit him with a polearm while he is in line of sight. Once he's dead (in one hit), attempt to push the boulder over his corpse. This will revive him. You can then repeat the procedure. You can work out the exact sequence of key strokes used in a complete cycle of this process (in this case, for example, "aahy.jyk"), and copy this line a few thousand times in a text editor, then paste the whole lot into the NetHack interface.
-The result will be many thousand death-dropped items and a very high score. If the number of death-dropped items exceeds 32,767 on the same square, the game will probably crash,<ref>[http://groups.google.com/group/rec.games.roguelike.nethack/browse_thread/thread/3f97bcf24f034605/5f51813967ab27a8?q=#5f51813967ab27a8 RGRN thread]</ref> so periodically checking Death's square and redistributing the items (possibly by teleporting them away, or polymorphing them together) is necessary. This is because the number of items present on a [[square]] is stored in a [[signed variable|signed short]] when the items are listed.
+The result will be many thousand death-dropped items and a very high score. If the number of death-dropped items exceeds 32,767 on the same square, the game will probably crash,<ref>[http://groups.google.com/group/rec.games.roguelike.nethack/browse_thread/thread/3f97bcf24f034605/5f51813967ab27a8?q=#5f51813967ab27a8 RGRN thread: [BUG] menucolors patch segfaults]</ref> so periodically checking Death's square and redistributing the items (possibly by teleporting them away, or polymorphing them together) is necessary. This is because the number of items present on a [[square]] is stored in a [[signed variable|signed short]] when the items are listed.
 This method no longer works as of 3.6.0, because Riders can [[displace]] other monsters; thus, the jelly fort will not work to contain Death. It is still possible to kill Death (or other Riders) arbitrarily many times, but not with this method of automation. Additionally, revived monsters give diminishing experience points and score, down to {{frac|64}} of the base value, which means that it will take much longer to achieve billions of points.