| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This introduces a new monster enchantment: ENCH_INSANE (or frenzy),
sends the monster neutral and berserk at the same time. The needle now
has the effect of causing this enchantment, instead of just sending
monsters berserk.
It now actually has some use, even if it is slightly risky.
|
| | |
|
| | |
|
| |
|
|
| |
I probably missed a few spots.
|
| |
|
|
| |
these days.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cloud_struct now has members for colour, name, and tile; colour will be
used instead of the default colour of the cloud type, and will be used
to recolour the tile of the cloud (if it exists). Name will be used to
rebrand the cloud's description, and also alter the message generate
while standing in a cloud.
Finally, tile can be used to completely customise the tile used for the
cloud. The value is stored as a string in order to maintain save
compatibility across ASCII and tiles. A random tile (found using
tile_main_count) from that set will also be used, however, no duration
effects will be applied.
Recoloured cloud tiles using just the colour code should be possible,
though aren't yet fully tested.
This commit bumps TAG_MAJOR_VERSION: changing marshalling of the
FogMachine Lua code causes nasty crashes on reloading saved games.
Otherwise, I don't think I broke anything else. :-)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This re-uses several ideas from the Emerald Eye FR, and implements the
spell "Mislead": this grants the "Misled" status effect to the player,
and causes on-level monsters to appear (glyph, name and tile) to be
other monsters. Only their appearance is changed.
Healing potions and rain remove this status effect.
Mara also has a beefed-up version of the Rakshasa clone spell: it
instead creates an "exact" clone (slightly altered spells list, and
non-unique status for his clones). Only two will ever be created at
once.
Finally, he has the spell "Summon Player Ghost". This spell creates a
ghost of the player (though marked as a summon, meaning that it
(shouldn't) register a milestone, though it will be treated as a
self-ghost kill) that is hostile. Only one of these should be existant
at any one point in time.
I'm pretty sure that I haven't broken anything, but would definitely
appreciate someone sanity-checking this commit.
Known minor issue: Kirke's summon ugly things being cast while having
the Misled status causes them to show up with no glyph.
|
| |
|
|
|
| |
It could be made to ask for a specific number, but I'm too lazy to code that
right now.
|
| |
|
|
| |
The variable wasn't even declared outside the DEBUG check.
|
| |
|
|
| |
saving RNG state.
|
| |
|
|
|
| |
With sense/see invisible being included in monster descriptions it's not
necessary any more and only serves in making monster status longer.
|
| | |
|
| |
|
|
|
| |
See documentation. This is somewhat hackish (or at least, hackier), but
I think there's a precendent for it at least.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Set use_fake_player_cursor = true to use this. This allows
defaulting the cursor to off, which means less cursor blinking
say when travelling.
This patch also moves the cursor control closer to where it's
used, so that the cursor is only turned on for actual input
prompts. I've definitely missed some prompts here: almost
anything that prompts for a single character and reads it
using getch() will not have a cursor with use_fake_player_cursor
set at the moment.
|
| | |
|
| |
|
|
|
|
|
|
| |
To the menu actions ACT_EXECUTE and ACT_EXAMINE add the third action
type ACT_MISC, for things like deleting menu entries. The member
"allow_toggle" has been changed to "action_cycle", with the possible
values CYCLE_NONE (default) , CYCLE_TOGGLE (allow_toggle == true), and
CYCLE_CYCLE (cycle through all three possible action types).
|
| | |
|
| |
|
|
| |
Also simplify mimic handling by referring to map_knowledge.
|
| |
|
|
|
|
|
| |
If you first cycle to a monster, then to some object, the object
will be searched starting at the center.
Also use coord_def& mfp for both input and output.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The same effect can now be achieved by overriding
ch_target_monster. If anyone wants this, I'm happy
to provide lua code.
|
| |
|
|
|
|
|
|
|
|
|
| |
_find_monster now calls ch_target_monster with coordinates of
a possible target.
Currently ch_target_monster is only passed the relative
coordinates of the possible target. It could easily be
passed flags like need_path. Eventually, it should be able
to check what the targetting is about (which spell, etc.),
but that's not so easy to do currently.
|
| | |
|
| |
|
|
|
|
|
|
| |
The option is now just a boolean option, and whether we're
actively targetting with the mlist is stored in
crawl_state.mlist_targetting.
Also remove some duplication of mlist logic from direction().
|
| | |
|
| | |
|
| |
|
|
|
| |
Fix Valgrind warnings about uninialized values in the dist struct (now
class) by giving it a constrcutor which initializes all values.
|
| |
|
|
| |
Oops.
|
| |
|
|
|
|
|
| |
If you fire/cast/zap at a monster with mod-L-click, then you can do the
command over again with the "`" key. Doesn't work yet with spells cast
via the spell pane (toggled on with "_"), or with items fired via
clicking on the inventory pane.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
An assert in ray_blocker was being triggered off of a call to
_get_monster_desc when attempting to cast targeted spells while
standing on a plant (as a Fedhas worshiper).
find_ray returns false when the target square is equal to the source,
which triggers the assert in ray_blocker. I added a check for the
monster being on the same square as the player prior to the call to
_blocked_ray in _get_monster_desc, although this may not be the right
way to deal with the issue.
|
| | |
|
| |
|
|
|
|
| |
This removes a couple of unnecessary includes from header files.
I may have missed adding some tiles includes.
|
| |
|
|
| |
Implements FR 2898414.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also fixes the range_view_annotator destructor
clobbering option "darken_beyond_range".
Options.target_range is now really an option, and called
Options.darken_beyond_range. Current darkening range is
now stored in crawl_state.darken_range.
I can't reproduce SIGHUP retaining darkened range
(BR 2151183) (why would it be saved?), so
range_view_annotator is not a crawl_exit_hook anymore.
crawl_exit_hook is not used anymore, but still present.
|
| | |
|
| | |
|
| | |
|
| | |
|
