Stackable - Revision history

Cathartes: upcoming, stacks of different knowledge status can merge

2023-11-19T06:29:44Z

upcoming, stacks of different knowledge status can merge

Cathartes: /* Strategy */ strategy of keeping deliberately-formally-unknown stacks ... maybe a bit esoteric

2023-03-03T07:00:57Z

‎Strategy: strategy of keeping deliberately-formally-unknown stacks ... maybe a bit esoteric

Actual-nh: Links

2021-02-18T03:52:09Z

Links

Actual-nh: Grammar/style; "close in type" does not make sense

2021-02-18T03:49:25Z

Grammar/style; "close in type" does not make sense

Xyzyxx at 16:43, 4 June 2018

2018-06-04T16:43:07Z

Xyzyxx: Update for 3.6.1

2018-05-03T20:10:16Z

Update for 3.6.1

Cherokee Jack: Crysknives stack in NetHack 3.6.0

2017-04-09T19:06:32Z

Crysknives stack in NetHack 3.6.0

220.255.2.80 at 15:25, 28 October 2011

2011-10-28T15:25:06Z

Dptr1988: /* Splitting stacks */ Split key listing.

2010-12-28T19:27:04Z

‎Splitting stacks: Split key listing.

Tjr: why crysknives don't stack: I guess it's because makesingular() would trip up

2010-07-19T23:13:24Z

why crysknives don't stack: I guess it's because makesingular() would trip up

@@ Line 44: / Line 44: @@
 It is possible to un-know the BUC of already-known objects in some circumstances. [[Praying]] on an altar will cause the potions of water on it to be blessed or cursed, but if you do it ''while [[blind]]'', the BUC status of the water will also become unknown. This will result in a formally unknown (but informally known) stack of holy or unholy water that you can name.  You will then be able to determine the BUC of potions of water you find by seeing whether they merge with your existing stack of holy or unholy water. Additionally, if you dip an item into holy or unholy water whose BUC is not known ''while blind'', and the BUC status of the item changes, that item's BUC status also becomes unknown. Neutralizing a potion with [[unicorn horn]] or [[amethyst]] will result in an uncursed potion of unknown BUC.
