yes, but the floor slab would be made in a different way. but the columns, and series of floors could be made with any grid point design

@@DCOParametric My strategy was a separation of the slabs and the grid structure but coordinating both is quite a challenge.

I can think of a solution, but it would not be using data trees. It would be to create the overall building forms first, with variable height, then contour vertically. Let me know if that doesnt make sense, I can always record a quick video showing what I mean.

@@DCOParametric The idea was basically to replace the slider of the building floors with a series, and then move them accordingly. Since they are all produced at once, but the graft is right before duplicating and moving the floor slabs, I figured it messes the data structure? I'm still trying to wrap my head around all this :) The idea is then to do X axis floor numbers, and Y axis slab size, to end up with a demonstration on a 10x10 gris of the 100 different buildings one can make using your algorithm :) Edit : it's a challenging puzzle. However, I figured it's right at the Grid that it doesn't want to make each grid and move it incrementally. Edit : it's because the series (functions) operate list block after list block. Data tree is for managin these list blocks into a hierarchy. And now after diagnosing and testing each component, I might find a way to make it work. Will it be able to handle additional dimension of complexity? Linear algebra flashbacks LOL

yes, correct that way works also

depends on what type of beam, if dropped, you would see them. If flush with the floors this script works, and can be further developed to show the beam system within the floors. check out some of the newer tutorials where I go over the process for creating a beam system