mikeprimm

Getting clean run with a warning message with current builds: https://dynmap.us/builds/DynmapBlockScan/DynmapBlockScan-3.6-SNAPSHOT-forge-1.12.2.jar

Not seeing anything in that dump to suggest dynmapblockscan - lots of exceptions from other mods, though....

Oops - sorry - haven't documented this change, but block aliases in v3.0 are block NAME based vs block ID based. I failed to update the default configuration.txt with the...

Just pushed a partial fix - grab latest DynmapBlockScan (and be sure you have current Dynmap v3.0 to match it).

I'll be getting more active on this later this week - I've been in the middle of a 1.11.2 migration/upgrade for the server I admin (and do much of the...

OK - this now is DOING something :) It isn't even close to done, but many/most solid cube blocks provided by any mod should now render (including blocks like logs...

Eventually, sure - the 'handling custom block automatically' thing is a lot less interesting there, but the 'final' version will also include handling of custom block models in RPs (including...

I've added a 1.12 build - http://www.dynmap.us/builds/DynmapBlockScan/DynmapBlockScan-3.0-alpha-1-forge-1.12.jar for DynmapBlockScan, http://www.dynmap.us/builds/DynmapForge/Dynmap-HEAD-3.x-forge-1.12.jar for DynmapForge v3.x. These are even more lightly tested than the 1.11.2 - I'll still be doing most dev and...

We now have builds for 1.10.2, 1.11.2, and 1.12 - all the latest can be found under http://www.dynmap.us/builds/DynmapBlockScan . All depend on the latest DynmapForge 3.x builds from under http://www.dynmap.us/builds/DynmapForge...

It literally cannot work on pre-1.8 builds: the whole basis of BlockScan is to work off of the data-driven (JSON-encoded) rendering data for blocks that most blocks use, starting as...