Bricks that don't exist but still have collision.

[Lord Tony®]

Well it's gone now whatever it was. I need to redownload my mission editor just in case this happens again.

[Ad Bot]

[honytawk]

This usually happens when there is a desync between the client and the server.
Possibly with a brick floating addon.

The client saw the bricks get killed because someone wanded the bottom brick.
But since the server has that brick floating addon, it didn't actually kill the brick and left it floating.
Re-ghosting should reload the bricks in mid air.
So just rejoin the server to fix it.

[Conan]

This usually happens when there is a desync between the client and the server.
Possibly with a brick floating addon.

The client saw the bricks get killed because someone wanded the bottom brick.
But since the server has that brick floating addon, it didn't actually kill the brick and left it floating.
Re-ghosting should reload the bricks in mid air.
So just rejoin the server to fix it.

it was his server :U

[honytawk]

it was his server :U

Yes, but it was probably a dedicated server.
Which means there is still a client and a server.

[Kyuande]

Yes, but it was probably a dedicated server.
Which means there is still a client and a server.

lol what no

[honytawk]

lol what no

Well, I don't see anywhere where Tony said it was on his own non-dedicated server.

I had the same problem on Gunny's server, and there the solution was what I explained.
But I guess it isn't then.
Also because I think I could still hammer the bricks.
Which Tony said he couldn't.

So I am sorry.
At least this is now documented on the help board for if someone who has the same problem I had comes along.