22 Mar, 2010, boblinski wrote in the 1st comment:
Votes: 0
Okay, I've not rebooted in a while, and I haven't had any crashes… but when I rebooted a couple of minutes.. I got this:

Quote
Mon Mar 22 00:04:25 2010 :: [*****] BUG: Fix_exits: 2509:2 -> 2508:0 -> 2510.
Mon Mar 22 00:04:25 2010 :: [*****] BUG: Fix_exits: 2600:0 -> 2598:2 -> 2603.
Mon Mar 22 00:04:25 2010 :: [*****] BUG: Fix_exits: 1848:1 -> 1847:3 -> 1849.
Mon Mar 22 00:04:25 2010 :: ROM is ready to rock on port 8888 (0.0.0.0).
Mon Mar 22 00:04:30 2010 :: Sock.sinaddr: 114.134.11.17


I've gone to rooms 2509 and 2508 etc.. but cannot find anything wrong.. can anyone clear up this issue for me a little?

Thanks,
Bob.
22 Mar, 2010, Koron wrote in the 2nd comment:
Votes: 0
Look at the actual .are files. Chances are there are errors of some sort in each of those rooms (probably corresponding with the numbers 2, 0, and 1, respectively). Once the mud starts up, it autocorrects them, so you wouldn't see anything without looking at the files.
22 Mar, 2010, ocson wrote in the 3rd comment:
Votes: 0
Those errors are generated, for example, if you can leave east from a room, then head west, and not end up where you started.
22 Mar, 2010, Sandi wrote in the 4th comment:
Votes: 0
It looks like this:
for ( door = 0; door <= 5; door++ )
{
if ( ( pexit = pRoomIndex->exit[door] ) != NULL
&& ( to_room = pexit->u1.to_room ) != NULL
&& ( pexit_rev = to_room->exit[rev_dir[door]] ) != NULL
&& pexit_rev->u1.to_room != pRoomIndex
&& (pRoomIndex->vnum < 1200 || pRoomIndex->vnum > 1299))
{
sprintf( buf, "Fix_exits: %d:%d -> %d:%d -> %d.",
pRoomIndex->vnum, door,
to_room->vnum, rev_dir[door],
(pexit_rev->u1.to_room == NULL)
? 0 : pexit_rev->u1.to_room->vnum );
bug( buf, 0 );
}
}


As you can see, in stock ROM rooms 1200 through 1299 are exempt from the building code. Sometimes you want to make a maze….
0.0/4