#(RalphTC) Npc yaw not finite

41 messages · Page 1 of 1 (latest)

deft wadi
#

See my console

cunning geodeBOT
#

(RalphTC) Npc yaw not finite

#

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>

deft wadi
#

Can you look at my console

trail ocean
#

!logs

gleaming zealotBOT
# trail ocean !logs
Info: logs

Please post your full latest log file.

Background Info: One of the most helpful tools to identifying the source of a problem is your server logs file! Logs contain all sorts of important information like server and plugin versions, any error messages, and a lot more important information (More Info).

How To: Your log can be found in the logs folder within your server folder. The most recent log is a text file labeled latest.log. To get help using these logs, please open that file in a text editor and copy all of the text, then open https://paste.denizenscript.com/New/Log and paste the text into the box on the page. Then click "Submit" and copy the URL and paste that back into this channel.

Please do not upload the file to Discord or to other pastebin services, use the log pastebin linked above.

trail ocean
#

@deft wadi

deft wadi
nocturne wraith
#

we need the full file

#

not just the error of it

deft wadi
nocturne wraith
#

!restartlog

gleaming zealotBOT
# nocturne wraith !restartlog
Info: restartlog

If you're having trouble posting your log file (!logs) or you posted a log but it's missing information, you might just need a restart!

What To Do: Restart your server, replicate the issue, and then Paste your logs/latest.log file right after.

Why: sometimes logs contain a lot of unrelated output if the server's been running too long which makes them unable to paste properly. Also, every day at exactly midnight minecraft servers do a log rotation, which basically just means the latest.log no longer contains the startup section of log output, which is often the most important section of the log!

deft wadi
nocturne wraith
gleaming zealotBOT
# nocturne wraith !checklog https://paste.denizenscript.com/View/106575
Server Version

Paper version git-Paper-411 (MC: 1.17.1)-- (Current build :white_check_mark:)

Plugin Version(s)

Citizens v2.0.30-SNAPSHOT (build 2828) -- (:warning:Outdated build, behind by 118)

Checked For

@nocturne wraith

Other Noteworthy Plugin(s)

WorldGuard v7.0.3;5407315, ProtocolLib v4.8.0

Suspicious Plugin(s)

SkinsRestorer v14.2.5 :triangular_flag_on_post: (Offline skins fixer plugin)

Possibly Relevant Plugin(s)

ViaVersion v4.5.1 - Mixed client vs server versions can sometimes cause packet-related issues.
Multiverse-Core v4.3.1-b861 - Multi-world configuration plugins may affect NPCs in unexpected ways.
GSit v[5.2.0.1] - 'Sit on other players' or 'sit on mobs' plugins sometimes allow players to sit on NPCs.

Potentially Bad Line(s)

[11:46:06] [Server thread/ERROR]: Ambiguous plugin name 'ViaVersion' for files 'plugins/ViaVersion-4.5.1.jar' and 'plugins/ViaVersion-v4.5.1-SNAPSHOT-b663.jar' in 'plugins' :warning: Log contains error messages.

nocturne wraith
#

Does that issue only happens with player mirror npcs?

#

Should also give Citizens an update

deft wadi
#

Yes, If I use playermirror

nocturne wraith
#

Seems like an issue with player mirror then

deft wadi
#

But, Do I not have the latest update?

#

Of citizens

nocturne wraith
#

No you're 118 builds behind

#

!update citizens

gleaming zealotBOT
deft wadi
#

Okay, I will update the plugin

#

maybe then is fixed?

deft wadi
#

They forget the yaw

#

as in finite

jade idol
#

if PlayerMirror is sending NaNs to Citizens, you should contact the PlayerMirror dev about that

#

likely they can fix it on their end, or if not, the dev can come here and talk to us about and we can solve it together

gleaming ventureBOT
#
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.)

#

@deft wadi