| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
| |
There's already a check when you try to actually memorize the spell, so
bailing out early here just hides information from the player for no
reason.
|
| |
|
|
|
|
|
|
|
|
| |
In general portals sounds were quite a mess. Ossuary and wizlab in
particular went from quick -> slow, the opposite of all the other sounds.
Sewer, volcano, labyrinth, and bazaar messages are unchanged. Ossuary now
uses the sewer/volcano set of messages, and wizlabs use the lab/bazaar
ones. Bailey and icecaves, which were already almost identical, are merged
and have an edit so that no one word is ever used in more than one time slot.
|
| | |
|
| |
|
|
|
| |
Using int here because an optimizing compiler is allowed to assume that
an unrand_type will never be zero.
|
| |
|
|
|
|
|
| |
Ideally, we wouldn't be using special for unrands totally different from
how items of the same type do, but that's less trivial than this commit.
A centralised place to check for being an unrand should at least make such
a change easier.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
It's not necessary to have a reward in the branch end (Swamp has none, and
Snake has only the gear of the nagas), royal jellies aren't very connected
to Spider, and food isn't very good loot anyway.
The main reason the vaults got ambrosia replaced with royal jelly was
pending a review, so here one is.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that there are only 7 (including chunks), there's no reason to not
have as many as possible of a single type (because of weight being gone),
you often might want to just have one slot of non-chunk food. The
categories before weren't quite obvious (preserved meat didn't include
beef jerkies apparently). Now you can just set whichever food type you
found the most of to be picked up and everything else off.
The downside is that this clutters the menu. If it's too much, possibly
the categories could become chunks, meat, bread, fruit, and other,
splitting bread and fruit for a Ko of Fedhas, for example. That only saves
two lines on this, though.
|
| |
|
|
|
| |
Also cleans up some old Forest code, which might make ^O look a bit
weird on imported saves; probably not a big problem.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Now that darts are gone, all ammo types can have their own colour.
|
| |
|
|
| |
No shift required.
|
| |
|
|
| |
Arguably it might be easy to miss something because of this.
|
| |
|
|
|
|
| |
(no shift necessary).
Thanks to my three year old daughter for user testing!
|
| | |
|
| |
|
|
| |
Broken by cb4b6e1; the stash title is now unwrapped again in Webtiles.
|
| | |
|
| |
|
|
|
|
| |
There are already checks later on during the recall process (in
_try_recall) that make sure they aren't recalled onto non-habitable
tiles, so there's no need to ban them from recalling at the start.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Since it no longer exists!
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This allows us to have a consistent and logical ordering of branches
without requiring the branch enum itself to be reordered (which could
have save compatibility implications). The new ordering of branches just
moves Depths to the place in the ordering that it already is planned to
go on the next major save compat bump, but other changes are possible,
if desired. All places in the code that iterate over branches have been
updated to use the new iterator except for code dealing with save files,
which still uses enum order, so that we can change the display ordering
without affecting saves.
|
| | |
|
| | |
|
| |
|
|
| |
Could occur when hitting an enemy with a distortion weapon.
|
| |
|
|
|
|
|
| |
Not needed now that we've branched 0.15.
This reverts commit 8064468542592958c6ace5dc27aa0fd88cce04a9.
This reverts commit 0f053f10eb5bf6e8df296044933b8f82496ce8d3.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Remove mentions of encumbered, overburdened, strength increasing
carrying capacity, and antitraining; update description of
crosstraining; add description of +slay and remove +acc/+dam
descriptions; remove a strange and largely incorrect mention of
int helping 'certain magical items'. (CBoE requires 2 int, but
that's it.)
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
There's a general agreement that Gozag isn't ready for 0.15;
he needs a significant amount of design work. For now he will
languish in trunk, like the lava orcs of yore. (Unlike them, he
will almost certainly be in 0.16.)
This commit is extremely ugly & hacky & should be reverted as
soon as we branch.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
it seems to be intentional that they are considered safe during travel
and explore, but they certainly shouldn't be considered safe when you're
actively fighting monsters.
|
| | |
|
