On Sat, 1 Feb 2003 [EMAIL PROTECTED] wrote: > Yes, I am aware of these differences and have fixed them already...
In order to spot these differences, I would imagine that you've got a quite intimate knowledge of the area file formats, or an ability to figure it out. After all, the changes aren't too obvious to someone who didn't know what to look for. And once you knew what the problems were, fixing them wouldn't be hard for anyone who knew what they were doing. (Therefore, the fact that you fixed them would mean you knew what you were doing at least a little bit). Yet on the other hand, you state that you don't know how to fix the differences between the stock door flag format and your new and improved format. This just doesn't add up. Based on the fact that you don't really understand how the exit flags work, I'm going to come to the conclusion that you also don't understand the problems pointed out to you, and have *NOT* fixed them. Your first course of action should be to go back and fix them. > but because I changed the way exit flags are saved and loaded > in my areas, my MUD will no longer load an area with exits saved > in the old manner. Really? Have you actally tried loading areas with exits saved in the old manner, or did you just make that up? Last time I checked, when ROM has a problem with an area file, such as in fread_number, it prints out the file name and the exact line the problem is on. The first thing I would do if I had an area file problem would be to actually look at the line it's fussing about, before making wild guesses as to what the problem would be. Dennis > > 2 things probably are different from a ROM based mud. > > > > 1) an extra ~\n in > > fprintf(fp,"#%d\nNAME~\nNO DESC\n~\n~\n0 0 0\n",vnum); > > 2) you don't have extra exits, so need to remove anything having to do with > > nw, ne, sw, se > > > > Also look in your #areadata or #area stuff to make sure that has the same > > stuff.
