Name - Revision history

Umbire the Phantom: /* #naming a class of items /

2022-12-04T07:27:04Z

‎#naming a class of items: *

Actual-nh: Grammar/style

2021-02-28T00:51:06Z

Grammar/style

Actual-nh: Grammar/style

2021-02-28T00:50:36Z

Grammar/style

Ardub23: I think there's enough info on the page that it's a stretch to call it a stub

2019-09-12T02:28:13Z

I think there's enough info on the page that it's a stretch to call it a stub

ChasonBot at 08:36, 20 December 2015

2015-12-20T08:36:45Z

Elronnd: /* #naming individual items */: Notes on naming to not intrinsics

2015-05-09T18:33:55Z

‎#naming individual items: : Notes on naming to not intrinsics

SophiaMakoto: The message associated with failing to name an object under circumstances has been added, as well as a redirecting page from the message to here.

2013-11-14T07:40:28Z

The message associated with failing to name an object under circumstances has been added, as well as a redirecting page from the message to here.

Bulwersator: /* SLASH'EM */ -|This seems to be missing some stuff, but what? (useless comment)

2013-05-04T15:15:47Z

‎SLASH'EM: -|This seems to be missing some stuff, but what? (useless comment)

Bcode: Template usage; usage notes; minor fixes

2013-05-01T11:49:07Z

Template usage; usage notes; minor fixes

Tjr: autopickup exceptions

2013-04-06T11:10:14Z

autopickup exceptions

