public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
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:19:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0410011408140.744-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <1096609511.4050.17763.camel@localhost>

On Thu, 30 Sep 2004, Lincoln Peters wrote:

> I don't know much about the logic (?) behind generating random numbers. 

There is much logic (determinism) behind computer generation of 
"random" numbers. Most generators should more properly be called 
pseudorandom number gnerators (PRNG's).

To get some "true" randomness, you have to look for sources that 
cannot be [easily] modelled. One example is backscatter of laser 
light off of a swirling fluid; use the coordinates of the 
backscattered rays and, voila, you have something that might pass 
the definition of "random".

> But I did find it rather surprising when the map looked exactly like the
> map I had played on just a few days ago.

As Matthew was saying, the statistical probability of such an 
occurance is higher than one might suspect, __at least with the 
current seeding mechanism.

> I doubt that an algorithm suitable to cryptographic work would be
> necessary for any game, 

Not in the game itself. I was thinking more towards if Xconq ever 
went to a secure client-server model.

> 3. I just got lucky.

Yep. It must have been your "birthday."

Eric


  reply	other threads:[~2004-10-01 18:17 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 [this message]
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=Pine.LNX.4.44.0410011408140.744-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --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).