| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Sometimes, they're there to emphasize a break between two sections of code,
which is good. In a majority of cases, though, they're just inconsistent.
|
|
|
|
|
| |
This fixes issues with the wrong UC title appearing sometimes if str > dex
but base str < base dex (or the reverse).
|
| |
|
|
|
|
|
|
|
|
|
| |
Save subvaults in vault_placement with their parent mapdefs, include subvault
names when generating logfile entries.
Tag monsters with the name of the map that placed them, and write a killermap
field to the logfile if the killer was placed by a map, and the player did not
die in that same map.
|
|
|
|
|
|
|
|
|
|
| |
For most header files, this only saves on having to recompile a
small number of source files, but there are also a few headers
where small changes would now take significantly less time.
This is most obvious for the Tiles build for which the dependencies
have been greatly reduced, so that the only additional includes
when compared to console are strictly library or tile related.
|
|
|
|
|
|
| |
This stops the tons of warnings, while allowing building for both old
and new C++ standards. And if we wanted to use shared_ptr or something,
now we can without being ambiguous.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I had to rename distance() (in coord.h) to distance2() because it conflicts
with the STL function to compare 2 iterators. Not a bad change given how it
returns the square of the distance anyway.
I also had to rename the message global variable (in message.cc) to buffer.
I tried to fix and improve the coding style has much as I could, but I
probably missed a few given how huge and tedious it is.
I also didn't touch crawl-gdb.py, and the stuff in prebuilt, rltiles/tool
and util/levcomp.*, because I have no clue about those.
|
|
|
|
|
|
| |
Only applies to branches with more than one level, so it shouldn't be too many
milestones. In order to get oplace to work correctly, the report_origin_level
argument to mark_milestone() was made slightly more flexible.
|
|
|
|
| |
It is a remnant of a gimmick banner from one of past tourneys.
|
|
|
|
|
| |
This reverts commit 90551e86189b850caf36c73f3445c480abc79f59.
This reverts commit ada134d4137d8d869c0f97e1cd4e553a2e58acc9
|
| |
|
|
|
|
|
|
| |
In portable code, basically every use of long or %ld/%lu/%lx is a bug.
A legitimate use in Crawl is the bit array: storing it in-memory should be
preferably done a word at a time.
|
|
|
|
|
|
|
|
| |
This reverts commit 7cd5a58682c59923555cb4e57b6bb1fe97ef8dfe.
Henzell and Sequell already use oplace correctly, and this commit made Sequell
unable to determine correctly which branch is entered. Updating Gretell with
the oplace code already in place in Henzell/Sequell shouldn't be hard.
|
|
|
|
|
|
| |
This was already done as "oplace", but none of the bots actually reported it.
It's pointless to say you are in Lair:1 when entering Lair, so it's a waste
of space to note the new level.
|
|\ |
|
| |
| |
| |
| | |
stubbing the loading of the morgue file
|
| |
| |
| |
| | |
and builds the list. Shows a short lines and then the detailed listing as you select each entry.
|
|\|
| |
| |
| |
| | |
This includes fixes for 64834896234968 places in master that add new uses of
LEVEL_FOO and so on.
|
| | |
|
|\| |
|
| |
| |
| |
| | |
The exceptions are extern "C", multi-line macros, and json.{cc,h}.
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The death description code is a nightmare...
|
|
|
|
|
|
|
| |
"File:" is shown in your editor's status bar.
"Written by:" was used only for the first person who changed a file. We got
git for that now, and pre-DCSS history is so woefully inaccurate it doesn't
really matter.
|
| |
|
| |
|
|
|
|
|
|
| |
I did review it manually to find places where they made sense (like some
tables), but for a massive sed job like this there might be places that
I missed.
|
|
|
|
|
|
| |
They're in a comma-separated field and use the same text as the @:-line of the
%-screen for now. I made a somewhat arbitrary selection of effects. It's not
clear we shouldn't just save all effects.
|
|
|
|
| |
This adds fields "sdam" and "tdam" to the score file.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This should help against the signed char problems, and is good for
code readability. Now, if you have a char, it's either an untyped
in-memory byte, or a symbol inside a string. Small numbers are instead
[u]int8_t, ints, an enum type, or, in so many cases, bools.
I didn't touch any of the tiles code, as it's currently broken and I don't
want to risk making it unbroken harder.
|
|
|
|
|
| |
Fixes things like "killed by triggering a a Zot trap trap" or
"killed by triggering a hand axe trap".
|
|
|
|
| |
tournament Fedhas banner.
|
|
|
|
| |
check at every point of use.
|
|
|
|
| |
Also, get rid of a few other longs.
|
|
|
|
|
| |
Map descriptions are intended to be human-readable place name qualifiers, such
as Pan (Cerebov's castle).
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Robert Vollmert <rvollmert@gmx.net>
|
| |
|
|
|
|
|
|
|
|
|
| |
For one, don't assert when reading an unknown background from the score file.
Instead, such backgrounds will be output as "unknown" or "??".
Then, make the translation functions from job to and from string aware of the
old "Thief" and "Death Knight" backgrounds, so they can be printed when
crawl lists highscores.
|
|
|
|
| |
That way I'll feel safer changing the meaning of scorefile_entry::cls.
|
|
|
|
| |
scores, nor any with unknown fields.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When generating a milestone for entering a new area, include the level
containing the entry stair/portal in the 'oplace' key. This will allow Henzell
to report the dungeon level containing the Lair entrance, wizlab, etc.
This isn't perfect: oplace will be plain Wrong when the player uses the Trowel
card to create portal vaults outside the main dungeon (such as Trowel in
Pandemonium). Trowel is generally problematic outside the dungeon
(see http://crawl.develz.org/mantis/view.php?id=960).
Since Ziggurats can legitimately be generated in Pandemonium, generate ziggurat
entry milestones in the onclimb event of the ziggurat portal, instead of
waiting until the player has entered the Ziggurat. Unfortunately this means
that the entry place for Ziggurats will be reported in the 'place' field
instead of 'oplace'.
I recommend that this change not be included in 0.6, since we need additional
work to fix Trowel and other issues before we have full milestone sanity.
|
| |
|