of     1   

Savi_ooo
#228340139Saturday, December 02, 2017 7:21 PM GMT

how2 reduce? ~ 𝓢𝖆𝖛𝖎
Aliics
#228340472Saturday, December 02, 2017 7:26 PM GMT

Remove as many memory-eating things you can from loops to optimize how you use resources. You can only reduce latency so much because the NPC will be more on the client-side. Also try setting the NPC's NetworkOwner to the person closest / the person it's targeting? I'm not certain of this one because they added this function while I was on a fairly long hiatus.
Savi_ooo
#228340550Saturday, December 02, 2017 7:28 PM GMT

asd ~ 𝓢𝖆𝖛𝖎
Savi_ooo
#228340602Saturday, December 02, 2017 7:29 PM GMT

Oh, gotcha thanks, I'll try those. ~ 𝓢𝖆𝖛𝖎
Savi_ooo
#228340692Saturday, December 02, 2017 7:31 PM GMT

Wait but no what I meant was the FPS lag, I've asked multiple people to join me and test the lag and it seems to lag for them as well :c ~ 𝓢𝖆𝖛𝖎
BJCarpenter
#228344326Saturday, December 02, 2017 8:45 PM GMT

A properly coded NPC will not lag, unless you have hundreds of them. If you do: In your FindNearestTorso do not search the entire workspace. Just search the Players for the closest Player. And change the wait() in the MoveTo part to wait(.5) or wait(1). The NPC does not need to recalculate his direction every .03 of a second (wait()).

    of     1