Actually, adding or removing area files doesn't require a full reboot unless you are running on a windows platform. Hotreboots work just fine for the situation. In a sense, doing a hotreboot is safer considering you might suffer from a hotreboot failure due to an area on the arealist.txt file being unrecognized, whereas if you do a full reboot, your mud won't be able to boot at all. So the hotreboot failure warning works as a safeguard to let you know there is a problem. As far as anyone being equipped with any particular item from an area that is being removed, don't worry. Dawn automatically calls an extract_obj(); function towards the affected pfiles.
Actually, its a fairly simple matter of removing every area you dont want from the areas.txt file, shutting down the mud, and rebooting on a clean compile. If you do such a thing though, I'd recommend having your staff dump *all* of their items ahead of time. I know DoT is designed to be highly tolerant of situations that would cause instantly fatal pfile corrputions on most other codebases but I'd rather not test it in such a dramatic fashion.
Meerclar - Lord of Cats
Coder, Builder, and Tormenter of Mortals
Stormbringer: Rebirth
storm-bringer.org:4500
www.storm-bringer.org
What is the best way to go about removing all but the OOC, dawn.are and mudschool.are area files, and keep the game from crashing?? :) great areas but I'm trying for some other areas that are my own and just wanted to cut them down to those three at least. Any suggestions? :)
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.