For example, when players A and B are talking to NPC M at the same time, player A’s client sees that NPC M is facing them and makes NPC move along a pre-set path. But for player B, NPC is facing them and still in place. Now my server is set so that the NPC will only look at the first locked player until that player leaves the field of view. But this can make it look strange to other players.
#(maidang) How can different players get different NPC data?
21 messages · Page 1 of 1 (latest)
(maidang) How can different players get different NPC data?
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>
Yes, this is implemented but needs some work for npcs that are pathfinding
That is tracked in another thread
/npc lookclose —perplayer true
Needs protocollib installed
Thread Closing Reminder
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@vital echo
Thank you, I tried using this command and it had some effect, but there are still some problems. Suppose the NPC has already locked onto player A, and then player B joins. For player A, everything appears normal, but for player B who joined later, it will twitch, like this.
Yes, I think there’s a packet that isn’t being overridden
Working on it
But as I say that is tracked in a different thread
Thank you. Actually, I don't really understand the content of this section (), but it can achieve better results. If not, I will use it first ()
Anyway, thank you very much!
Thread Closing Reminder
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@vital echo
I'm still not very good at it. Can anyone provide a detailed method