Todd Mitchell wrote: > I notice that random maps now place a return exit on the final_map - It > would be great to be able to disable this with a mesg entry or to > specify the destination x/y coords on the final_map so that different > random maps can point to the same final map without having an exit > always showing up at the enrty of that map. Also I suppose this means > the random map doc can be updated as not providing a return exit on the > final map was a big no-no in the past. If I recall, the return exit, when placed automatically, pops back to the original location to that entry. Eg, if you have two series of maps (say A and B) that you want to use for the same final map, the quick return should point back appropriately. Note that it is not possible for A and B to use the same real map - each one would probably still need to have its own copy (final_map_A, final_map_B), at least from the server standpoint. Otherwise, you'd get the issue that the exit that leads back up could only lead to one set of those maps. For example, player on series B wanders down, after someone on A already has done so (so final map has been loaded). When he gets to the final map, you don't want the up exit to lead to the bottom of A - you want it to lead to the bottom of B. However, as I think about it, I believe all current final maps are designed for a specific location, and it is the final map itself (located in the map folder) which has the 'pop back to top' exit on it, and it isn't the random map code that is doing this. It just so happens that things are set so that the exit the leads back up one level is placed on the same space (and above) any explicity placed return exits. _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel