In theory, it only keeps in memory the chunks (16x16x8 that can currently be seen by someone, so once an individual has gone out of sight it's not much a matter of how far, (but just a bit of CPU and disk size as the world expands).
But given the various other stuff that's been said, I'm not sure how accurate that is.
Aye, the Backup Plugin i'm using is meant to create a PNG of the world map when it does the backups, but I haven't installed the map plugin that actually lets it do that yet. I'll go about doing that now.
Ahhhh hahaha, I wanted to make a pit in the middle of my maze with lava in it and I've just burnt my entire maze down. Including all the green wool (XEN! :@) which took me all of last night to make.
Roses are bollocks, Violets are crud, I hate bloody flowers, And much prefer mud.
Best thing would be to (this would be farrrrrrr easier on linux btw :(( ) run a small web/ftp server on the same machine and when the png is generated, automatically convert it to a fairly low (like 50% quality) jpeg and move it to the webserver. A jpeg will be a bit mooshy but it's a fair compromise between detail and size.
Fair bit of work there, obviously so maybe just do it once a week or so by hand.
Yeah, I was thinking down that route but to it would probably make more sense if someone else could host it (either at home or on some hosting) so I only have to upload it once, as like I say bandwidth is stretched to fuck as it is :|
Probably don't even need to go that far - I suspect a 75% JPEG would balance filesize/quality acceptably.
I wonder if doing a 8-bit PNG with only 64 colours might even give a good balance - just tried it on the above image and it comes out at 103KB (i.e. 40% filesize of the JPG).
There are PNG optimising utilities that can probably do that in a scripted way.
