emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#33119: closed ("Bad item name" in Dungeon Crawl St


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#33119: closed ("Bad item name" in Dungeon Crawl Stone Soup)
Date: Tue, 23 Oct 2018 16:30:02 +0000

Your message dated Tue, 23 Oct 2018 12:29:14 -0400
with message-id <address@hidden>
and subject line Re: bug#33119: "Bad item name" in Dungeon Crawl Stone Soup
has caused the debbugs.gnu.org bug report #33119,
regarding "Bad item name" in Dungeon Crawl Stone Soup
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
33119: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33119
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: "Bad item name" in Dungeon Crawl Stone Soup Date: Mon, 22 Oct 2018 14:41:38 -0400 User-agent: mu4e 1.0; emacs 26.1
In crawl (and the crawl-tiles variant) I get frequent error messages
when levels are being generated like "Bad item name: fruit", which
appears to be for item types that were removed from the game.

Worse yet, when starting some of the sprints (eg The Pits), the game
freezes up, apparently with too many error such messages.

I figured this was due to the crawl-upgrade-saves.patch file, but when I
tried building without the patch I got the same errors.

Anyone experiencing the same?



--- End Message ---
--- Begin Message --- Subject: Re: bug#33119: "Bad item name" in Dungeon Crawl Stone Soup Date: Tue, 23 Oct 2018 12:29:14 -0400 User-agent: mu4e 1.0; emacs 26.1
nee writes:

> As a workaround for now you can rename your ~/.crawl directory to
> ~/.crawl-backup and play with a fresh saves directory for the new version.
>
> Here is an example:
> mv ~/.crawl ~/.crawl-backup-pre-0.22.1

This worked... I was even able to keep the scores file, though I deleted
everything else.  I stopped getting the error messages.

I'm unsure if the issue was actually being hit by anyone else, and
whether the patch needs work or not, so I'm closing this.  In the event
it should be reopened, then reopen it.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]