Your message dated Tue, 6 Apr 2010 14:37:04 +0200
with message-id <[email protected]>
and subject line this code was rewritten twice
has caused the Debian Bug report #323079,
regarding crawl: a door was visible through walls
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
323079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323079
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: crawl
Version: 1:4.0.0beta26-4.kon.2
Severity: minor

The closed door of the bottom room is visible from the positions
marked with @ below.  (That is, the door appears highlighted, and
the "x" command describes it as "A closed door." rather than "You
can't see that place.")  The door should not be visible, as there
is a wall in between.  If I open the door, then it is no longer
visible.

   #.....######    #.#                 Kalle the Footpad
   #.....#....#    #<#                 Hill Orc
   #.....####.#    #.#                 HP: 13/13
   ##+#.......#    #.#                 Magic: 0/0
    #.#.####..#    #.#                 AC: 2     (0)
    #.#.#  #..###  #.#                 EV: 10
    #.#.#  #...>#  #.#                 Str: 12
    #.#.#  ##.######.#                 Int: 7
    #.#.#####..%.@@@.#                 Dex: 15
    #........#########                 Gold: 22
    ###.####.#                         Experience: 1/4  (11)
      #.#  #.#                         Level 1 of the Dungeon
 ######.# ##+#####                     a) +2 orc dagger
 .......# #...)..#
 ######.# #......#
      ### #......#
          #......#

I'm running a version with some local patches, but they do not
change the visibility algorithm.

crawl (1:4.0.0beta26-4.kon.2) local; urgency=low

  * Local version!
  * source/item_use.cc (enchant_armour): Properly uncurse the armour,
    rather than the weapon.

 -- Kalle Olavi Niemitalo <[email protected]>  Tue,  2 Aug 2005 23:53:58 +0300

crawl (1:4.0.0beta26-4.kon.1) local; urgency=medium

  * Local version!
  * source/dungeon.cc (box_room_doors): Give up if there are not enough
    good spots, instead of falling in an infinite loop.

 -- Kalle Olavi Niemitalo <[email protected]>  Sat, 18 Jun 2005 10:07:51 +0300

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.12-1-k7
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)

Versions of packages crawl depends on:
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libgcc1                     1:4.0.1-2    GCC support library
ii  libncurses5                 5.4-3        Shared libraries for terminal hand
ii  libstdc++6                  4.0.1-2      The GNU Standard C++ Library v3

-- no debconf information

Attachment: pgpoYhlndauv5.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
This problem appears to be unreproducible in Stone Soup crawls.
The vision code have been rewritten twice, including Rob Vollmert's total
rewrite in 0.6, so it's very unlikely this bug persists in some form.

Of course, we can count on a other, brand new bugs somewhere -- but this one
is in all likelihood a goner.

If I'm totally wrong, please reopen.

-- 
1KB             // Microsoft corollary to Hanlon's razor:
                //      Never attribute to stupidity what can be
                //      adequately explained by malice.


--- End Message ---

Reply via email to