Re: Suggestion for reducing size of map files, server/client bandwidth

[Mark Wedel <master@rahul.net>]

 Actually, it is pretty easy to write a simple shell script to add
whatever archetype you want to a large region of the map.

 This is how I do the exists in the world maps.  Have a script that writes
the relevant data (ie, arch exit, x $i, y $z, sp $b, hp $q, end)  I then
insert that information into the start of the map (using a text editor)
but beyond the actual map object.

 Same can easily be done for floors.

 Doing backgrounds is going to be more effort thant it is worth, and
very likely, all that will happen is that this background gets turned into
the relevant object for that area of the map. (to actually do various lookups
to seeif the space in question is a floor or not could be done, but would
more likely make things lower than they are now.  Plus, that would have
to be written.)

 crossedit also allows filling of large areas to whatever is wanted.

 Maps that miss floors under chairs can pretty eaisly be fixed, and this
is an error on the map makers part in the first place.  Map makers will
always make various errors, trying to put code in to prevent that
would gain little.

 The object structure does need to be cleaned up.  There is no reason a floor
needs to take 280 bytes.  But it will probably always take at least
60 or so.

 The other problem with regions or backgrounds is this:  In some cases,
certain map makers want objects hidden below the floor (Example: buttons).
In other cases, the map maker wants them above the floor.  If you
have generic backgrounds, one of these will always be true.

 --Mark