Change Details

If you have destroyed a forest with setdamage. After the reconnect if you execute ``` hint str (nearestTerrainObjects [player, [], 10, false] select {damage _x >= 1}) ``` You will see that this return nothing, because damage command return 0 instead 1. But the command damage need to return 1 because all trees has fallen. So I think, when you reconnect you receive the data of object that he was "restored" but you don't have the effect of "restored"

If you have destroyed a forest with setdamage. After the reconnect if you execute ``` hint str (nearestTerrainObjects [player, [], 10, false] select {damage _x >= 1}) ``` You will see that this return nothing, because damage command return 0 instead 1. But the command damage need to return 1 because all trees has fallen. So I think, when you reconnect you receive the data of object that he was "restored" but you don't have the effect of "restored". This working fine when setting damage with setdamage on the tree or the wall.

If you have destroyed a forest with setdamage. After the reconnect if you execute ``` hint str (nearestTerrainObjects [player, [], 10, false] select {damage _x >= 1}) ``` You will see that this return nothing, because damage command return 0 instead 1. But the command damage need to return 1 because all trees has fallen. So I think, when you reconnect you receive the data of object that he was "restored" but you don't have the effect of "restored". This working fine when setting damage with setdamage on the tree or the wall.