What would be the problem. I understand the grid can be a nuisance with this but rapid copying of events, brick destruction, and recreation would be sound theoretically. It is just that the brick might loose ownership once remade if the event is not done proper.
What?
I do not mean a brick mover or teleporter. I mean an alternative to the Brick->setPlayerTransform event which is instead Player->setBrickTransform which moves the player you apply it to to a named brick you specify, so that it works properly with all events with Player outputs. For instance, you cannot use the setPlayerTransform event with JVS Doors "onDoorStuckPlayer" because that will teleport the activating client's player, not the player objects getting stuck in it, which might be different. (e.g. someone tries to follow you through a door then it closes on them)
The problem with it would be getting a list of named bricks individually shown on the clients, but a text input where you write a valid brick name would be possible too.
