I can see that being useful but not entirely what I was after. ACF actually does this pretty well, you can erase all the clones so there's 0 on screen and it only has a button to add a row, so if there's 0 of something there's also 0 visible rows in the backend. It seems in MB.IO there's always one clone minimum visible. So the request would be the ability to just have 0 fields visible except a button to add clones as needed, and once that's possible we'd be able to remove the final row in a set the same way we can remove the rest.
