Oooh... I like that idea!
You can just save a mastercopy. That would be an added process that would really just be extra data needed.
Or, just leave the forge docker in place, just as a marker for the human where the old module was. You want to remove the part? You're gonna have to go out there with a cutting torch.
That's too complicated and unpredictable if the forge docker/rail is adjacent to different blocks. I'd just leave the forge blocks in place by default and add the possibility to link them to another block, by which they'll be replaced upon welding.
Why aren't templates a solution for you? I know the copy paste controls are pretty nasty, but surely you could do what you're describing here with them (assuming you're in single player with no template size restriction).
I can imagine many uses for this option but if I tell them to you your imagination will get no exercise. :p
1: agreed, that one right there is a cock-block for anything to do with Templates. It, and it alone, is the single greatest challenge to overcome.Lukwan said:
Well a good way to be able to do the fusing thing would be to add in kind of like a "Fuse" block, which, when you dock a ship, and then activate it, then the ships would both be fused together at the docks. so basically if you activate the fuser while in the mothership, it will delete the core of the docked ship, and then you just delete the rails. It also allows you to actually build an entire ship in only two parts XD If you do it from the docked ship though then it removes the core of the mothership.
It's a great idea, but with the block ID limitation it would be simpler to use existing blocks to achieve the same result. Perhaps a new piece of equipment, like a welding tool that somehow performs the task of the block you describe. Maybe it melds two adjacent blocks and then converts them to a standard block, also triggering the process of shifting the docked entity to the main entity and thus changing the core to some generic block or camera or something. Actually a camera would be handy.
This is not an issue anymore.
They said they could increase block data from 3 to 4 bytes per block, but I don't believe in unlimited IDs, unless you come up with that link.
Brief low level computer refresher for anyone that doesn't know (keeping it simple to avoid unsigned vs signed and various other things out of the conversation).
That isn't how it works. Most of the 3 bytes is used for orientation, activation and HP. A fourth byte would multiply the available IDs by 256.
This would be 256 * 2048 = 524.288 IDs then. Several new shapes, colors and slab versions would quickly use up thousands of additional IDs. So while being a lot, it's not unlimited.
