summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/hints.cc
diff options
context:
space:
mode:
authorChris Oelmueller <chris.oelmueller@gmail.com>2013-09-05 05:30:02 +0200
committerelliptic <hyperelliptical@gmail.com>2013-09-17 19:36:46 -0400
commitfa329ecffc128ad36e75b5129d71f748f85d5c07 (patch)
tree51185cfed91f015cc1b493c5987a8c4f634b5728 /crawl-ref/source/hints.cc
parent77324f1d651b4d77a2af873fafaa5ec9b7da0782 (diff)
downloadcrawl-ref-fa329ecffc128ad36e75b5129d71f748f85d5c07.tar.gz
crawl-ref-fa329ecffc128ad36e75b5129d71f748f85d5c07.zip
Use piety_breakpoint 30 in good god code
This is the first legit > comparison as opposed to >= which breakpoints usually compare to. Anything that should be done?
Diffstat (limited to 'crawl-ref/source/hints.cc')
-rw-r--r--crawl-ref/source/hints.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/crawl-ref/source/hints.cc b/crawl-ref/source/hints.cc
index 084749ce3d..d56e789296 100644
--- a/crawl-ref/source/hints.cc
+++ b/crawl-ref/source/hints.cc
@@ -2538,7 +2538,7 @@ void learned_something_new(hints_event_type seen_what, coord_def gc)
" didn't mind your converting to " << new_god_name
<< ". ";
- if (old_piety > 30)
+ if (old_piety > piety_breakpoint(0))
text << "You even kept some of your piety! ";
text << "Note that this kind of alliance only exists "