From: Lincoln Peters <sampln@sbcglobal.net>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Map-related deja-vu
Date: Fri, 01 Oct 2004 05:45:00 -0000 [thread overview]
Message-ID: <1096609511.4050.17763.camel@localhost> (raw)
In-Reply-To: <415CA434.9060904@phy.cmich.edu>
On Thu, 2004-09-30 at 17:26, Eric McDonald wrote:
> mskala@ansuz.sooke.bc.ca wrote:
>
> > Is this a problem? If so, we could easily put in a better seeding rule
> > and/or a better random number generator.
>
> As I recall from looking at the 'util.c' code once upon a time, Xconq
> uses a simple LCRNG. If we wanted something with a much longer cycle
> length, we could go for a Mersenne Twister or some such. Of course, that
> would not be suitable for cryptographic work, but neither is the current
> one.
I don't know much about the logic (?) behind generating random numbers.
But I did find it rather surprising when the map looked exactly like the
map I had played on just a few days ago.
I doubt that an algorithm suitable to cryptographic work would be
necessary for any game, but if I ever find myself playing the exact same
"random" game more than once after the random-number generation code is
upgraded, we'll know that the it still needs work.
>
> But, better seeding would probably be a good first step.
Agreed.
I'm a bit surprised that nobody reported this before. Perhaps that is
because:
1. Anyone else who experienced this problem didn't realize that the maps
were actually identical.
2. Anyone else who experienced this problem neglected to report it (this
doesn't seem as uncommon as we would like).
3. I just got lucky.
---
Lincoln Peters
<sampln@sbcglobal.net>
Between grand theft and a legal fee, there only stands a law degree.
next prev parent reply other threads:[~2004-10-01 5:42 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 [this message]
2004-10-01 18:19 ` Eric McDonald
2004-10-01 18:47 ` Stan Shebs
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=1096609511.4050.17763.camel@localhost \
--to=sampln@sbcglobal.net \
--cc=mcdonald@phy.cmich.edu \
--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).