diff options
| author | Adam Borowski <kilobyte@angband.pl> | 2012-06-24 17:02:19 +0200 |
|---|---|---|
| committer | Adam Borowski <kilobyte@angband.pl> | 2012-06-24 17:14:46 +0200 |
| commit | bf500ca0f0c03f9b47483a75c60910e70388e638 (patch) | |
| tree | e9bd0fa575222337ddf703b062481e95006ea856 /crawl-ref/source/mon-movetarget.cc | |
| parent | c702831a7453b0c4c2aed77e2d3b2fd7bb5cf1fd (diff) | |
| download | crawl-ref-bf500ca0f0c03f9b47483a75c60910e70388e638.tar.gz crawl-ref-bf500ca0f0c03f9b47483a75c60910e70388e638.zip | |
Remove #define LOS_MAX_RADIUS
Having both it and LOS_RADIUS is misleading, especially as they're
arbitrarily used. This distinction doesn't make sense anyway, as any
LOS changes need to be done at runtime, only the max matters during
compilation.
Diffstat (limited to 'crawl-ref/source/mon-movetarget.cc')
| -rw-r--r-- | crawl-ref/source/mon-movetarget.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/crawl-ref/source/mon-movetarget.cc b/crawl-ref/source/mon-movetarget.cc index f600b1ca47..6cdc27632b 100644 --- a/crawl-ref/source/mon-movetarget.cc +++ b/crawl-ref/source/mon-movetarget.cc @@ -1101,7 +1101,7 @@ void set_random_slime_target(monster* mon) { // Strictly neutral slimes will go for the nearest item. const coord_def pos = mon->pos(); - int mindist = LOS_MAX_RADIUS_SQ + 1; + int mindist = LOS_RADIUS_SQ + 1; for (radius_iterator ri(mon->get_los()); ri; ++ri) { // XXX: an iterator that spirals out would be nice. |