Stackable
In NetHack, many varieties of items can stack into one inventory slot. This includes:
- gems, glass, rocks, and gray stones
- potions
- scrolls
- comestibles, except for hatchable eggs and revivable corpses
- candles, if close in age and type
- certain ranged weapons:[1]
- All arrows (orcish, regular, elven, silver, and ya)
- Athames
- Boomerangs
- Crossbow bolts
- All daggers (orcish, normal, elven, and silver)
- Darts
- All spears (orcish, normal, elven, dwarven, and silver)
- Flintstones
- Javelins
- Knives
- Worm teeth and crysknives
- Scalpel
- Shuriken
- Stiletto
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 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 d 4 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:
- Use the adjust command to split the stack
- Rename one of the stacks (e.g. “Melee” or “Main”)
- Rename the other stack to something else
You should now have two stacks of identical items, with different names.
Strategy
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 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.
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 dipping and fountains, and take care to have identified acid, as dipping acid will cause an explosion.
This page may need to be updated for the current version of NetHack.
It may contain text specific to NetHack 3.6.1. Information on this page may be out of date.
Editors: After reviewing this page and making necessary edits, please change the {{nethack-361}} tag to the current version's tag or {{noversion}} as appropriate.
