Mapping Programs?
- Thread starter MortalDanger
- Start date
I have been using MCmap with MCmapDZ to add a google maps style interface. It renders blocks it does not recognize but the colors are not correct. It is good enough to make out the terrain and figure out where things are.
You can see in that sample the giant redwoods are gray as well as some of the Autumn trees. For now it is good enough for the players on my server.
I know you can give it a colors.txt file to associate block id's with the correct colors, I just have not taken the time to do it yet.
Hope that helps.
You can see in that sample the giant redwoods are gray as well as some of the Autumn trees. For now it is good enough for the players on my server.
I know you can give it a colors.txt file to associate block id's with the correct colors, I just have not taken the time to do it yet.
Hope that helps.
Nice program. Just tried it on my old tekkit single player game. Here's the results https://dl.dropbox.com/u/46396473/output.jpg
My little home, lost in the woods. Hmm, spent weeks in that small area, constantly busy. Doesn't look like it! Couldn't get it to use my Terrain.png file for colours properly though, I'm guessing it's only expecting 16x textures, and I've got 64x. So instead I used the default texture options.
My little home, lost in the woods. Hmm, spent weeks in that small area, constantly busy. Doesn't look like it! Couldn't get it to use my Terrain.png file for colours properly though, I'm guessing it's only expecting 16x textures, and I've got 64x. So instead I used the default texture options.
Wow, great thanks. If anyone ends up editing the color id's, post it here if you would. Thanks again.
dynmaps is forge compatible.
http://www.minecraftforum.net/topic/1524169-132forge-dynmap-dynamic-web-maps-for-smp/
http://www.minecraftforum.net/topic/1524169-132forge-dynmap-dynamic-web-maps-for-smp/
Thanks, Just set dynmap up on my server and it looks amazing. The isometric view is great.
It seems pretty resource intensive and I am concerned about how much bandwidth its gonna use. I only have a few players so it might not be to be a big deal. Render takes quite a long time on a large world. Been running a fullrender and it is still going after about 3 hours. Almost up to 2G of storage for the map. it is nice that I do not have to maintain, render and upload the maps by hand anymore.
Here are a couple of screenshots from my server using Dynmap:
Zoomed for detail:
Yea, I got dynmap as well but it is extremely slow. In fact, it loaded a few chunks and has stopped entirely. I turned off cave rendering to speed it up but nothin' gives. Just sits there with those loaded chunks and makes no other effort. 
Yea, I got dynmap as well but it is extremely slow. In fact, it loaded a few chunks and has stopped entirely. I turned off cave rendering to speed it up but nothin' gives. Just sits there with those loaded chunks and makes no other effort.
Try the command
/dynmap fullrender
Haha, yea I figured that out not 2 minutes after I posted. Dur. I'll post some pics. Thanks again.
So I used some chunk loading turtles to start generating my map. They are slowly working there way out in a spiral pattern and now the map is huge. it will be fun to render it out in a day or so. It will let me and some of our friends carve up our map into little nations
Sorry for resurrecting an older thread, but I've been using mcmapDZ and am trying to sort out a way to properly color some blocks that have been coming out as the wrong color.
I'm trying to get a colors.txt to work for:
Redwood leaves
Construction Foam
Autumn Leaves
Greatwood + Silverwood leaves
Rubber tree leaves (both from IC2 and the other, huge type)
Basalt (working)
Red Rock (working)
I've managed to get some working, but mcmap appears to be disregarding certain blockids as invalid. Through testing it appears that a blockid value larger than 255 will be rejected. Here's my current colors.txt:
(please excuse the strange spacing)
All but the last four ids are rejected. If there's a program that works like mcmap but allows for blockids larger than 255, I should be able to get my colors.txt to work fine. Any thoughts?
*edit* upon looking at what I think is the correct code on github, it appears that the reason for the restriction is that an 8-bit integer is being used to read blockIDs. This means that for larger ids, the result would probably be wrapped around 256 a number of times. For example, here's the wrapped blockid number for construction foam:
610 % 256 = 98
To test this theory I placed construction foam in a square next to stone bricks (both have a wrapped blockid of 98) and ran the mapping program twice. When rendered without a custom colors.txt entry, they both appeared grey. When rendered WITH the custom colors.txt entry, they both appeared white.
I suppose this means that the reason why our redwood trees and whatnot are rendering with strange colors is because the blockids are being wrapped around and probably end up overlapping with other blocks' colors.
I'm trying to get a colors.txt to work for:
Redwood leaves
Construction Foam
Autumn Leaves
Greatwood + Silverwood leaves
Rubber tree leaves (both from IC2 and the other, huge type)
Basalt (working)
Red Rock (working)
I've managed to get some working, but mcmap appears to be disregarding certain blockids as invalid. Through testing it appears that a blockid value larger than 255 will be rejected. Here's my current colors.txt:
(please excuse the strange spacing)
Code:
#ID R G B A Noise
1309 49 150 5 255 0
1312 128 68 28 255 0
1313 128 68 28 255 0
1314 128 68 28 255 0
1315 128 68 28 255 0
610 99 99 99 255 0
1301 219 116 2 255 10
1610 49 150 5 255 0
1610:1 9 80 213 255 0
625 101 150 27 255 0
211 101 150 27 255 0
212 128 68 28 255 0
215 60 60 60 255 15
251 148 70 44 255 10All but the last four ids are rejected. If there's a program that works like mcmap but allows for blockids larger than 255, I should be able to get my colors.txt to work fine. Any thoughts?
*edit* upon looking at what I think is the correct code on github, it appears that the reason for the restriction is that an 8-bit integer is being used to read blockIDs. This means that for larger ids, the result would probably be wrapped around 256 a number of times. For example, here's the wrapped blockid number for construction foam:
610 % 256 = 98
To test this theory I placed construction foam in a square next to stone bricks (both have a wrapped blockid of 98) and ran the mapping program twice. When rendered without a custom colors.txt entry, they both appeared grey. When rendered WITH the custom colors.txt entry, they both appeared white.
I suppose this means that the reason why our redwood trees and whatnot are rendering with strange colors is because the blockids are being wrapped around and probably end up overlapping with other blocks' colors.
He's pregenerating the map. There's nothing to render if a chunk hasn't been 'visited' before because the chunk doesn't exist. He's using turtles to do that.