Hey,
i won’t answer the “How to save answer”, but i MUST tell you something about the last sentence:
That’s a no go. With thousands of blocks you will run into performance issues pretty fast.
I recommend using either the InstanceStaticMesh Component or thinking about a way like Minecraft did it.
They are building the meshes by hand (letting the Engine render triangles based on given verts).
Only visible Block sides are drawn etc. I did a Minecraft game in Unity a few years ago.
Minecraft is already running poorly (though that’s mainly due to Java) and they are only rendering the visible sides
of each block. So if you place too blocks onto each other, the 2 sides that they meet on aren’t drawn.
I think Minecraft checks if the Block (for each side) is AIR or not. If it’s not AIR, then don’t draw the side.
Of course it’s not only doing this for AIR, but also for other things that don’t completely cover the side.
So if this, for example, is a chunk of blocks:
http://puu.sh/ngfYc/7a99d5acb7.jpg
Then this is all that will be rendered. If you now remove a block, the block that sits beneath the one that got destroyed will have an AIR block
above it and its upper face will be drawn.
This saves LOTS of performance.