ok I’m going to try, while I also got other NPCs to guide me, and hey about your theme, I put that out of anger that I needed help and the people writing in your theme anyway, be strong.
2 Likes
Let’s see, with this method the loop is not necessary, I think, because MoveTo() gets stuck for that simple reason, if that’s why you think, would it be better to do the HearthBearth and replace the MoveTo()?
2 Likes
No, because runservice ignores waits since it runs every frame. Replace the moveto
1 Like
yes, but when I mean using runservice. I mean override MoveTo()
2 Likes
I don’t quite understand lol. Keep the current loop and replace moveto to PrimaryPart.Position or cframe, which will require you to change point.Position to point.CFrame
Run service is used for specific loops such as physics or renders and don’t support yields
1 Like
please dear friend, MOVETO() is a function that is used to move humanoids fluidly, IF I FOR SOME REASON move the model with that function it will not do it fluidly, it will do it in less than 0.02 seconds, you don’t realize ?
2 Likes
Oh I got it. Sorry lol. Well again, replace moveto to that. It should not yield though, that’s weird but I’ll guess it’s trying to see if it’s clipping or not and replication lag is also screwing it up or something I don’t really know.
1 Like
I can’t replace it because of that, it won’t work the right way, does anyone have a real solution?
Could you show a video of what happens when you replace it?
It’s obvious, Each waypoint has a magnitude of 2, if I use that, it will appear to teleport, please refer to this link which will explain the functions of MoveTo() https://create.roblox.com/docs/reference /engine/classes/Humanoid#MoveTo
Roblox indicates it in such a way and also, updating is necessary, SetPrimaruPartCFrame or as you said Model.PrimaryPart.CFrame It is not something Updated or suitable for that roblox I think PivotTo()
I’m still waiting for a person to help me, a savior, a good programmer
Jesus Christ you really are trying to bash my head in every chance you get? NPC are not moving correctly - #6 by nombreincorrectodepn
Because you are not right, please, I just wanted to help on that issue since it made me angry that you continue to deceive people with the same argument so that you came to a topic without having knowledge about it?
I misunderstood what you said. I’m gonna log off devforum fir now since there’s a crisis currently happening
Someone really help me, I see that many people see the issue but nobody contributes absolutely nothing
please help me, the truth is that I have had this for days and nobody has helped me.
someone come to help me, I keep on going on with this and I can’t find a solution.
listen to one last question before closing the topic, the method provided by the documentation is after 6 seconds of being frozen, therefore it will freeze and then continue, it is something that comes to mind, the thing is that if I do That will stay frozen anyway, just that it won’t stay all the time, it would be practically the same, what do you use to solve it?
The second is that there currently seems to be a problem with Roblox, as working with Vector3 that you have defined yourself in this situation can be almost impossible because the humanoid will not move to the position, but about 5-10 cues away. I had this problem and so I fixed it. I hope this helps! Look, there is the solution, you are useless, hopefully the house will vote for you
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.