Difference between revisions of "Autopickup exception"

From NetHackWiki
Jump to navigation Jump to search
(→‎How to use it effectively)
(→‎Corpses: potholes, rephrase)
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Tocright}}
 
{{Tocright}}
−
'''AUTOPICKUP_EXCEPTION''' is a configuration option that allows you to define what items are automatically picked up, with more precision than [[pickup_types]] gives. You also need to have [[autopickup]] on and [[pickup_types]] match the AUTOPICKUP_EXCEPTION -lines. Highly recommended but not necessary is adapting [[pickup_burden]].
+
'''AUTOPICKUP_EXCEPTION''' is a configuration option that allows you to define what items are automatically picked up, based on the name of the item. This gives more precision on top of [[pickup_types]]. You need to have [[autopickup]] on for autopickup exceptions to be active.
  
−
OPTIONS=autopickup
+
In NetHack 3.6 autopickup exceptions are [[Compile-time options#AUTOPICKUP_EXCEPTIONS|compiled in by default]]. The [[Nethack.alt.org#NetHack 3.4.3 NAO|NAO version of NetHack 3.4.3]] has them as well.
−
OPTIONS=pickup_types:$?!/(
 
−
OPTIONS=pickup_burden:unencumbered
 
−
 
 
−
In NetHack 3.6 [[Compile-time options#AUTOPICKUP_EXCEPTIONS|autopickup exceptions]] are compiled in by default. [[NAO]] has them as well.
 
−
 
 
−
You can either define the exceptions in the [[options]] screen or in your [[configuration file]] by putting the following lines in it:
 
−
 
 
−
AUTOPICKUP_EXCEPTION=">chest"
 
−
 
 
−
This will make the hero never pick up all items that match the string "chest".
 
  
−
AUTOPICKUP_EXCEPTION="<dagger"
+
==Syntax==
 +
An autopickup exception rule is expressed as either a <tt><</tt> or a <tt>></tt>, followed by a [[wikipedia:Regular expression|regular expression]]. The leading character determines whether items whose names match the regular expression are picked up: a <tt><</tt> rule flags the matched item for pickup, while a <tt>></tt> rule ignores the matched item.
  
−
This will make the hero always pick up all items that match the string "dagger".
+
The regular expression is matched against the singular form of the name of the item, plus any preceding article or number: "a gold piece" matches a single gold piece, "2 gold piece" matches a stack of 2 gold pieces, but "2 gold pieces" would match nothing.{{reffunc|objnam.c|makesingular}} Any "called ..." or "named ..." suffixes added with the [[Name|#name]] command ''are'' included, so take note of your own naming habits and write your autopickup exceptions accordingly.
  
−
If the first character inside the quoted string is a greater-than sign (<tt>&gt;</tt>), then the matched items will be not be picked up; if it's a less-than sign (<tt>&lt;</tt>), the items will be picked up. The rest of the string defines what items will match for that rule. The string matching allows for basic wildcards, where period plus asterisk (<tt>.*</tt>) matches any number of characters and question mark (<tt>?</tt>) matches any one character.  A "never pickup" rule takes precedence over an "always pickup" rule if both match an item. If no rule matches, autopickup defaults to pickup_types.
+
As of version [[3.6.4]], autopickup exceptions override one another sequentially the same way [[menucolors]] and [[MSGTYPE]]s do, with rules specified later in the config file taking precedence over those specified earlier, and rules specified during play via the {{kbd|O}} command taking precedence over everything. Order is all that matters; neither <tt><</tt> nor <tt>></tt> takes precedence over the other. [[Pickup_types]] is consulted if and only if no matching rule is found.  
  
−
NetHack attempts to convert the object names and called-classnames to singular form before matching them against your exceptions. This usually makes writing exceptions easier; however, when you use #name to give an object a called-classname, like "a gem called worthless", NetHack will mangle the called-classname as well, possibly making it harder to match against. In particular, it will attempt to make the word "worthless" singular by removing an "s", but only if the word comes at the end of the name. Thus, to drop all worthless glass, (whether formally or informally IDed) you should say ">*worthless?", not ">*worthless".{{reffunc|pickup.c|is_autopickup_exception}}
+
In the [[configuration file]], exceptions are specified by the string <tt>AUTOPICKUP_EXCEPTION=</tt> followed by the rule enclosed in double quotes. When adding an exception via the {{kbd|O}} command, you're just prompted for the rule without quotes.
  
−
==How to use it effectively==
+
==Strategy==
 
Autopickup exceptions can greatly simplify dungeon exploration. You can use them to keep dangerous items out of monsters' hands, to conveniently sort through large piles of loot, to automate things you might forget, to save a turn when fleeing or on [[speed run]]s, to remove good morphs from your [[polypiling]] line without paying attention, etc.
 
Autopickup exceptions can greatly simplify dungeon exploration. You can use them to keep dangerous items out of monsters' hands, to conveniently sort through large piles of loot, to automate things you might forget, to save a turn when fleeing or on [[speed run]]s, to remove good morphs from your [[polypiling]] line without paying attention, etc.
  
 
Some items, such as [[gold]], are useful only in the early game. You can add and remove rules in-game with the {{kbd|O}} command, though the settings will revert the next time you run the program. If your needs change much over the course of a long game, the easiest way to update the exceptions is to comment or uncomment the lines in your [[nethackrc]], [[save]] the game, and restore. You can also use [[pickup_types]] as an in-game switch to distinguish between early-game and late-game configurations by simply not mentioning items you want to default to [[pickup_types]].
 
Some items, such as [[gold]], are useful only in the early game. You can add and remove rules in-game with the {{kbd|O}} command, though the settings will revert the next time you run the program. If your needs change much over the course of a long game, the easiest way to update the exceptions is to comment or uncomment the lines in your [[nethackrc]], [[save]] the game, and restore. You can also use [[pickup_types]] as an in-game switch to distinguish between early-game and late-game configurations by simply not mentioning items you want to default to [[pickup_types]].
  
−
The regular expression in the rule is matched against the singular form of the name of the item, plus any preceding article or number: "a gold piece" matches a single gold piece, "2 gold piece" matches a stack of 2 gold pieces, but "2 gold pieces" would match nothing.{{reffunc|objnam.c|makesingular}} Any "called ..." or "named ..." suffixes added with the [[Name|#name]] command ''are'' included, so take note of your own naming habits and write your autopickup exceptions accordingly.
+
===Suggested rules===
−
 
+
First, it's necessary to turn on autopickup, and set some pickup_types that will act as a catch-all assuming none of our autopickup exception rules match. Highly recommended — but not necessary — is adapting [[pickup_burden]].
−
As of version [[3.6.4]], autopickup exceptions override one another sequentially the same way menucolors and msgtypes do, with rules specified further down in the config file taking precedence over those specified earlier, and rules specified during play via the {{kbd|O}} command taking precedence over everything.
+
OPTIONS=autopickup
−
 
+
OPTIONS=pickup_types:$?!/(
−
===Easy ones===
+
OPTIONS=pickup_burden:unencumbered
−
Individually-name the real Amulet right away and you'll never fall for a fake:
 
  
 +
Individually #[[name]] the real [[Amulet of Yendor]] right away and you'll never fall for a [[Cheap plastic imitation of the Amulet of Yendor|fake]]:
 
  AUTOPICKUP_EXCEPTION=">Amulet of Yendor"
 
  AUTOPICKUP_EXCEPTION=">Amulet of Yendor"
 
  AUTOPICKUP_EXCEPTION="<Amulet of Yendor named"
 
  AUTOPICKUP_EXCEPTION="<Amulet of Yendor named"
  
−
Avoid turning your scrolls of scare monster to dust:
+
Avoid turning your [[Scroll of scare monster|scrolls of scare monster]] to dust:
 
  AUTOPICKUP_EXCEPTION=">scroll .* scare monster"
 
  AUTOPICKUP_EXCEPTION=">scroll .* scare monster"
  
 
Walk in peace over empty wands and [[wand of nothing|wands of nothing]]:
 
Walk in peace over empty wands and [[wand of nothing|wands of nothing]]:
−
  AUTOPICKUP_EXCEPTION=":0¥)"
+
  AUTOPICKUP_EXCEPTION=">:0)"
 
  AUTOPICKUP_EXCEPTION="> named empty"
 
  AUTOPICKUP_EXCEPTION="> named empty"
 
  AUTOPICKUP_EXCEPTION="> nothing"
 
  AUTOPICKUP_EXCEPTION="> nothing"
  
−
Good [[monster starting inventory|items left after a fight]] that careful weight watching:
+
Good [[monster starting inventory|items left after a fight]], but requires careful weight watching:
 
  # AUTOPICKUP_EXCEPTION="<potion .* healing"
 
  # AUTOPICKUP_EXCEPTION="<potion .* healing"
 
  # AUTOPICKUP_EXCEPTION="<potion .* gain level"
 
  # AUTOPICKUP_EXCEPTION="<potion .* gain level"
  
 
Pick up formally [[identified]] artifacts. Don't blast yourself to death with a cross-aligned one — leave unidentified ones on the floor:
 
Pick up formally [[identified]] artifacts. Don't blast yourself to death with a cross-aligned one — leave unidentified ones on the floor:
−
  AUTOPICKUP_EXCEPTION="<[^| ]the "
+
  AUTOPICKUP_EXCEPTION="<^the "
  
 
Some people also want known-blessed items, though this likely picks up too much:
 
Some people also want known-blessed items, though this likely picks up too much:
−
  #  AUTOPICKUP_EXCEPTION="<blessed"
+
  #  AUTOPICKUP_EXCEPTION="< blessed "
  
 
===Corpses===
 
===Corpses===
−
The [[comestible]] item class includes [[food]], which you may well want to autopickup, but also [[corpses]], which are prohibitively heavy, usually worthless, and in the case of [[chickatrice]] and [[cockatrice]] corpses, extremely dangerous. The solution to this is to include {{white|%}} in your pickup_types and then add the following exception:
+
The [[comestible]] item class includes [[food]], which you may well want to autopickup, but also includes [[corpses]], most of which are not worth carrying around - some corpses are also prohibitively heavy and, in the case of [[cockatrice]] and [[chickatrice]] corpses, extremely dangerous. If you want to pick up food, but not corpses, include <tt>%</tt> in your pickup_types and then add the following exception:
 
  AUTOPICKUP_EXCEPTION="> corpse"
 
  AUTOPICKUP_EXCEPTION="> corpse"
  
−
Some corpses you actually might want to pick up include [[lichen]] and [[lizard]]s, which do not decay and the latter of which is invaluable in [[stoning|certain emergencies]], and [[newts]], [[floating eyes]], and [[wraiths]], which are lightweight and have beneficial effects when eaten:
+
Corpses you ''will'' want to pick up include [[lichen]] and [[lizard]]s, which do not decay and the latter of which is invaluable in [[stoning|certain emergencies]].  You may also want to grab [[newt]]s, [[floating eye]]s, and [[wraith]]s, which are lightweight and have beneficial effects when eaten. If you want to pick up these, add the following lines beneath the corpse rule:
 
  AUTOPICKUP_EXCEPTION="<lichen corpse"  
 
  AUTOPICKUP_EXCEPTION="<lichen corpse"  
 
  AUTOPICKUP_EXCEPTION="<lizard corpse"  
 
  AUTOPICKUP_EXCEPTION="<lizard corpse"  
 
  AUTOPICKUP_EXCEPTION="<newt corpse"
 
  AUTOPICKUP_EXCEPTION="<newt corpse"
 
  AUTOPICKUP_EXCEPTION="<floating eye corpse"
 
  AUTOPICKUP_EXCEPTION="<floating eye corpse"
−
  AUTOPICKUP_EXCEPTION="<wraith corpse"  
+
  AUTOPICKUP_EXCEPTION="<wraith corpse"
 +
 
 +
===Things too good to miss===
 +
Wands of wishing, magic lamps, magic markers, and wands of lasting [[Elbereth]] are useful even in the endgame, when you likely have enough other things on your mind. You don't want monsters zapping create monster or shooting death rays at you.
 +
 
 +
AUTOPICKUP_EXCEPTION="<wand .* wish"
 +
AUTOPICKUP_EXCEPTION="<wand .* create monster"
 +
AUTOPICKUP_EXCEPTION="<wand .* tele"
 +
#AUTOPICKUP_EXCEPTION="<wand .* poly"
 +
 +
AUTOPICKUP_EXCEPTION="<wand .* fire"
 +
AUTOPICKUP_EXCEPTION="<wand .* lightning"
 +
AUTOPICKUP_EXCEPTION="<wand .* death"
 +
#AUTOPICKUP_EXCEPTION=">wand .* cold$" # For Juiblex's swamp
 +
 +
AUTOPICKUP_EXCEPTION="<magic marker"
 +
AUTOPICKUP_EXCEPTION="< lamp"
 +
AUTOPICKUP_EXCEPTION="> oil lamp"
 +
AUTOPICKUP_EXCEPTION="> lamp .* oil"
 +
AUTOPICKUP_EXCEPTION="<amulet .* life"
 +
AUTOPICKUP_EXCEPTION="<athame"
  
 
===Define pickup / drop in-game===
 
===Define pickup / drop in-game===
Line 78: Line 89:
 
Usually, you need only one of each type of magical armor / ring / amulet / spellbook / magical tool. Wouldn't it be nice if the game managed that for you? It can if you're willing to class-name all objects immediately.
 
Usually, you need only one of each type of magical armor / ring / amulet / spellbook / magical tool. Wouldn't it be nice if the game managed that for you? It can if you're willing to class-name all objects immediately.
  
−
Below are the rules for armor. You could call the mine town watchmens' helmets "plain", turning it from its name from its unidentified description to "a helmet called plain" and removing it from the pickup list. See [[User:Tjr|Tjr]]'s [http://alt.org/nethack/userdata/tjr2/tjr2.nh343rc config] for other item types, although it needs to be updated for Nethack 3.6 regex format.
+
Below are the rules for armor. You could call the Minetown watchmen's helmets "plain", turning it from its name from its unidentified description to "a helmet called plain" and removing it from the pickup list. See [[User:Tjr|Tjr]]'s [http://alt.org/nethack/userdata/tjr2/tjr2.nh343rc config] for other item types, although it needs to be updated for NetHack 3.6 regex format.
  
 
  # AUTOPICKUP_EXCEPTION="<robe"
 
  # AUTOPICKUP_EXCEPTION="<robe"
Line 84: Line 95:
 
  # AUTOPICKUP_EXCEPTION="<apron"
 
  # AUTOPICKUP_EXCEPTION="<apron"
 
  # AUTOPICKUP_EXCEPTION="<polished silver shield"
 
  # AUTOPICKUP_EXCEPTION="<polished silver shield"
−
  # AUTOPICKUP_EXCEPTION="<smooth shield"
+
  # AUTOPICKUP_EXCEPTION="<smooth shield" # blind description
−
# #     when blind       ^^^^^^
+
−
 
 
 
  AUTOPICKUP_EXCEPTION=">helmet"
 
  AUTOPICKUP_EXCEPTION=">helmet"
 
  AUTOPICKUP_EXCEPTION="<conical hat"
 
  AUTOPICKUP_EXCEPTION="<conical hat"
Line 93: Line 103:
 
  AUTOPICKUP_EXCEPTION="<crested helmet"
 
  AUTOPICKUP_EXCEPTION="<crested helmet"
 
  AUTOPICKUP_EXCEPTION="<visored helmet"
 
  AUTOPICKUP_EXCEPTION="<visored helmet"
−
 
+
 
  AUTOPICKUP_EXCEPTION=">cloak"
 
  AUTOPICKUP_EXCEPTION=">cloak"
 
  AUTOPICKUP_EXCEPTION="<tattered cape"
 
  AUTOPICKUP_EXCEPTION="<tattered cape"
Line 99: Line 109:
 
  AUTOPICKUP_EXCEPTION="<ornamental cope"
 
  AUTOPICKUP_EXCEPTION="<ornamental cope"
 
  AUTOPICKUP_EXCEPTION="<piece of cloth"
 
  AUTOPICKUP_EXCEPTION="<piece of cloth"
−
 
+
 
  AUTOPICKUP_EXCEPTION=">gloves"
 
  AUTOPICKUP_EXCEPTION=">gloves"
 
  AUTOPICKUP_EXCEPTION="<old gloves"
 
  AUTOPICKUP_EXCEPTION="<old gloves"
Line 105: Line 115:
 
  AUTOPICKUP_EXCEPTION="<riding gloves"
 
  AUTOPICKUP_EXCEPTION="<riding gloves"
 
  AUTOPICKUP_EXCEPTION="<fencing gloves"
 
  AUTOPICKUP_EXCEPTION="<fencing gloves"
−
 
+
 
  AUTOPICKUP_EXCEPTION=">boots"
 
  AUTOPICKUP_EXCEPTION=">boots"
 
  AUTOPICKUP_EXCEPTION="<combat boots"
 
  AUTOPICKUP_EXCEPTION="<combat boots"
Line 116: Line 126:
  
 
===Keeping ammunition out of monsters' hands===
 
===Keeping ammunition out of monsters' hands===
−
Especially in the Mines, you want to collect lightweight but dangerous projectiles and deposit them in a safe location &endash; on a square with a [[scroll of scare monster is good]], as is the downstair on a previously cleared level. This keeps monsters from reusing them against you over and over. (Deactivate daggers if you don't fire them yourself — they're heavy.)
+
Especially in the Mines, you will want to collect lightweight but dangerous projectiles and deposit them in a safe location &endash; on a square with a [[scroll of scare monster]], the downstair on a previously cleared level, or underneath a [[boulder]]. This keeps monsters from reusing them against you. (Deactivate daggers if you don't throw them yourself — they're heavy.)
  
 
  AUTOPICKUP_EXCEPTION="< arrow"
 
  AUTOPICKUP_EXCEPTION="< arrow"
Line 125: Line 135:
 
  ## AUTOPICKUP_EXCEPTION="<crude arrow"
 
  ## AUTOPICKUP_EXCEPTION="<crude arrow"
 
  AUTOPICKUP_EXCEPTION="< ya"
 
  AUTOPICKUP_EXCEPTION="< ya"
 +
 
  ## AUTOPICKUP_EXCEPTION="<bamboo arrow"
 
  ## AUTOPICKUP_EXCEPTION="<bamboo arrow"
 
  AUTOPICKUP_EXCEPTION="<crossbow bolt"
 
  AUTOPICKUP_EXCEPTION="<crossbow bolt"
Line 130: Line 141:
 
  AUTOPICKUP_EXCEPTION="<shuriken"
 
  AUTOPICKUP_EXCEPTION="<shuriken"
 
  AUTOPICKUP_EXCEPTION="<throwing star"
 
  AUTOPICKUP_EXCEPTION="<throwing star"
 +
 
  AUTOPICKUP_EXCEPTION="<dagger"
 
  AUTOPICKUP_EXCEPTION="<dagger"
 
  ## AUTOPICKUP_EXCEPTION="<elven dagger"
 
  ## AUTOPICKUP_EXCEPTION="<elven dagger"
Line 138: Line 150:
 
  AUTOPICKUP_EXCEPTION="<knife"
 
  AUTOPICKUP_EXCEPTION="<knife"
  
−
===Things too good to miss===
 
−
Wands of wishing, magic lamps, magic markers, and wands of lasting [[Elbereth]] are useful even in the endgame, when you likely have enough other things on your mind. You don't want monsters zapping create monster or shooting death rays at you.
 
−
 
−
AUTOPICKUP_EXCEPTION="<wand .* wish"
 
−
AUTOPICKUP_EXCEPTION="<wand .* create monster"
 
−
AUTOPICKUP_EXCEPTION="<wand .* tele"
 
−
#AUTOPICKUP_EXCEPTION="<wand .* poly"
 
−
 
−
AUTOPICKUP_EXCEPTION="<wand .* fire"
 
−
AUTOPICKUP_EXCEPTION="<wand .* lightning"
 
−
AUTOPICKUP_EXCEPTION="<wand .* death"
 
−
#AUTOPICKUP_EXCEPTION=">wand .* cold$" # For Juiblex's swamp
 
−
 
−
AUTOPICKUP_EXCEPTION="<magic marker"
 
−
AUTOPICKUP_EXCEPTION="< lamp"
 
−
AUTOPICKUP_EXCEPTION="> oil lamp"
 
−
AUTOPICKUP_EXCEPTION="> lamp .* oil"
 
−
AUTOPICKUP_EXCEPTION="<amulet .* life"
 
−
AUTOPICKUP_EXCEPTION="<athame"
 
  
 
===Avoiding loadstones===
 
===Avoiding loadstones===
−
With this rule, you should never pick up a loadstone, regardless of your [[blind]]ness or knowledge of loadstones:
+
With these rules, you should never pick up a loadstone, regardless of your knowledge of loadstones:
 
  AUTOPICKUP_EXCEPTION="> loadstone"
 
  AUTOPICKUP_EXCEPTION="> loadstone"
 
  AUTOPICKUP_EXCEPTION="<stone called luck"
 
  AUTOPICKUP_EXCEPTION="<stone called luck"
Line 166: Line 159:
 
  AUTOPICKUP_EXCEPTION="> rock"
 
  AUTOPICKUP_EXCEPTION="> rock"
 
  AUTOPICKUP_EXCEPTION="> gray stone"
 
  AUTOPICKUP_EXCEPTION="> gray stone"
−
+
 
−
When blind, [[gems]] and [[worthless glass]] are called "gems", and all other {{white|*}} are called "stones".
+
When blind, [[gems]] and [[worthless glass]] are called "gems", and all other {{white|*}} are called "stones", so with the following rule, you won't risk picking up loadstones while blind, either:
 
  AUTOPICKUP_EXCEPTION=">^[a0-9]+ stone"
 
  AUTOPICKUP_EXCEPTION=">^[a0-9]+ stone"
  
−
The leading "^[a0-9]+" ensures that gems with "stone" in their identified name (amber stones, turquoise stones, etc.) are not matched.
+
The leading <tt>^[a0-9]+</tt> ensures that valuable gems with "stone" in their identified name (amber stones, turquoise stones, etc.) are not matched.
  
 
===Only exceptions pick stuff up===
 
===Only exceptions pick stuff up===
Line 188: Line 181:
 
{{featured}}
 
{{featured}}
 
[[Category:Options]]
 
[[Category:Options]]
−
{{nethack-360|offset=1}}
+
{{nethack-366|offset=1}}

Latest revision as of 15:34, 13 July 2023

AUTOPICKUP_EXCEPTION is a configuration option that allows you to define what items are automatically picked up, based on the name of the item. This gives more precision on top of pickup_types. You need to have autopickup on for autopickup exceptions to be active.

In NetHack 3.6 autopickup exceptions are compiled in by default. The NAO version of NetHack 3.4.3 has them as well.

Syntax

An autopickup exception rule is expressed as either a < or a >, followed by a regular expression. The leading character determines whether items whose names match the regular expression are picked up: a < rule flags the matched item for pickup, while a > rule ignores the matched item.

The regular expression is matched against the singular form of the name of the item, plus any preceding article or number: "a gold piece" matches a single gold piece, "2 gold piece" matches a stack of 2 gold pieces, but "2 gold pieces" would match nothing.[1] Any "called ..." or "named ..." suffixes added with the #name command are included, so take note of your own naming habits and write your autopickup exceptions accordingly.

As of version 3.6.4, autopickup exceptions override one another sequentially the same way menucolors and MSGTYPEs do, with rules specified later in the config file taking precedence over those specified earlier, and rules specified during play via the O command taking precedence over everything. Order is all that matters; neither < nor > takes precedence over the other. Pickup_types is consulted if and only if no matching rule is found.

In the configuration file, exceptions are specified by the string AUTOPICKUP_EXCEPTION= followed by the rule enclosed in double quotes. When adding an exception via the O command, you're just prompted for the rule without quotes.

Strategy

Autopickup exceptions can greatly simplify dungeon exploration. You can use them to keep dangerous items out of monsters' hands, to conveniently sort through large piles of loot, to automate things you might forget, to save a turn when fleeing or on speed runs, to remove good morphs from your polypiling line without paying attention, etc.

Some items, such as gold, are useful only in the early game. You can add and remove rules in-game with the O command, though the settings will revert the next time you run the program. If your needs change much over the course of a long game, the easiest way to update the exceptions is to comment or uncomment the lines in your nethackrc, save the game, and restore. You can also use pickup_types as an in-game switch to distinguish between early-game and late-game configurations by simply not mentioning items you want to default to pickup_types.

Suggested rules

First, it's necessary to turn on autopickup, and set some pickup_types that will act as a catch-all assuming none of our autopickup exception rules match. Highly recommended — but not necessary — is adapting pickup_burden. 

OPTIONS=autopickup
OPTIONS=pickup_types:$?!/(
OPTIONS=pickup_burden:unencumbered

Individually #name the real Amulet of Yendor right away and you'll never fall for a fake: 

AUTOPICKUP_EXCEPTION=">Amulet of Yendor"
AUTOPICKUP_EXCEPTION="<Amulet of Yendor named"

Avoid turning your scrolls of scare monster to dust: 

AUTOPICKUP_EXCEPTION=">scroll .* scare monster"

Walk in peace over empty wands and wands of nothing: 

AUTOPICKUP_EXCEPTION=">:0)"
AUTOPICKUP_EXCEPTION="> named empty"
AUTOPICKUP_EXCEPTION="> nothing"

Good items left after a fight, but requires careful weight watching: 

# AUTOPICKUP_EXCEPTION="<potion .* healing"
# AUTOPICKUP_EXCEPTION="<potion .* gain level"

Pick up formally identified artifacts. Don't blast yourself to death with a cross-aligned one — leave unidentified ones on the floor: 

AUTOPICKUP_EXCEPTION="<^the "

Some people also want known-blessed items, though this likely picks up too much: 

#  AUTOPICKUP_EXCEPTION="< blessed "

Corpses

The comestible item class includes food, which you may well want to autopickup, but also includes corpses, most of which are not worth carrying around - some corpses are also prohibitively heavy and, in the case of cockatrice and chickatrice corpses, extremely dangerous. If you want to pick up food, but not corpses, include % in your pickup_types and then add the following exception: 

AUTOPICKUP_EXCEPTION="> corpse"

Corpses you will want to pick up include lichen and lizards, which do not decay and the latter of which is invaluable in certain emergencies. You may also want to grab newts, floating eyes, and wraiths, which are lightweight and have beneficial effects when eaten. If you want to pick up these, add the following lines beneath the corpse rule: 

AUTOPICKUP_EXCEPTION="<lichen corpse" 
AUTOPICKUP_EXCEPTION="<lizard corpse" 
AUTOPICKUP_EXCEPTION="<newt corpse"
AUTOPICKUP_EXCEPTION="<floating eye corpse"
AUTOPICKUP_EXCEPTION="<wraith corpse"

Things too good to miss

Wands of wishing, magic lamps, magic markers, and wands of lasting Elbereth are useful even in the endgame, when you likely have enough other things on your mind. You don't want monsters zapping create monster or shooting death rays at you. 

AUTOPICKUP_EXCEPTION="<wand .* wish"
AUTOPICKUP_EXCEPTION="<wand .* create monster"
AUTOPICKUP_EXCEPTION="<wand .* tele"
#AUTOPICKUP_EXCEPTION="<wand .* poly"

AUTOPICKUP_EXCEPTION="<wand .* fire"
AUTOPICKUP_EXCEPTION="<wand .* lightning"
AUTOPICKUP_EXCEPTION="<wand .* death"
#AUTOPICKUP_EXCEPTION=">wand .* cold$" # For Juiblex's swamp

AUTOPICKUP_EXCEPTION="<magic marker"
AUTOPICKUP_EXCEPTION="< lamp"
AUTOPICKUP_EXCEPTION="> oil lamp"
AUTOPICKUP_EXCEPTION="> lamp .* oil"
AUTOPICKUP_EXCEPTION="<amulet .* life"
AUTOPICKUP_EXCEPTION="<athame"

Define pickup / drop in-game

The following rules let you manually override autopickup exceptions without changing the rules at all by #naming items with strings containing "<" or ">": 

AUTOPICKUP_EXCEPTION="<<"
AUTOPICKUP_EXCEPTION=">>"

Because rules defined later take precedence over ones defined earlier, if you want these manual overrides to take effect unconditionally, you have to put them at the end of the file. If you want to be able to name a class of unidentified items with ">" to leave them alone and then individually-name one of those items with "<" to pick it up, add the following rules below that: 

autopickup_exception="< named .*<"
autopickup_exception="> named .*>"

One of each kind of magical object

Usually, you need only one of each type of magical armor / ring / amulet / spellbook / magical tool. Wouldn't it be nice if the game managed that for you? It can if you're willing to class-name all objects immediately.

Below are the rules for armor. You could call the Minetown watchmen's helmets "plain", turning it from its name from its unidentified description to "a helmet called plain" and removing it from the pickup list. See Tjr's config for other item types, although it needs to be updated for NetHack 3.6 regex format. 

# AUTOPICKUP_EXCEPTION="<robe"
# AUTOPICKUP_EXCEPTION="<faded pall"
# AUTOPICKUP_EXCEPTION="<apron"
# AUTOPICKUP_EXCEPTION="<polished silver shield"
# AUTOPICKUP_EXCEPTION="<smooth shield" # blind description

AUTOPICKUP_EXCEPTION=">helmet"
AUTOPICKUP_EXCEPTION="<conical hat"
AUTOPICKUP_EXCEPTION="<plumed helmet"
AUTOPICKUP_EXCEPTION="<etched helmet"
AUTOPICKUP_EXCEPTION="<crested helmet"
AUTOPICKUP_EXCEPTION="<visored helmet"

AUTOPICKUP_EXCEPTION=">cloak"
AUTOPICKUP_EXCEPTION="<tattered cape"
AUTOPICKUP_EXCEPTION="<opera cloak"
AUTOPICKUP_EXCEPTION="<ornamental cope"
AUTOPICKUP_EXCEPTION="<piece of cloth"

AUTOPICKUP_EXCEPTION=">gloves"
AUTOPICKUP_EXCEPTION="<old gloves"
AUTOPICKUP_EXCEPTION="<padded gloves"
AUTOPICKUP_EXCEPTION="<riding gloves"
AUTOPICKUP_EXCEPTION="<fencing gloves"

AUTOPICKUP_EXCEPTION=">boots"
AUTOPICKUP_EXCEPTION="<combat boots"
AUTOPICKUP_EXCEPTION="<jungle boots"
AUTOPICKUP_EXCEPTION="<hiking boots"
AUTOPICKUP_EXCEPTION="<mud boots"
AUTOPICKUP_EXCEPTION="<buckled boots"
AUTOPICKUP_EXCEPTION="<riding boots"
AUTOPICKUP_EXCEPTION="<snow boots"

Keeping ammunition out of monsters' hands

Especially in the Mines, you will want to collect lightweight but dangerous projectiles and deposit them in a safe location &endash; on a square with a scroll of scare monster, the downstair on a previously cleared level, or underneath a boulder. This keeps monsters from reusing them against you. (Deactivate daggers if you don't throw them yourself — they're heavy.) 

AUTOPICKUP_EXCEPTION="< arrow"
## AUTOPICKUP_EXCEPTION="<elven arrow"
## AUTOPICKUP_EXCEPTION="<orcish arrow"
## AUTOPICKUP_EXCEPTION="<silver arrow"
## AUTOPICKUP_EXCEPTION="<runed arrow"
## AUTOPICKUP_EXCEPTION="<crude arrow"
AUTOPICKUP_EXCEPTION="< ya"

## AUTOPICKUP_EXCEPTION="<bamboo arrow"
AUTOPICKUP_EXCEPTION="<crossbow bolt"
AUTOPICKUP_EXCEPTION="<dart"
AUTOPICKUP_EXCEPTION="<shuriken"
AUTOPICKUP_EXCEPTION="<throwing star"

AUTOPICKUP_EXCEPTION="<dagger"
## AUTOPICKUP_EXCEPTION="<elven dagger"
## AUTOPICKUP_EXCEPTION="<orcish dagger"
## AUTOPICKUP_EXCEPTION="<runed dagger"
## AUTOPICKUP_EXCEPTION="<crude dagger"
## AUTOPICKUP_EXCEPTION="<silver dagger"
AUTOPICKUP_EXCEPTION="<knife"


Avoiding loadstones

With these rules, you should never pick up a loadstone, regardless of your knowledge of loadstones: 

AUTOPICKUP_EXCEPTION="> loadstone"
AUTOPICKUP_EXCEPTION="<stone called luck"
AUTOPICKUP_EXCEPTION="< luckstone"
#AUTOPICKUP_EXCEPTION="< touchstone"
AUTOPICKUP_EXCEPTION="> rock"
AUTOPICKUP_EXCEPTION="> gray stone"

When blind, gems and worthless glass are called "gems", and all other * are called "stones", so with the following rule, you won't risk picking up loadstones while blind, either: 

AUTOPICKUP_EXCEPTION=">^[a0-9]+ stone"

The leading ^[a0-9]+ ensures that valuable gems with "stone" in their identified name (amber stones, turquoise stones, etc.) are not matched.

Only exceptions pick stuff up

If you want only the exceptions to pick anything up, put this rule at the beginning of your file: 

AUTOPICKUP_EXCEPTION=">.*"

This excludes everything, so that you can turn on autopickup, but not actually autopickup anything unless you say so with an exception.

References

  1. ↑ makesingular in objnam.c

External references

Retrieved from "https://nethackwiki.com/index.php?title=Autopickup_exception&oldid=152281"