Make config option to complain about unknown blocks.

[GoogleCodeExporter]

Please make a configuration option to complain about unknown blocks found in 
world files.
And to dump them into blockConfig format file.
Would make it that much easier to prepare texture packs for mods.

Original issue reported on code.google.com by anrdae...@freemail.ru on 19 Apr 2012 at 11:10

[GoogleCodeExporter]

It would be possible to log the unknown block id's not found in the 
blockConfig.xml. Dumping to the xml format cannot be done as we cannot glean 
any of the other information about the block type and textures from the world 
data.

We will consider logging unknown block id's not defined in the xml.

Original comment by sambened...@gmail.com on 20 Apr 2012 at 12:31

• Added labels: Priority-Low, Type-Enhancement, Usability
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by sambened...@gmail.com on 20 Apr 2012 at 12:42

• Changed state: Considered

[GoogleCodeExporter]

I don't ask you about filling information you can't acquire. (Why would I? O.o)
But dumping block:damage map into XML (With all blocks being <air> or just 
commenting out the dumped chunk) will make it easy to fill the rest by hands.
Also, on a side note, see another issue about BlockConfig format.

Original comment by anrdae...@freemail.ru on 20 Apr 2012 at 12:46

[GoogleCodeExporter]

v 2.14 should now report the id:data values it couldn't match up right after 
the chunks are scanned. I was not able to test it completely.

Original comment by sambened...@gmail.com on 1 May 2012 at 3:56

• Changed state: Fixed

[GoogleCodeExporter]

Seems like it doesn't do so. I don't know, if I need to activate this option 
explicitly, though...

Original comment by anrdae...@freemail.ru on 23 May 2012 at 12:49