public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Map-related deja-vu
Date: Fri, 01 Oct 2004 18:47:00 -0000	[thread overview]
Message-ID: <415DA3D5.4010507@apple.com> (raw)
In-Reply-To: <1096588332.4050.15389.camel@localhost>

Lincoln Peters wrote:

>I just had the weirdest thing happen when I was testing knightmare.g. 
>Although the module is set up to produce a new random map every time I
>load it, the last time I ran it, it produced a map that, as far as I can
>tell, is identical to a map it produced when I was testing a few days
>ago, down to the layout of independent units!
>
>Since the world-size is set to 240x120 (circumference 1440), I would
>think that the chance of getting the exact same map twice would be
>astronomically low.  Has anyone else experienced this kind of behavior? 
>Could it be a bug in Xconq?  Is it more likely a bug in my computer's
>random-number generator?  Or should I consider it to be a sign and buy a
>pair of lottery tickets?
>
It certainly could be a duplicate. I thought about the possibility
when deciding how studly the randomization needed to be, but you
would likely only see the exact dup if you started up hundreds of
games with exactly the same size map, same number of players, same
options, etc., and if the world wasn't seen, you couldn't be sure it
was a dup until nearly the end of the game. If the world was seen and
you really didn't want the dup, you'd just kill it off and start
another game. Given the length of time a game takes, for a normal
player it would likely be years before a dup appeared, assuming
Xconq was not updated in the meantime.

On the flip side, one of my concerns back then was computational
efficiency, which seems rather quaint. One could seed from a bigger
number and do 64-bit arithmetic, will likely be unnoticeable to
performance.

Stan

      parent reply	other threads:[~2004-10-01 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01  0:19 Lincoln Peters
2004-10-01  0:26 ` mskala
2004-10-01  0:49   ` Eric McDonald
2004-10-01  5:45     ` Lincoln Peters
2004-10-01 18:19       ` Eric McDonald
2004-10-01 18:47 ` Stan Shebs [this message]

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=415DA3D5.4010507@apple.com \
    --to=shebs@apple.com \
    --cc=sampln@sbcglobal.net \
    --cc=xconq7@sources.redhat.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).