-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ID and stacking behavior for darts, javelins #334
Comments
Or maybe they should be able to spawn with an innate + or - enchant! |
Hah, that is such a characteristically cheeky reply. I like it. +1 to the idea of stacking incendiary darts and javelins, though. |
I would argue against free stacking of different sets of throwables, for what it's worth. |
I also like the idea of keeping the door open to spawning blessed (cursed?) throwables. Maybe blessed ones have an improved chance of runic slaying? |
Right, allowing throwables to be generated with enchantments would obviously negate the original issue report, and I agree that would make for a more interesting change. Changing only the starting ID behavior, I expect, would be a simpler, stopgap change not requiring a major version bump, and perhaps make it more obvious that enchantment levels had been added when the starting ID change is reverted. I've never actually tried meleeing with incendiary darts, does that generate infinite combustion? +15 incendiary darts of multiplicity might be fun! |
👍 for being identified by default, if needed we can make a separate issue to discuss merging stacks once done |
Enhancement request: found javelins, darts, and incendiary darts should start out identified as +0.
Experienced players know that all stackables are uncursed, and thus a found javelin is a safe mid-game upgrade from the starting dagger. But this feels like illicit knowledge and generally contradicts Brogue's ethos of all cards on the table.
As a corollary, it would then be reasonable to combine like items found separately into a single stack occupying a single inventory slot.
The text was updated successfully, but these errors were encountered: