From ebf5a248635cf60c77083a6f6e2c13a6ac765cda Mon Sep 17 00:00:00 2001 From: Robert Vollmert Date: Thu, 15 Oct 2009 11:31:01 +0200 Subject: Remove fallback calculation from find_ray. There is now a separate fallback_ray() that needs to be called explicitly. I've manually converted uses of find_ray with allow_fallback == true. find_ray with allow_fallback set always returned true, yet there were a number of places that used the return value, in particular in directn.cc. I'll check these later. --- crawl-ref/source/decks.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crawl-ref/source/decks.cc') diff --git a/crawl-ref/source/decks.cc b/crawl-ref/source/decks.cc index f067d84a15..5c13839431 100644 --- a/crawl-ref/source/decks.cc +++ b/crawl-ref/source/decks.cc @@ -1584,7 +1584,7 @@ static void _move_stair(coord_def stair_pos, bool away) } ray_def ray; - if (!find_ray(begin, towards, true, ray, 0, true)) + if (!find_ray(begin, towards, ray, 0, true)) { mpr("Couldn't find ray between player and stairs.", MSGCH_ERROR); return; -- cgit v1.2.3-54-g00ecf