Author Topic: Bug Report - Client sided brick destruction  (Read 551 times)

On my current server I have been building a very tall platform. Some of the people I build with have been complaining that when a brick gets destroyed the entire build falls apart. The bricks are all still technically there, but they can not see them. I just figured out the issue. On my server I have a lot of fog for ambiance so the view distance is turned way down.

The issue:
Players who have joined my server before spawn in the same place that they were at when they left if they had joined previously. After bricks are finished ghosting, the player will assume everything is loaded. This is in fact not the case, The bricks holding up the structure were not loaded for the client on my server. When anyone breaks a brick on the build the client's Blockland instance thinks that the brick was holding everything up.

Obviously an easy fix would be to fly around and make sure all the bricks are loaded. Regardless it is a bug that should be looked into, It is very easy to recreate.

Recreating the issue:
Build a tall tower with a small brick on top. Set the view distance to minimum. Have someone leave the server when they are standing on top of the structure, then rejoin the server. they will appear to ghost all bricks in visible range. Next destroy the small brick and they will experience the entire build collapse. (brick collisions will still be active server-side)

Its not a very big bug but hopefully it will be looked into.

Its a bit annoying, yes. But if the issue is caused on your server primarily because they are spawning back where they left off, then just disable Script_Player_Persistence.

This is caused by the client thinking it has to display all bricks falling because it hasn't ghosted the support column and therefor thinks the build is floating. It sucks, but you prevent it by making sure the player ghosts the column, or by not killing bricks

I've had this happen to me several times but I didn't think much about it.