Terrain methods suddenly error from not being aligned to grid

[filiptibell]

We started seeing these errors pop up in client analytics approx. 7 hours ago:

Region has to be aligned to the grid (use Region3:ExpandToGrid)

We are definitely rounding to grid size already and this code has been working fine for many months.
Our game Tropical Resort Tycoon 2, which consists of islands with water around them to travel on, no longer has any water at all. Whatever flag was flipped for this - please revert it since it is completely breaking our game.

---

EDIT

After some investigation the regions are most definitely aligned to the grid, and are not empty or otherwise abnormal in any way. Here’s an example:

And calling Region3:ExpandToGrid actually does fix this even though we guarantee all our regions to be aligned in previous parts of our code. Does Region3 now keep some internal state as to whether ExpandToGrid has been called or not ???

[Exodation]

This odd error has also affected my game. It completely broke some features i had like custom explosives. I have also not published changes for a whole week so this seems like a roblox issue.

Example of a code that will throw out the error:

local reg = Region3.new(Vector3.one, Vector3.new(4,4,4))
reg:ExpandToGrid(4)
workspace.Terrain:ReplaceMaterial(reg,4, Enum.Material.Sandstone, Enum.Material.Air) 

I was messing around to try to fix this, and somehow, this seems to work:

local reg = Region3.new(Vector3.one, Vector3.new(4,4,4)) 
workspace.Terrain:ReplaceMaterial(reg:ExpandToGrid(4),4, Enum.Material.Sandstone, Enum.Material.Air)

[heedicalking]

There are other things this recent update broke as well. Something with Z layering/LOD is causing flickering. Getting real sick of these unannounced backend changes causing hidden errors across games

[AlienDai (Alien)]

This issue has also affected my game completely breaking it for a day. We would really appreciate it if Roblox notified us before releasing these kinds of changes.

[neutrinostack]

Thank you for quickly reporting the issue.
We reverted the change that was causing the issue. That should not happen anymore after you restart your experience.