Re: DCSS ziggurats

First, sorry about the horrible linebreaks. I'd thought 76 columns
would be enough, but apparently the limit is something closer to 70 or
72.
Also, other than anyone may have inferred from my posting I wasn't
actually angry, more curious and a bit nervous about having made some
mistakes.

On Jul 16, 9:34 pm, Dingir <a...@xxxxxxxxx> wrote:
As you were resolutely asking for an example: I vaguely remember a
bug report where the entrance to the Tomb was created in a region of
the normal (Crypt) map such that you could only enter that area via
controlled teleport.  Someone of the developers answered something
like: "As there is no save file, we can't reproduce it."  The bug
report was deleted.  In a way it's like saying: "I don't believe
your bug report; therefore I will delete it."

Ah, yes, the usual problem with non-reproducable bug reports. I'm
fairly sure whoever closed it didn't actually believe (or mean to
imply) that you were lying, in case you were worrying about that.
However, we do get a lot of reports from players about "buggy vaults"
who didn't actually try to search for secret doors. (Which is
something important to know in that it tells us that some players
don't know about secret doors or searching, but of course that doesn't
change the fact that the bug reports themselves are invalid.) Now of
course I don't know how much information you gave but the problem is
that we get a lot of false alarms like that, so that without a save
file or map dump it _can_ be hard to convince us there's an actual
problem. I'm really sorry about that. :/

True, there is a (large?) number of false bug reports, but if you
get rebutted for trying to honestly submit a bug report, or at least
what you think might be a bug, it can be quite disheartening seeing
your bug report being deleted.

It appears it's a matter of miscommunication once again for which I'd
like to apologize. Whoever wrote that reply was just being terse, but
it came across as rude which was surely not intended. I always do try
to remember to thank the submitter whenever I close a bug report (or
feature request) but sometimes I simply forget, and when I have to
close a bug report as unresolved (or out of date or anything else
other than a proud "Fixed!") my usual "Thanks anyway" seems cheap even
to me. It's always a bad situation. On the other hand there's little
point to leaving bug reports open in the long run that are completely
unreproducible as there's always a chance that it was fixed in the
meantime without anyone noticing. (Which might have been the closing
developer's reasoning.)

Still, this is a very important point. *writes down: "Work on our
communications skills!"*

Another example (but about this I am not sure at all, and have no
means to test it now) was the bug report about the logic of what
rings are being autopicked up or not if you already have a ring of
that kind.  As far as I remember from playing 0.5 several times,
I still noticed some inconsistencies, but didn't bother to pay
much attention to it.

Oh, that was probably me. I can't find your BR right now (searching
for "ring" or "autopick" didn't turn it up) but as far as I remember I
did add all the rings you mentioned, but of course there may have been
more I missed. Hmm... the magic rings stack, don't they? Apparently
the only rings that are not outright bad and not autopicked up if
known are poison resistance, see invisible, teleport control if the
player already has said property (possibly by a ring).

Of course if you do indeed mean "have" (in inventory?) rather than
"are currently wearing" that's a whole different problem and one we
feel we don't really need to cater for. However, if you were to write
a lua script for that we'd probably use it. :p

I can imagine how it is as a (software) developer.  And again,
please do take my small criticism as from someone who truly likes
the game you created and enhanced, respectively.  If I wouldn't
care about crawl-ref at all, I wouldn't even criticize it.

Heh, I believe that, and you weren't even ranting! :D

Thanks for the valuable feedback!

Johanna
.

Quantcast