map_master allows loading prebuilt maps from schematics. The global
'map_master' table has the following fields:



# function map_master.register_map(name, def)
Registers a map. 'name' is a string, `def` a table that looks like this:	
{
	spawnpoint = <vector>, --Relative to minpos
	minpos = <vector>, --Position with minimal x, y, z of map. Is set to {x = 0, y = 0, z = 0} if not set.
	size = <vector>, --Values must be >= 1. They are the size of the map in 16x16x16 cubes.
	path = <string>, --Path where schematics are located
}

or like this:
{
	spawnpoint = <vector>, --Relative to minimal minpos of all sectors/
	sectors = {
			sector1 = {
				minpos = <vector>, --Position with minimal x, y, z of sector.
				size = <vector>, --Values must be >= 1. They are the size of the map in 16x16x16 cubes.
				path = <string>, --Path where schematics are located
			},
			sector2 = {
				minpos = <vector>, --Position with minimal x, y, z of sector.
				size = <vector>, --Values must be >= 1. They are the size of the map in 16x16x16 cubes.
				path = <string>, --Path where schematics are located
			},
			...
		}
}
The second format allows for maps to consist of multiple boxes. while the first one is absolute

# table map_master.registered_maps	
	Stores registered maps indexed by name. In addition to the fields of the
	map definition, registered maps contain a field 'name' that stores the map name.
	If sectors are definied, the registered map contains a minpos which is 
	used to determine the absolute position of the spawn point.
	
	
# function map_master.load_map(name, done_callback)	
	Loads the map with name 'name'. Returns true if the map is known. After
	loading is done, 'done_callback' with the success of loading as boolean
	argument.
