gistfile1.txt

20:41 < aheadley> kahrl_: that's what i was figuring, can you give me just a real high level idea of what minetest does?
20:47 < kahrl_> aheadley: minetest calls each cube a mapnode; a mapnode consists of an ID (tree, dirt, dirt with grass, ...) and two 
                parameters (light and direction for torches etc.)
20:47 < kahrl_> 16x16x16 of these mapnodes are called a mapblock
20:48 < kahrl_> besides the nodes it can contain metadata for specific nodes (like the contents of chests) and static objects 
                (unloaded entities)
20:49 < kahrl_> a stack of those mapblocks (with the same X and Z value) is called a mapsector
20:49 < aheadley> is there a Y limit for mapsectors?
20:49 < kahrl_> the whole map is stored in a sqlite database, each row contains one mapblock
20:50 < kahrl_> Y goes from approx. -30900 to +30900
20:50 < kahrl_> or -30900/16 to +30900/16 in block coordinates
20:51 < aheadley> hooo boy
20:52 < jordan4ibanez_> what was the version before the api changed?
20:52 < kahrl_> jordan4ibanez_: before itemdef?
20:52 < jordan4ibanez_> yes i believe so..was that the one that broke all the mods
20:53 < kahrl_> look for the blog post before the one that announced itemdef
20:53 < aheadley> hmmm, what's the terrain generator like for the surface's Y-coordinate? all over the place or generally with in a 
                  certain range of values?
20:54 < jordan4ibanez_> alright im guessing version 0.4.dev-20120106-1?
20:54 < kahrl_> jordan4ibanez_: sounds like it
20:54 < jordan4ibanez_> ok good
20:54 < celeron55> aheadley: the current one doesn't go much higher or lower than 64, but occasionally it can reach even +-100 or more
20:55 < celeron55> (+-64, that is)
20:55 < aheadley> ok, thanks guys
20:55 < celeron55> aheadley: you should see the code of minetestmapper.py
20:55 < celeron55> it will give a rough idea what is needed; it doesn't work with minetest 0.4 though
20:56 < aheadley> will do
20:56 < celeron55> also it has legacy code to support the old flat-file format