Some players of our game are experiencing an issue in which the Nextbot AI that chases them are seemingly “invisible”. When we did our investigation into this issue it’s seemingly because the “Client Nextbot” (which contains the visual of a Nextbot) that is welded to the “Server” AI object is somehow breaking. The code and game have been untouched for over a month practically, however this issue started around July 31st which is a Wednesday. As far as we are aware Roblox pushes updates on Wednesdays so we were wondering if there was anything touched regarding Welds that could help us debug this issue further. An important thing to clarify is that this is an inconsistent issue that is difficult to replicate because it is only happening to some players.
Are there any other physics constraints applied to the bot? We recently rolled out a change relating to LinearVelocity, AlignOrientation, AlignPosition and AngularVelocity. Do you use any of these constraints? Thanks.
For the time being, you can set Workspace. MoverConstraintRootBehavior to Disabled to recover the old behavior. If you would like to send me a model, I can help you work through any issues caused by the change. As the announcement post explains, this change fixes several long standing issues with mover constraints so its important that we eventually get things working with the new property enabled. Thanks.