DeleteAboveBricks and LoadSave events.

[Zeblote]

5. There is no serverside function to tell when a client is done loading bricks

Not exactly a callback, but you can check whether every object that is supposed to be loaded has a ghost ID assigned for said client.

client.getGhostID(%brick.getID()) != -1

[Ad Bot]

[Headcrab Zombie]

There's no function for when the brick's are done being ghosted, but there is one for when the save is done being loaded.

This doesn't really help at all. Go load a large save, and see how much longer it takes to ghost than it does to load.

Not exactly a callback, but you can check whether every object that is supposed to be loaded has a ghost ID assigned for said client.

client.getGhostID(%brick.getID()) != -1

I see, I didn't know about this function. I thought ghosting was purely client side, I didn't think the server would be able to get any info about it

[jes00]

Should I even finish this then?

[Thorfin25]

Should I even finish this then?

Yes.

[Headcrab Zombie]

No, as stated this can already be done with another add-on, which is better because:

1.  Blockland used to have a deleteBrick event but it was removed because it could be used it ways that results in bricks you didn't have full trust with being deleted. Any recreation of it is likely to be failed

If you don't feel the risk of having you're add-on failed enough, there's more

2. This would only be usable in single player, as traveling through a door to delete the bricks would forget over anyone else still in that room

3. Continuously deleting and reloading the same bricks is silly. Although it would be less of a problem considering it would only work on single player, it still results in more downtime, you'll have to reload the area every single time you leave and come back to it, whereas with using teleport to distant areas, you only have to load it the first time you go there

4. It's much easier to set up a simple teleport, than making a ton of individual saves, and matching their names up