A recent change as of yesterday (approx. 15 hours ago) - an internal flag (sent to the team privately) was flipped in relation to humanoid friction changes.
This particular flag is causing issues in games with humanoid movement - as an example, a game called Islands - our NPCs are not moving at all anymore. I’ve also asked around and it’s happening in other games such as Bedwars with the NPCs as well.
Can you update your Rojo version to latest and try again, the release 3 days ago should be compatible with the Scale dependent stuff we’re releasing: Releases · rojo-rbx/rojo · GitHub
There was unfortunately a long draught of Rojo releases which caused this and will be causing some further friction before developers update to this latest release.
Details for posterity: The old rojo version doesn’t know anything about scale, so since scale is a float, it assumes a default of zero for the scale of old models in the case where you mix both new and old input rbxm files in the Rojo build. As you can imagine, various pieces of code we’re releasing now that depend on Scale don’t play nicely with that zero scale. The updated version correctly applies a default scale of 1.
Apologies for the late response, had to check if Uplift had a up-to-date version (which they do) - since mainline Rojo still lacks support for Font - doing this it does appear to have fixed the issues; however. So I appreciate your help.
Yeah totally understandable - really appreciate the explanation about it. Makes a lot of sense.
I don’t think there was any real announcement or mention of humanoid friction changes or it relying on the new scaling feature, I think if this was mentioned it could have help a lot more in future as well to make it easier to pin this issue down w/out resorting to fflag hunting.
For future reference don’t worry about tracking things down to the flag change before posting, that’s our job! Certainly appreciated when you do, but don’t feel obliged to hold back the bug report until you’ve investigated so deeply, you can just add that information once you have it or close the bug report if it turns out to be your own code’s fault.
If you see something break and think it’s probably our fault it’s actually better for us if you fire off a bug report as soon as possible: The engineer who flipped the flag will be on the lookout for such bug reports. They’ll likely immediately be able to recognize that your problem is related and advise (if intentional change) or revert the flag (if unintentional).