TinyCraft [Axe]

[AngelFish]

Heh, that's almost exactly the 2D case of the algorithm I came up with

As you can see from that demo, the algorithm has some problems if you're not careful, but they shouldn't be noticeable unless you have a large scale view like that.

[ZippyDee]

So....how would we use that?

[leafy]

I personally don't see the point of tracking changes; you're going to have to unarchive and archive each map anyways. It might even be harder and take longer to track just the changes, when you could just overwrite the old map with the new one completely.

[ZippyDee]

He's saying that using a reversible RNG you could simply recover the randomized data for the point you are at, so you wouldn't have to save a map at all and you'd ONLY have to save the changes you made to that map for the next time it's generated.

[AngelFish]

I personally don't see the point of tracking changes; you're going to have to unarchive and archive each map anyways. It might even be harder and take longer to track just the changes, when you could just overwrite the old map with the new one completely.

The point of the change list is that there's no map to archive/unarchive in the first place. Memory becomes significantly less of an issue when you're *only* storing the blocks or chunks the player has modified.

*Chunks would be more memory efficient

[ZippyDee]

Well, looking at Notch's algorithm, it looks like what he's doing is generating a smooth 2D noise map for the main terrain (rocks, grass, water) and then another 2D noise map for adding sand and trees and cacti and things like that...Shouldn't be too difficult to do that on calc.

[saintrunner]

This is running fairly awesome 4scale for a 32x32 tilemap.

Hey how many bytes is this?

[ZippyDee]

This is running fairly awesome 4scale for a 32x32 tilemap.

Hey how many bytes is this?

32x32 tilemap, 4 levels of grayscale, meaning 2 bits per tile, so 2048 bits or 256 bytes. Unless I completely botched my thinking there.....

[saintrunner]

hmmm, Thats not too bad, but after the sprites are thrown in it might be a bunch more

[ZippyDee]

Well, how many tiles are there total? We could calculate how much you'd need for a 128x128 map (the size used in minicraft). I think there are 20 tiles total, right? If we could get it down to 16, we'd probably save quite a bit of space...

[saintrunner]

Oh good IDEA! Any body have a calculator? lol jk

[ZippyDee]

Hmm...Maybe there are some tiles that we could combine the value of. Like...you won't see Lava anywhere but under ground, and you won't see Grass anywhere but in the top world. Also, Grass could be Clouds and Rock could be InfiniteFall in the sky world. And we could combine something like Tree and IronOre. That brings it to 16 tile values needed, so we can represent two tiles with each byte. That should simplify things considerably in terms of saving and recalling map data, too!

Edit: They don't have to be those exact tiles. I'm sure there are probably better combinations.

[AaroneusTheGreat]

By the way I still vote for MineCrack for the name. Where's the write-in? -.-

You seem to be chugging along Leafy! Keep up the good work! It's looking good so far. Hopefully you'll be able to get a solution for your memory problem soon. Speaking of, what were we talking about?

[kindermoumoute]

Here a first screen :
For the moment, executable is around 1200 bytes larger.


EDIT : Wow, pretty nice on real calc.

[leafy]

1200 bytes larger? We'll have to cut that down xD

Anyways, I think I've figured out the overworld map generator. Wasn't terribly difficult, the code's just bloody long.