Author Topic: Convert a Small Brick Build Into an Individual Brick Add-on -Proposal-  (Read 2747 times)



How can I do that?
nooooooooooo idea

you or someone else will just have to use whatever posts and information provided to help you along

How can I build a tree into bricks, force it into one brick, then remove all the internal faces?

If you don't leave holes in the middle, all internal faces are removed automatically. Bricks that are made properly will cover each other and hide useless faces.

Possible, but you would need an add-on that allows overlapping bricks so you could build inside the bounds of the "house" brick, and as Zeblote mentioned, there is a limit on the amount of collision meshes you can have. Another main issue is the fact that you can't recolor different parts of the house, and if you could, all those parts would be the same color (or based off it)

If you don't leave holes in the middle, all internal faces are removed automatically. Bricks that are made properly will cover each other and hide useless faces.
What are holes in the middle? Which gaps do you refer to?

What are holes in the middle? Which gaps do you refer to?
my guess is that he's referring to if there was empty space inside the tree, as if the tree is 'hollow'.

my guess is that he's referring to if there was empty space inside the tree, as if the tree is 'hollow'.
And if it is solid and less than ten bricks then I can make it into one brick?

And if it is solid and less than ten bricks then I can make it into one brick?
There's no point in doing that.

There's no point in doing that.
Then how do I make a small build into one brick?

Alright kids, it's time to learn about faces!

See this rectangular prism (2x4 brick)?

It has six faces. Blockland makes it so you can see each of these faces. What if we add a 2x2 brick to the edge of it, how many faces are there now?


Six! The two faces that touch each other are not rendered since no one will see them.


If you were to set your camera inside a brick you wont see these faces. Why? they don't exist!

Let's say you made a tree out of twenty bricks, and had those bricks turned into one brick that looked exactly the same. That one brick would lag just as much as the twenty. Because in the end they still have the same number of faces.

These are problems with your request Neventii:
  • Most servers only reach one fifth of the brick limit. Having multiple bricks as one serves no function do to this.
  • A converted brick would act the same way as all the bricks it was originally made out of.

As long as there is no faces showing within what you build it will act as one brick. If you want to be able to move what you build around like one brick I suggest getting the Duplicator. Go to page 28 of the topic and see how it works for painting the Duplication as well!

As Zeblote and The Resonate! have stated this request serves no purpose. Truthfully it would be worse then having multiple bricks because of how bricks work code wise.

The Resonate! have stated this request serves no purpose.
nah i would maybe use it out of sheer laziness

instant chairs and other small builds

when you talk about 1/5th of the brick limit, do you mean the 256k or the 1mil

nah i would maybe use it out of sheer laziness

instant chairs and other small builds

when you talk about 1/5th of the brick limit, do you mean the 256k or the 1mil
Most people go up to the old brick limit of 256k which is about 1/5th of the current brick limit of 1mil. With 200k being 1/5th of 1mil and just I sort of rounded down the rest for the 1/5th estimate. With the brick limit of 1,048,576 and the old brick limit of 256,000 the old brick limit is about 1/4th of what it is now. Or more precisely, the old brick limit is 24.4140625% of what it is now. Now since I have crunched the numbers I apologize for my mathematical error.

Also wouldn't it actually be easier not to use a converter?
Let's say this add-on was hypothetically made, and made as best as it possibly could. Here is what would happen: You would first have to make the build, then you would select the build with a tool (like the duplicator) that would convert it into one brick. Do to how Blockland works you would have to relaunch your server for it to appear in the brick list.
You would no matter what have to close and open your server for this new brick to appear. The duplicator in turn eliminates the hassle you would have of having to close and reopen your server. For with the duplicator all you have to do it make the build, select it, and place it where you need it.

If Zeblote's duplicator included duplication saving and a GUI from which duplications could be selected like the brick cart that would be much more efficient. Also if there were server settings for whether what you see appear in the list of duplications to load were just your own dupe saves or everyone's from the server. That seems like the most practical idea to me. 

Most people go up to the old brick limit of 256k which is about 1/5th of the current brick limit of 1mil. With 200k being 1/5th of 1mil and just I sort of rounded down the rest for the 1/5th estimate. With the brick limit of 1,048,576 and the old brick limit of 256,000 the old brick limit is about 1/4th of what it is now. Or more precisely, the old brick limit is 24.4140625% of what it is now. Now since I have crunched the numbers I apologize for my mathematical error.

Also wouldn't it actually be easier not to use a converter?
Let's say this add-on was hypothetically made, and made as best as it possibly could. Here is what would happen: You would first have to make the build, then you would select the build with a tool (like the duplicator) that would convert it into one brick. Do to how Blockland works you would have to relaunch your server for it to appear in the brick list.
You would no matter what have to close and open your server for this new brick to appear. The duplicator in turn eliminates the hassle you would have of having to close and reopen your server. For with the duplicator all you have to do it make the build, select it, and place it where you need it.

If Zeblote's duplicator included duplication saving and a GUI from which duplications could be selected like the brick cart that would be much more efficient. Also if there were server settings for whether what you see appear in the list of duplications to load were just your own dupe saves or everyone's from the server. That seems like the most practical idea to me. 
First of all, thank you so much for your contribution to this thread. You have been very helpful. Secondly, even if I can not reduce brick count, would it act as one brick when evented?

First of all, thank you so much for your contribution to this thread. You have been very helpful. Secondly, even if I can not reduce brick count, would it act as one brick when evented?
Yes it would act as one brick when evented, however the duplicator can also do this (page 28 of the duplicator thread). The duplicator has been modified from its original purpose of copying builds into treating a select group of bricks as one.

One of the primary drives behind this request is you want to be able to reuse certain elements of what you build. Set up an area while building of where you make things for duplication, when you want to add it to the primary build you are working on just select it with the duplicator and move it over.

The reasons behind your request are decent, but functionality the idea of a converter for small brick builds into one brick make it a bad idea. Luckily the duplicator can satisfy most of your requirements.