I enabled a change to the snapping input box today.
If you still remember, could you confirm for me what you saw in the grid snap input box when you checked it and whether snapping was enabled?
As part of the changes I decoupled snapping and grid snap increment where before they were tied together. It’s possible some devs were somehow in a weird state where they had snap increment = 0 and snapping enabled even you should only have been able to get into that state by manually editing the settings file.
If that’s what happened here maybe there’s some other way to get into that state which I didn’t anticipate. I’ll keep my eye on this. If anyone else runs into this could you let me know?
will it be possible to use 0 increment again (or is it intentional)? im also struggling with this same issue, and i really want to continue using 0 increment.
What is your intent with the zero increment? Entering zero now should just disable snapping which is almost identical to the previous behavior (Previously snapping was set to 0.01 stud increment when entering zero).
Had this move bug all day but just assumed since roblox is having other service issues that it was affecting this too. My move snap box was checked and it was on 0 studs. Fixed it the same way YED did.