Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@Vivit-R
Copy link
Contributor

@Vivit-R Vivit-R commented Oct 8, 2021

Currently, items that have been #named stack with items that have not, with the unnamed item stack acquiring the name of the named item stack as soon as the two meet each other in your inventory. This means that it's strictly better to have a stackable item informally BUC-identified than it is to have it formally BUC-identified, because then other items with the same beatitude you find later will stack with it and become (informally) BUC-identified as well.

This results in strategies like dropping only one dart on the altar and #naming the stack according to the results. To remove this tedium, I've tweaked the behavior so that formal BUC-identification behaves the same way as informal BUC-identification. Some variants already implement this change—I know Fourk does, but I'm not sure about 4.

A more radical possibility I considered was doing the same for the knowledge of the enchantment/fooproofing of an item, effectively removing the effect of ID status completely (except maybe dknown when the player is blind) on the stackability of items, but that's a larger change, so I'm saving it for a different PR.

@nhcopier nhcopier deleted the branch NetHack:NetHack-3.7 January 27, 2022 16:20
@nhcopier nhcopier closed this Jan 27, 2022
@nhmall nhmall reopened this Jan 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.