On Wed, 30 Jul 1997, Sammy wrote:
[[ stuff i wrote and some stuff Sammy wrote snipped ]]
=>
=>The big thing I forgot to mention in my previous post was that I'd like to
=>eliminate most of the zone numbers in the prototype files. What I mean is
=>that rather than have an object file full of objects numbered 8500, 8501,
=>8502, etc, a good generic system might have a "Zone: 85" tag at the
=>beginning of a file, with objects numbered 0 through whatever. This would
=>make renumbering zones a snap.
=>
Another thing I want to do is eliminate the need for rnum values. I find
it rather confusing to have to keep track of 2 sets of values (rnum and
vnum). So, what I will probably do is use a tree of some sort for the
objs and mobs, and a graph for the rooms (with a tree index for zones)
eg.
zone1
/ \
/ \
sub zone sub zone2
/ \ / \
first last first last (first/last rooms in zone)
then the rooms would be loaded connecting them to their respective exits
by pointers to the room, instead of a rnum index into an array.
The only thing I can see that might cause a problem is rooms that have no
exits, and cannot be entered from another room. (ie. an island) Why a
builder would want to waste space with such a room is beyond me, but it
could possably happen. (axiom to keep in mind: end users never do what you
expect.)
The main advantage I can see to this system is that you don't have to
worry about exceeding the 10, 100, 1000, or whatever limit you set per
zone, limit for room vnums. Each zone can be given a range of vnums, so
that a small zone can have vnums 1-20, and not waste the other 80 vnums
that could possably be used by another zone.
So... while you are hacking around with db.c to make the files all conform
to a set standard... You might want to consider something similiar to
this. (although... get the parser working first.. would be hell trying to
do both at the same time.)
Another advantage to losing the arrays for objs/mobs/etc. is the notorious
bugs being discovered with zedit... no need to do the top_of_zone_table +
3 crap... Arrays do provide some ease of use... but when you start
needing to expand them they start to suck.
--
Dez.
void signature () {
printf ("Praise not the day until evening has come; a woman\n"
"until she is burnt; a sword until it is tried; a maiden until\n"
"she is married; ice until it has been crossed; beer until it\n"
"has been drunk. -- Viking Proverb\n");
}
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/08/00 PST