How laggy are humanoid NPCs? How many is a lot?

[Uraeust]

Hi. I am working on a simple player chasing NPC and first I gave a shot to non humanoid version as I heard humanoids were not very efficient lag-wise, but I had hard time with movement and jump systems, they did not feel natural at all. So now I am willing to try humanoid NPCs just to be able to use MoveTo(), but I am worried about lag.

As long as the AI core script is decently optimized, how many humanoid NPCs can I use at the same time without having serious performance issues? How would it compare against non humanoid NPCs? Does anybody have any guess on numbers?

[Nube762]

I guess it depends, but I’ve seen people have around 20 or 30 NPCs easily with raycasting stuff in their code and no other optimizations. Like Y3llow Mustang, the youtuber that creates a lot of cool NPCs and makes them fight eachother.

But you could optimize them even more, it has been discussed in other posts tho like these ones:

Are Humanoids laggy?

I want to make a large, open world game. It will have many objects containing Humanoids, such as enemies and various interactive objects. My current understanding includes: Too many humanoid models will cause the game to lag, as too many moving parts on the client takes up memory. Too many humanoids containing scripts will cause lag, as that’s a lot of running scripts. Too many moving parts in the Workspace causes the server’s physics to lag. My questions are the following: Will a lot of …

How to Optimize Humanoids

This exactly, thanks for writing! Building a custom-humanoid from scratch not only eliminates useful features (properties, events, inbuilt functions, even clothing), but can consume a significant amount of time to develop. Custom-humanoids can be worth-while and evidently do provide performance benefits, but for the general population of developers optimising the existing humanoid is considerably the best approach. Tldr and additional tricks Disable all HumanoidStates. These consume memory …