(nuttapillar) Citizens using 12% of server thread??

[weary swift]

Hi, my server is lagging terribly, with only about 12TPS, so I did a spark profile, and citizens is using 12% of the server thread, which seems excessive. What can I do about this? https://spark.lucko.me/r5hz8HWdlj

[mortal field]

(nuttapillar) Citizens using 12% of server thread??

[mortal field]

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>

[silver ravine]

Hmm, two things jump out at me immediately

A lot of time spent on trivial tasks like getBukkitEntity, getting the clock time which suggests a poor sampling interval

Your citizens build is outdated, so there’s no real comparison point for me unless you update

[keen belfry]

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.)

@weary swift

[weary swift]

will the latest still work on a 1.19.3 server?

[muted stone]

!patchversions

[proud surge]

Info: patchversions

We support only the latest patch-version of Minecraft for any recent main version (and Mojang, Spigot, Paper, etc. all generally also follow the same rule).

"Patch version" means the last number in a version label, for example in 1.18.2, the main version is 1.18, and the patch version is .2.
So if 1.18.2 is the latest patch version, then 1.18.1, and 1.18(.0) are all outdated patch versions, and therefore are unsupported.

Note that we do still support recent older main versions (such as 1.17 and 1.16) so long as you are on the latest patch-version of those main versions (like 1.17.1 and 1.16.5).

[muted stone]

Is there any reason you can't update?

[weary swift]

Yes, not all plugins have updated to support 1.19.4 yet. One of the plugins I use, does not work on 1.19.4. Also, 1.19.3 is still very recent. why not support it? I thought it was common knowledge that servers don't always update straightaway, as they have to wait for plugins.

so im stuck between some plugins not updating enough, and other plugins dropping support too soon.

[muted stone]

Most plugins already updated, which plugins are blocking you?

[weary swift]

Jukelooper does not support 1.19.4 yet

I was hoping to stick with 1.19.3 until 1.20 releases, and just skip 1.19.4. but didnt realise 1.19.3 would lose support so soon

[muted stone]

Have you tested it? what error did you get? at a glance it looks like an API-only plugin

[weary swift]

I've read the forums for it, and all recent comments/reviews suggest it wont work on 1.19.4. And the community for that plugin has accepted that the dev has gone missing and we're all waiting for an update

It's not a huge deal though. I could just sacrifice that plugin, without too much issue. But IDK if updating will even fix the citizens lag.

[muted stone]

Well, just tossed it into a 1.19.4 server and it seems to startup fine - either way if the developer abandoned it and it isn't maintained anymore it's probably a good idea to try and find an alternative

[muted stone]

Well, it's very possible it will, but even if it doesn't and it's an actual bug that'll be fixed, the latest versions don't support 1.19.3

So will have to update anyway (which is an important thing to do unrelated to Citizens, even Paper themselves doesn't support 1.19.3 in favor of 1.19.4)

[weary swift]

alright, ill cave. I'll sacrifice jukelooper and update.

[plain lynx]

I guess there is a reason why plugin could not be updated anymore:
https://www.youtube.com/watch?v=ZujwT2oKAZw

[silver ravine]

happy to help as always @weary swift

if you're still experiencing issues in 1.19.4, please post a spark log and can take a look

[keen belfry]

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.)

@weary swift

[weary swift]

Yeah i was surprised to see that feature. so i dont need that plugin anymore. but the dev still kinda went missing.

[keen belfry]

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.)

@weary swift

[weary swift]

/reaolved

[keen belfry]

Resolved

Thread closed as resolved.

[weary swift]

/reaolved

[keen belfry]

Thread Reopened

Thread was manually reopened by @weary swift.