Something I noticed recently is that, when you select not to render the whole world, but only a part of it, the numbers you have to put in are CHUNKS, not coordinates. So when you try to render an area of "a couple thousand of blocks" and you type in from "-2000" to "2000", you actually render the area from the coordinates -32000 to 32000, and it's no wonder that this takes quite a while.
Maybe this misunderstanding solves your problem, The TopMostDog, but if you already figured it out excuse me :-D
Rollback Post to RevisionRollBack
There's a block? Break it. There's a creeper? Slay it. There's a diamond? Get it!
I just tried rendering our world, and MCMap seems to be having a few issues. For simplicity, I copied the server world into the singleplayer save folder so MCMap would find it easily.
1) The big issue is that I've run into is that there are a few areas where it just doesn't render. I'm not exactly sure why, as there is most definitely world there. In some cases, I've even been building there.
2) There are a few areas that are rendering with odd colours: ores on the surface seem to render with a pinky colour, while shallow water and swamps seem to get a purplish-grey colour.
Follow Up: At least in the case of the gash in the picture, it seems MCMap found some data corruption in my world. Given that I copied the data into the SP save and MCMap made the picture from the SP save, I loged into the server and visited the area there and low and behold the server had to generate fresh terrain to fill in that area. Not sure how it came to be glitched, but that's the way of things. Had to replace several regions from backups, and in-game it seems to be in proper condition, so I'm doing another render to see if that fixes things.
I've only had MCMap for a day, and it is already proving useful.