-{{upcoming|NetHack 3.7.0|Unseen non-tame monsters picking up items will cause the BUC/enchantment/erosion statuses to become unknown, since {{commit|ad7f2afef9907ef6e52a17dd446b44d1dc774dbe}}. This will cause those items to fail to merge with known stacks, which is especially relevant for stacks of [[projectile]] weapons.}}
+{{upcoming|NetHack 3.7.0|Unseen non-tame monsters picking up items will cause the BUC/enchantment/erosion statuses to become unknown, since {{commit|ad7f2afef9907ef6e52a17dd446b44d1dc774dbe}}.
 {{nethack-366}}
 <references/>
 [[Category:Item attributes]]

@@ Line 40: / Line 40: @@
 Getting potions to stack is of the utmost importance in [[alchemy]]. All alchemy results will be "diluted potion of X", and diluted potions will only stack with other diluted potions. Because of this, later on in the game it can be advantageous to dilute (by dipping once) potions for alchemy, for increased efficiency. Just beware all the risks associated with [[dip]]ping and [[fountain]]s, and take care to have identified [[acid]], as dipping acid will cause an explosion.
-{{nethack-361}}
+Keeping objects' BUC/enchantment/erosion status formally unknown will allow other objects with the same formally unknown status to stack. Thus, it may be advantageous to deliberately keep some stacks of objects unidentified, so that when you encounter more of those in the dungeon, they will still stack.
 <references/>
 [[Category:Item attributes]]

@@ Line 1: / Line 1: @@
 In NetHack, many varieties of items can stack into one inventory slot. This includes:
-* [[gem]]s, glass, rocks, and [[gray stone]]s
+* [[gem]]s, glass, [[rock]]s, and [[gray stone]]s
 * [[potions]]
 * [[scrolls]]
-* [[comestibles]], except for hatchable eggs and revivable corpses
+* [[comestibles]], except for hatchable [[egg]]s and revivable [[corpse]]s
 * [[candle]]s, if of the same type and close in age
 * certain [[ranged weapon]]s:<ref>http://cpansearch.perl.org/src/DOY/NetHack-Item-0.12/lib/NetHack/Item/Spoiler/Weapon.pm</ref>

@@ Line 1: / Line 1: @@
 In NetHack, many varieties of items can stack into one inventory slot. This includes:
-* [[gem]]s, glass, rocks, and gray stones
+* [[gem]]s, glass, rocks, and [[gray stone]]s
 * [[potions]]
 * [[scrolls]]
 * [[comestibles]], except for hatchable eggs and revivable corpses
-* [[candle]]s, if close in age and type
+* [[candle]]s, if of the same type and close in age
 * certain [[ranged weapon]]s:<ref>http://cpansearch.perl.org/src/DOY/NetHack-Item-0.12/lib/NetHack/Item/Spoiler/Weapon.pm</ref>
 :*All [[arrow]]s (orcish, regular, elven, silver, and ya)
@@ Line 14: / Line 14: @@
 :*[[Dart]]s
 :*All [[spear]]s (orcish, normal, elven, dwarven, and silver)
-:*[[Flintstone]]s
+:*[[Flint stone]]s
 :*[[Javelin]]s
 :*[[Knife|Knives]]

@@ Line 28: / Line 28: @@
 The usual way to split a stack is to supply a numeric parameter to the [[adjust]], [[drop]] or [[pick up]] command, or when moving items into or out of a [[container]]. For example, if you have 7 daggers in inventory slot ''a'', you can type {{kbd|d}} {{kbd|4}} {{kbd|a}} to drop 4 of them.
-This method is sufficient if you simply want to split a stack temporarily, as they will quickly merge with each other if you adjust, drop or stash them without a numeric parameter. If you want to carry around multiple stacks of the same type of item and keep them separated, you will need to take additional measures:
+== Strategy ==
-== Strategy ==
+Besides conserving inventory space, getting items to stack is important for efficiency when using [[holy water]] to bless stacks of items, or using a scroll of [[enchant weapon]] to enchant an entire stack of arrows. It can also affect how many projectiles are fired in a single turn; a player can only get off multiple shots in one turn if the projectiles are from the same stack.
-Besides conserving on inventory space, getting items to stack is important for efficiency when using [[holy water]] to bless items, or using a scroll of [[enchant weapon]] to enchant an entire stack of arrows. It can also affect how many projectiles are fired in a single turn; a player can only get off multiple shots in one turn if the projectiles are from the same stack.
+An item being picked up or removed from a container will automatically stack with another item of the same type in your inventory, if it can. If you want to prevent this, you will have to #name the individual items with different names. It is not sufficient to split the stack into two and name one of them - stacks will always take on a name if they do not already have one. This phenomenon can often be observed early on, when one finds an orcish dagger, has the pet BUC test it, and then names it uncursed, only to see other new daggers stack with it.
-There are occasions, however, where one may want to get a stack to split. The way to achieve this is to [[name]] the stacks separately. For example, a starting rogue may desire to both keep one of his starting stack of daggers as a main weapon, and have the rest of the stack serve as projectiles. The way to do this would be to split one dagger from the stack, name it, e.g., "Melee", then name the other stack, e.g., "Throwing". Then, they will stay separated. It is not sufficient to split the stack into two and name one of them - stacks will always take on a name if they do not already have one. This phenomenon can often be observed early on, when one finds an orcish dagger, has the pet BUC test it, and then names it uncursed, only to see other new daggers stack with it.
+As of [[NetHack 3.6.1]], you can wield a stack of throwable weapons (e.g. daggers or spears) and then [[quiver]] them. This will give you the option to leave one weapon wielded and quiver the rest, which will split the stack accordingly.
-Splitting stacks is also useful when someone needs to split up a stack of [[water]] to make an initial [[unholy water]] by reading while [[confused]] a blessed [[scroll of remove curse]]. It may be tedious, but it is probably wise to split up around 10 stacks for this purpose.
+Splitting stacks is useful when someone needs to split up a stack of [[water]] to make an initial [[unholy water]] by reading while [[confused]] a blessed [[scroll of remove curse]]. It may be tedious, but it is probably wise to split up around 10 stacks for this purpose.
 Getting potions to stack is of the utmost importance in [[alchemy]]. All alchemy results will be "diluted potion of X", and diluted potions will only stack with other diluted potions. Because of this, later on in the game it can be advantageous to dilute (by dipping once) potions for alchemy, for increased efficiency. Just beware all the risks associated with [[dip]]ping and [[fountain]]s, and take care to have identified [[acid]], as dipping acid will cause an explosion.

@@ Line 1: / Line 1: @@
 In NetHack, many varieties of items can stack into one inventory slot. This includes:
-* [[gem]]s, glass and stones
+* [[gem]]s, glass, rocks, and gray stones
 * [[potions]]
 * [[scrolls]]
 * [[comestibles]], except for hatchable eggs and revivable corpses
-* [[candle]]s, if close in age
+* [[candle]]s, if close in age and type
 * certain [[ranged weapon]]s:<ref>http://cpansearch.perl.org/src/DOY/NetHack-Item-0.12/lib/NetHack/Item/Spoiler/Weapon.pm</ref>
 :*All [[arrow]]s (orcish, regular, elven, silver, and ya)
@@ Line 17: / Line 17: @@
 :*[[Javelin]]s
 :*[[Knife|Knives]]
-:*[[Worm tooth|Worm teeth]] and [[Crysknife|crysknives]] (in [[NetHack 3.6.0]])
+:*[[Worm tooth|Worm teeth]] and [[Crysknife|crysknives]]
 :*[[Scalpel]]
 :*[[Shuriken]]
 :*[[Stiletto]]
-In order for objects to stack, their [[beatitude]], [[enchantment]], and [[erosion]] status must be exactly the same. Additionally, even a subtle difference in identification status can affect whether or not something stacks. For example, if you have two daggers, and only drop one on an altar and see it was uncursed, those two daggers will no longer stack. Then, if you were to go a step further, and use a [[scroll of identify]] on the dagger you didn't drop, and it was an uncursed +0 dagger, then it would no longer stack with your plain "uncursed dagger".
+In order for objects to stack, their type, [[beatitude]], [[enchantment]], [[erosion]] status, and identification status must all be ''exactly'' the same. For example, if you have two daggers, and only drop one on an altar and see it was uncursed, those two daggers will no longer stack (because one is identified as uncursed, and the other's BUC status is not formally identified). Then, if you were to go a step further, and use a [[scroll of identify]] on the dagger you didn't drop, and it was an uncursed +0 dagger, then it would '''still''' not stack with your plain "uncursed dagger" (because only one dagger's enchantment is identified).
 == Splitting stacks ==
-The usual way to split a stack is to supply a numeric parameter to the [[drop]] or [[pick up]] command, or when moving items into or out of a [[container]]. For example, if you have 7 daggers in inventory slot ''a'', you can type {{kbd|d}} {{kbd|4}} {{kbd|a}} to drop 4 of them.
+The usual way to split a stack is to supply a numeric parameter to the [[adjust]], [[drop]] or [[pick up]] command, or when moving items into or out of a [[container]]. For example, if you have 7 daggers in inventory slot ''a'', you can type {{kbd|d}} {{kbd|4}} {{kbd|a}} to drop 4 of them.
-This method is sufficient if you simply want to carry fewer items around. If you want to carry around multiple stacks of the same type of item, you will need to take additional measures:
+This method is sufficient if you simply want to split a stack temporarily, as they will quickly merge with each other if you adjust, drop or stash them without a numeric parameter. If you want to carry around multiple stacks of the same type of item and keep them separated, you will need to take additional measures:
-# Use [[name|#name]] to give a name to the stack you want to split (e.g. “[[Throw]]ing” or “[[Quiver]]”)
+# Use the [[adjust]] command to split the stack
-# Use the above method to stash or drop part of the stack
+# Rename one of the stacks (e.g. “[[Melee]]” or “Main”)
-# Rename the part of the stack that is still in your inventory (e.g. “[[Melee]]” or “Main”)
+# Rename the other stack to something else
 You should now have two stacks of identical items, with different names.
@@ Line 41: / Line 40: @@
 Besides conserving on inventory space, getting items to stack is important for efficiency when using [[holy water]] to bless items, or using a scroll of [[enchant weapon]] to enchant an entire stack of arrows. It can also affect how many projectiles are fired in a single turn; a player can only get off multiple shots in one turn if the projectiles are from the same stack.
-There are occasions, however, where one may want to get a stack to split. The way to achieve this is to [[name]] the stacks separately. For example, a starting rogue may desire to both keep one of his starting stack of daggers as a main weapon, and have the rest of the stack serve as projectiles. The way to do this would be to name the entire stack, e.g., "Throwing", and drop all but one. Then, name the last one still in the inventory to e.g., "Main". Then you can pick up the others and they will be separated. It is not sufficient to name them, drop all but one, and then clear out the name for the one in hand - stacks will always take on a name if they do not already have one. This phenomenon can often be observed early on, when one finds an orcish dagger, has the pet BUC test it, and then names it uncursed, only to see other new daggers stack with it.
+There are occasions, however, where one may want to get a stack to split. The way to achieve this is to [[name]] the stacks separately. For example, a starting rogue may desire to both keep one of his starting stack of daggers as a main weapon, and have the rest of the stack serve as projectiles. The way to do this would be to split one dagger from the stack, name it, e.g., "Melee", then name the other stack, e.g., "Throwing". Then, they will stay separated. It is not sufficient to split the stack into two and name one of them - stacks will always take on a name if they do not already have one. This phenomenon can often be observed early on, when one finds an orcish dagger, has the pet BUC test it, and then names it uncursed, only to see other new daggers stack with it.
-This naming tactic is also useful when someone needs to split up a stack of [[water]] to make an initial [[unholy water]] by reading while [[confused]] a blessed [[scroll of remove curse]]. It may be tedious, but it is probably wise to split up around 10 stacks for this purpose.
+Splitting stacks is also useful when someone needs to split up a stack of [[water]] to make an initial [[unholy water]] by reading while [[confused]] a blessed [[scroll of remove curse]]. It may be tedious, but it is probably wise to split up around 10 stacks for this purpose.
 Getting potions to stack is of the utmost importance in [[alchemy]]. All alchemy results will be "diluted potion of X", and diluted potions will only stack with other diluted potions. Because of this, later on in the game it can be advantageous to dilute (by dipping once) potions for alchemy, for increased efficiency. Just beware all the risks associated with [[dip]]ping and [[fountain]]s, and take care to have identified [[acid]], as dipping acid will cause an explosion.
-{{nethack-343}}
+{{nethack-361}}
 <references/>
 [[Category:Item attributes]]

← Older revision		Revision as of 23:13, 19 July 2010
Line 23:		Line 23:

	In order for objects to stack, their [[beatitude]], [[enchantment]], and [[erosion]] status must be exactly the same. Additionally, even a subtle difference in identification status can affect whether or not something stacks. For example, if you have two daggers, and only drop one on an altar and see it was uncursed, those two daggers will no longer stack. Then, if you were to go a step further, and use a [[scroll of identify]] on the dagger you didn't drop, and it was an uncursed +0 dagger, then it would no longer stack with your plain "uncursed dagger".		In order for objects to stack, their [[beatitude]], [[enchantment]], and [[erosion]] status must be exactly the same. Additionally, even a subtle difference in identification status can affect whether or not something stacks. For example, if you have two daggers, and only drop one on an altar and see it was uncursed, those two daggers will no longer stack. Then, if you were to go a step further, and use a [[scroll of identify]] on the dagger you didn't drop, and it was an uncursed +0 dagger, then it would no longer stack with your plain "uncursed dagger".
		+
		+	Perhaps the crysknife does not stack despite its throwable status because [[Objnam.c#makesingular\|makesingular()]] would trip up over "3 worm teeth named cookies", causing all sorts of problems with [[wish]]ing, [[autopickup exception]]s, and general object comparison.

	== Splitting stacks ==		== Splitting stacks ==