all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: nee <nee@cock.li>
To: 33119@debbugs.gnu.org
Subject: bug#33119: "Bad item name" in Dungeon Crawl Stone Soup
Date: Mon, 22 Oct 2018 21:49:33 +0200	[thread overview]
Message-ID: <3e8642cc-c869-c470-598e-c7556c3c6575@cock.li> (raw)
In-Reply-To: <87ftwxj02l.fsf@dustycloud.org>

Am 22.10.18 um 20:41 schrieb Christopher Lemmer Webber:
> 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?
> 
> 
> 

Something is wrong with the patch. It probably doesn't upgrade the
saves. Usually crawl looks at the build date and compares that to the
build date your save was made with, but in guix that's always 1970, so
it would never upgrade saves. The patch should have fixed this by also
adding the build-version to the save, but there seems to be some bug so
it doesn't trigger the upgrade.

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

  reply	other threads:[~2018-10-22 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 18:41 bug#33119: "Bad item name" in Dungeon Crawl Stone Soup Christopher Lemmer Webber
2018-10-22 19:49 ` nee [this message]
2018-10-23 16:29   ` Christopher Lemmer Webber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e8642cc-c869-c470-598e-c7556c3c6575@cock.li \
    --to=nee@cock.li \
    --cc=33119@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.