summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/dungeon.cc
diff options
context:
space:
mode:
authorRobert Vollmert <rvollmert@gmx.net>2009-11-10 14:34:37 +0100
committerRobert Vollmert <rvollmert@gmx.net>2009-11-10 14:34:37 +0100
commit672df2f6a49ff8683255e5bad316674d16285f0c (patch)
treea3d04761b18fce07545c67f08f6c4471d31cd659 /crawl-ref/source/dungeon.cc
parentd2b8c2a72d975b9bf6a3f8ea41cff136adf8cb0a (diff)
downloadcrawl-ref-672df2f6a49ff8683255e5bad316674d16285f0c.tar.gz
crawl-ref-672df2f6a49ff8683255e5bad316674d16285f0c.zip
Add conditional bloodifying function and use it in some places.
This might help the reported blood-covered deep water, though I didn't see any obvious case that was a likely cause.
Diffstat (limited to 'crawl-ref/source/dungeon.cc')
-rw-r--r--crawl-ref/source/dungeon.cc4
1 files changed, 2 insertions, 2 deletions
diff --git a/crawl-ref/source/dungeon.cc b/crawl-ref/source/dungeon.cc
index 096700f6f2..adb5ada5c6 100644
--- a/crawl-ref/source/dungeon.cc
+++ b/crawl-ref/source/dungeon.cc
@@ -6547,7 +6547,7 @@ static void _labyrinth_add_blood_trail(const dgn_region &region)
if (path.size() < 10)
continue;
- env.pgrid(start) |= FPROP_BLOODY;
+ maybe_bloodify_square(start);
#ifdef WIZARD
env.pgrid(start) |= FPROP_HIGHLIGHT;
#endif
@@ -6560,7 +6560,7 @@ static void _labyrinth_add_blood_trail(const dgn_region &region)
if (step < 2 || step < 12 && coinflip()
|| step >= 12 && one_chance_in(step/4))
{
- env.pgrid(pos) |= FPROP_BLOODY;
+ maybe_bloodify_square(pos);
}
#ifdef WIZARD
env.pgrid(pos) |= FPROP_HIGHLIGHT;