[CF-Devel] Bug - The Closed Random Maps

Fri Sep 28 19:08:33 CDT 2001

 What I believe is happening is that the random map (previously generated)
is getting reset, but the map that leads to it is not.

 This would not be an especially rare occurance - many random maps are
entered from highly visited maps that are not likely to reset, but if no
one visits the random one for a while, it does get reset, and hence
the temp file removed.

 It gets more complicated in the fact that an exit is known by the
server because the slaying field is /!.  However, when the random map
actually gets generated, this slaying field gets change to be
the actual path (/random/000000...).

 The correct solution is for the server to look at the path of a map
that it faled to open, and if it is a random map, re-generate a new
random map from the vars in the exit object (msg), and update the slaying
to that new valid path.

On Fri, 28 Sep 2001, Chachkoff Yann wrote:

>

      Annoying bug: Sometimes, the random maps appear to be "closed". On the server 

     >

      side, you get something like this:

     >

     >

      Trying to load map 

     >

      /home/crossfire/share/crossfire/maps/random/0000000000000001.load_original_map: 

     >

      /random/0000000000000001 (0)

     >

      Can't open /home/crossfire/share/crossfire/maps/random/0000000000000001

     >

      Can't open /home/crossfire/share/crossfire/maps/random/0000000000000001

     >

      Can't read map file: No such file or directory

     >

     >

      The problem seems to appear randomly. Does anyone know where the problem is ?

     >

     >

      Chachkoff Y.

     >

      _______________________________________________

     >

      crossfire-devel mailing list

     >

      crossfire-devel at lists.real-time.com

     >

      https://mailman.real-time.com/mailman/listinfo/crossfire-devel

     >