From NetHackWiki
(Redirected from Stack)
Jump to navigation Jump to search

In NetHack, many varieties of items can stack into one inventory slot. This includes:

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.


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.

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.

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 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.

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.

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.

The following information pertains to an upcoming version (NetHack 3.7.0). If this version is now released, please verify that it is still accurate, then update the page to incorporate this information.

Unseen non-tame monsters picking up items will cause the BUC/enchantment/erosion statuses to become unknown, since commit ad7f2afe.

Also, commit 86c29f5b makes identical objects able to merge regardless of known status if you are not blind or hallucinating, making deliberate un-identification generally unnecessary, except possibly for zen players.