Minecraft overviewer

User avatar
neko259
Member
 
Posts: 769
Joined: Sun Jun 19, 2011 06:51

Minecraft overviewer

by neko259 » Fri Feb 03, 2012 10:56

Can anybody port it to work with minetest maps? It would be really helpful.
Bitcoin donations: 18r66dJmUjwTmWRTFnorpGMzs8d4B8jzbw
 

User avatar
dannydark
Member
 
Posts: 428
Joined: Fri Aug 12, 2011 21:28

by dannydark » Fri Feb 03, 2012 11:28

This indeed would be a nice addition to Minetest ^_^
 

User avatar
neko259
Member
 
Posts: 769
Joined: Sun Jun 19, 2011 06:51

by neko259 » Fri Feb 03, 2012 11:33

dannydark wrote:This indeed would be a nice addition to Minetest ^_^

I wanted to edit minetest map generator to make it generate blocks view, not only a color. But I can't understand how does it get nodes data from the map database. And the database itself is very strange. Instead of having different columns for different characteristics it stored some encoded coordinate and a blob field with everything else.
Bitcoin donations: 18r66dJmUjwTmWRTFnorpGMzs8d4B8jzbw
 

bcmpinc
Member
 
Posts: 30
Joined: Fri Jun 17, 2011 09:10

by bcmpinc » Sat Feb 04, 2012 14:12

This is what I remember from minetest 0.3:

The world is stored as cubes of 16x16x16 blocks. So if you want to know whats block is at 36 blocks from the origin in x-direction, you need to get the blob field of the row that has coordinate (2,0,0). Because (36 div 16) = 2. The blob is zipped, so you need to unpack it. You can look in the minetestmapper code to see how this is done. Then you need to extract the data, which will give you one 3d array and one set of metadata. In the 3d array you read the value at position [2+0*16+0*256]. This value contains information about what type this block is. Unfortunately, this also uses a non-trivial encoding, but again, minetestmapper.py should help here.
 


Return to Minetest Features

Who is online

Users browsing this forum: No registered users and 34 guests

cron