@@ Line 27: / Line 27: @@
 As with naming individual items, there are multiple reasons to name an entire object class:
 * Keep track of the possibilities for items you find after applying various object identification tests, such as [[Wand#Engrave-identification|engrave testing]].
-* Prior to [[NetHack 3.6.0]], naming a scroll or spellbook will let you [[Magic marker#Unknown scrolls and spellbooks|write items of that type as though it were identified]]. Obviously you also have to actually know what that type is, or have named all scrolls or books in that price group so it can be written successfully no matter which of those it happens to be.
+* Prior to [[NetHack 3.6.0]], naming a scroll or spellbook will let you [[Magic marker#Unknown scrolls and spellbooks|write items of that type with a magic marker as though it were identified]]. Obviously you also have to actually know what that type is, or have named all scrolls or books in that price group so it can be written successfully no matter which of those it happens to be.
 * [[Unicorn#Unicorns and gems|Throwing class-named gems to a unicorn]] gives a larger Luck bonus than unnamed gems.
 * Some classes of items can not be named in this way, notably [[weapon]]s and [[comestible]]s.

@@ Line 5: / Line 5: @@
 Naming items in NetHack can be very helpful for keeping track of items. You can name a class of objects after informally identifying something, or keep reminders so as to not put on that [[BUC|cursed]] [[amulet of strangulation]].
-In some cases, you cannot name the class of things such as artifacts, bags, or gems while blind (''You would never recognize another one.'')
+In some cases, you cannot name the class of things such as artifacts, bags, or gems while blind (''You would never recognize another one'').
 == #naming individual items ==

@@ Line 1: / Line 1: @@
 {{for|naming monsters|call}}
-'''#name''' is an [[extended command]] which is mapped to {{kbd|N}} (capital N) by default, if you are using [[number pad]]. (On [[nethack.alt.org]] and in [[AceHack]], it is mapped to {{kbd|C}} by default.) You can do two things with #name:
+'''#name''' is an [[extended command]], mapped to {{kbd|N}} (capital N) by default if you are using the [[number pad]] option. (On [[nethack.alt.org]] and in [[AceHack]], it is mapped to {{kbd|C}} by default.) You can do two things with #name:
 * Name an individual item
 * Call a ''class'' of items (that is, all the items of that type, such as all steel wands)

@@ Line 3: / Line 3: @@
 * Name an individual item
 * Call a ''class'' of items (that is, all the items of that type, such as all steel wands)
-Naming items in NetHack can be very helpful for keeping track of items. You can name a class of objects after informally identifying something, or keep reminders so as to not put on that [[BUC|cursed]] [[Amulet of strangulation]].
+Naming items in NetHack can be very helpful for keeping track of items. You can name a class of objects after informally identifying something, or keep reminders so as to not put on that [[BUC|cursed]] [[amulet of strangulation]].
-Do note that in some cases you cannot name things such as artifacts, bags, or while blind (''You would never recognize another one.'')
 == #naming individual items ==
 These are a few reasons to rename an individual item with #name, with an example for each:
 * Roleplay (naming your primary weapon "Stinging Blow" because of the amount of damage you can do with it)
-* Reminders (naming an item you suspect is cursed, etc.)
+* Reminders (naming an item you suspect is cursed)
 * Certain [[artifact]]s can be generated by naming a weapon of their base class ([[Sting]], [[Orcrist]])
-* To keep items from stacking in your inventory, you can name stacks of them differently. This is useful when using confused blessed [[scroll of remove curse|scrolls of remove curse]] to generate [[holy water]] and [[unholy water]]
+* To keep items from stacking in your inventory, you can name stacks of them differently. This is useful when using confused blessed [[scroll of remove curse|scrolls of remove curse]] to generate {{of|potion|holy water|and=1|unholy water}}.
-* Names of important items are often used to keep notes on games, especially in games played by multiple people (see [[robin]])
+* Names of important items are often used to keep notes on games, especially in games played by multiple people (see [[Robin]])
 * Naming the [[Amulet of Yendor]] will allow you to identify it from all the fakes if you drop it or it gets stolen
 * Abusing the [[naming artifacts|artifact naming bug]] will allow you to identify some specific items
 * Individual names will not be [[amnesia|forgotten]]
 * [[Autopickup exception]]s can match on individual item name
-* [[Intrinsics]]: naming a an object that you're likely to keep for a while with the names of intrinsics you have.  Example &ldquo;N &mdash; A [[lizard]] corpse named [[Sleep resistance|awake]], [[fire resistance|cold]], [[speed|fast]], [[cold resistance|hot]]&rdquo;
+* [[Intrinsics]]: naming an object that you're likely to keep for a while with the names of intrinsics you have.  Example: "N &ndash; A [[lizard]] corpse named [[Sleep resistance|awake]], [[fire resistance|cold]], [[speed|fast]], [[cold resistance|hot]]"
 == #naming a class of items ==
@@ Line 26: / Line 27: @@
 As with naming individual items, there are multiple reasons to name an entire object class:
 * Keep track of the possibilities for items you find after applying various object identification tests, such as [[Wand#Engrave-identification|engrave testing]].
-* Naming a scroll will let you [[Magic marker#Unknown scrolls and spellbooks|write scrolls of that type as though it were identified]]. Obviously you also have to actually know what that type is, or have named all scrolls in that price group so it can be written successfully no matter which of those it happens to be.
+* Prior to [[NetHack 3.6.0]], naming a scroll or spellbook will let you [[Magic marker#Unknown scrolls and spellbooks|write items of that type as though it were identified]]. Obviously you also have to actually know what that type is, or have named all scrolls or books in that price group so it can be written successfully no matter which of those it happens to be.
-* [[Unicorn#Unicorns and gems|Throwing class-named gems to a unicorn]] gives a luck bonus versus unnamed gems.
+* [[Unicorn#Unicorns and gems|Throwing class-named gems to a unicorn]] gives a larger Luck bonus than unnamed gems.
 * Some classes of items can not be named in this way, notably [[weapon]]s and [[comestible]]s.
-* Seeing the difference between items which look the same, for example to know what [[gray stone]] you just found. If you already called [[touchstone]]s, [[luckstone]]s and [[flintstone]]s, you can avoid [[loadstone]]s easier.
+* Seeing the difference between items which look the same, for example to know what [[gray stone]] you just found. If you already called [[touchstone]]s, [[luckstone]]s and [[flint stone]]s, you can avoid [[loadstone]]s more easily.
-* [[Autopickup exception]]s can match on what an object class is called
+* [[Autopickup exception]]s can match on what an object class is called.
 == Removing a name ==
-To remove the name given to an object or class of objects, enter a name that consists only of spaces. If you simply press enter at the name prompt, you will cancel your naming attempt and the object will keep its previous name.
+To remove the name given to an object or class of objects, enter a name that consists only of spaces. If you press enter at the name prompt without typing anything at all, it is treated as canceling the naming attempt, and the object will keep its previous name.
 == SLASH'EM ==
 In [[SLASH'EM]], in addition to #naming [[Sting]] and [[Orcrist]], you can also give the name "[[Elfrist]]" to an [[orcish spear]].
 [[Category:Extended commands]]
 {{nethack-343}}

← Older revision		Revision as of 08:36, 20 December 2015
Line 41:		Line 41:

	[[Category:Extended commands]]		[[Category:Extended commands]]
		+	{{nethack-343}}

@@ Line 35: / Line 35: @@
 In [[SLASH'EM]], in addition to #naming [[Sting]] and [[Orcrist]], you can also give the name "[[Elfrist]]" to an [[orcish spear]].
-{{stub|This seems to be missing some stuff, but what?}}
+{{stub}}
 [[Category:Extended commands]]

Name - Revision history

Umbire the Phantom: /* #naming a class of items */*

Actual-nh: Grammar/style

Actual-nh: Grammar/style

Ardub23: I think there's enough info on the page that it's a stretch to call it a stub

ChasonBot at 08:36, 20 December 2015

Elronnd: /* #naming individual items */: Notes on naming to not intrinsics

SophiaMakoto: The message associated with failing to name an object under circumstances has been added, as well as a redirecting page from the message to here.

Bulwersator: /* SLASH'EM */ -|This seems to be missing some stuff, but what? (useless comment)

Bcode: Template usage; usage notes; minor fixes

Tjr: autopickup exceptions

Umbire the Phantom: /* #naming a class of items /