Humanoid:ChangeState() not working on NPC

Help and Feedback Scripting Support
1

Why can I not change the state of the NPC’s Humanoid?

Server-side code:

self.Humanoid:SetStateEnabled(Enum.HumanoidStateType.Running, false)
self.Humanoid:ChangeState(property)

task.spawn(function()
	print(property, self.Humanoid:GetState(), self.Humanoid.Parent.PrimaryPart:GetNetworkOwner())
end)

Output:

Enum.HumanoidStateType.Physics Enum.HumanoidStateType.Running nil
2 Likes
2

If you’re changing the humanoid state of a unanchored character, it has to change.
If it’s a anchored character, you cannot change its state. It will always default to FallingDown.

The core issue is that you’re rushing with your prints, if you replace task.spawn with task.delay, you will notice a difference as to what it outputs.

task.delay(0, function()
	print(property, self.Humanoid:GetState(), self.Humanoid.Parent.PrimaryPart:GetNetworkOwner())
end)

or if you dont want to yield, create a connection to the StateChanged signal.

self.Humanoid.StateChanged:Connect(function(oldState, newState)
	print("Old humanoid state was:", oldState, "new is:", newState) -- optional
	print(property, self.Humanoid:GetState(), self.Humanoid.Parent.PrimaryPart:GetNetworkOwner())
end)

Hope this helped.

3

You’re right, the humanoid state was changed, which can be observed with the delay

But when I change the NPC’s NetworkOwner to a player, it flips back automatically to Running

1 Like
4

The behavior when you switch the NetworkOwner to a client is a bit different, because you’re using a server-script, the moment you switch it over to a client, the client thinks that the NPC is at older state only if the client hasnt noticed the new state in time.

The likely reason is something related to how server tries to replicate changes made so other clients basically notice and see it, the moment you change the ownership from server to a client, now the client blindly trusts it’s own state instead of what the server said right after setting the ownership, so it cancels out that state change the server wanted to operate before changing the ownership.

And so, if the client doesnt replicate that wanted state change in time, you get these issues.

Putting a delay and changing the state of the humanoid first to Physics, waiting a player’s ping amount of seconds (GetNetworkPing) multiplied by 2 and then switching the NetworkOwnership to that client is the only close fix, however if the client’s ping is up to 5000ms+ it would still cause inaccuracy.

The only thing you could really do as far as i know, is:

  • Change the ownership very late, basically to let the client acknowledge the state change first.
  • Use remote events
  • Switch the script context to client (although you wont be able to set the network ownership and you’d need to exclude even more states)
  • Or dont switch ownership at all (only if you dont need to rely on what a client thinks)
1 Like