Oh god. Now this is stupid.
Now this, kids, clearly shows a lack of research and experimentation.
What happens when you move something around on the 1/5 stud grid is that you MAY move it off of the 1 stud grid (you didn't in the single part example -__-). Then, when you switch back, the 1 stud grid is aligned to the current position of that part. This is essential. If you want to stick it back on the same grid it was on before, move it into a position where it was on the grid and turn on the 1 stud grid.
In your first example with the building, all you had to do was switch to 1/5 stud grid, move it to fit the corner and switch back to 1 stud so that the 1 stud grid was aligned to the parts on the base. What happened with the brick was an accident. In the 1/5 grid, you just happened to end moving on exactly the previous 1 stud grid.
Without doing this, Roblox absolutely no idea what 'grid' to sync to. It isn't magic and it can't read your mind. All of this is intentional behaviour. Really, there isn't a set grid because this would offset many models in games where the baseplate was slightly moved to start with and all buildings were slightly off. It's all increments, which make perfect sense when you know how to use them.
Plus, if this offset thing is such a worry to you, hack together a simple .lua file to execute in studio to move a model by a certain amount if it gets knocked off by something weird like 0.15 studs. Or even a plugin. It isn't difficult, and if you can make a game like yours, you should be able to do this. |