You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the docs, it says that room:Update() is useless, but it isn't useless.
Take the case of spawning a trapdoor where a pit already exists.
If you simply remove the pit and try to spawn a trapdoor, the pit will be successfully removed, but the trapdoor will not appear.
The solution is to remove the pit, call room:Update(), and then spawn the trapdoor.
Thus, I think that the docs should recommend that it is best practice to always call room:Update() after removing any grid entity. This recommendation should appear on both the section for room:Update() and room:RemoveGridEntity().
Separately, please link to this issue in the documentation for room:Update().
The text was updated successfully, but these errors were encountered:
In the docs, it says that
room:Update()
is useless, but it isn't useless.room:Update()
, and then spawn the trapdoor.Thus, I think that the docs should recommend that it is best practice to always call
room:Update()
after removing any grid entity. This recommendation should appear on both the section forroom:Update()
androom:RemoveGridEntity()
.Separately, please link to this issue in the documentation for
room:Update()
.The text was updated successfully, but these errors were encountered: