#(centiliter) Plugin not loading up on 1.21.4

15 messages · Page 1 of 1 (latest)

gray finch
#

Hi there, my server is Purpur 1.21.4 and I'm on the latest version of Citizens (2.0.38). The plugin appears red and for some reason did not want to work anymore after updating from 1.21.1 -> 1.21.4

Any ideas?

sage templeBOT
#

(centiliter) Plugin not loading up on 1.21.4

sage templeBOT
#

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.

covert gustBOT
# jaunty orchid !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.

gray finch
jaunty orchid
covert gustBOT
# jaunty orchid !logcheck https://paste.denizenscript.com/View/133685
Server Version

Purpur version 1.21.4-2416-HEAD@51aafbc (2025-04-12T23:37:33Z)

Plugin Version(s)

Citizens v2.0.38-SNAPSHOT (build 3804) -- (Outdated build, behind by 2)

Checked For

@jaunty orchid

Online/Offline

Offline, but proxied.

UUID Version

4 (:white_check_mark: Online)

Other Noteworthy Plugin(s)

WorldGuard v7.0.13+82fdc65, ProtocolLib v5.3.0, Quests v3.15.2-b216e2b

Suspicious Plugin(s)

IPWhitelist v1.16.3 :triangular_flag_on_post: (Offline exploits fixer plugin)

Problematic Plugin(s)

PlugManX v2.4.1 - :warning: Plugin Managers are dangerous and will cause unpredictable issues. Remove it.
CommandNPC v1.9.1 - :warning: NPC Command plugins have never had a valid reason to exist, as there have always been better ways to do that. The modern way is https://wiki.citizensnpcs.co/NPC_Commands.

Possibly Relevant Plugin(s)

TAB v5.2.1 - This plugin adds Below_Name scoreboards to NPCs.
ViaVersion v5.3.2 - Mixed client vs server versions can sometimes cause packet-related issues.
Multiverse-Core v4.3.13 - Multi-world configuration plugins may affect NPCs in unexpected ways.
GSit v2.0.0 - 'Sit on other players' or 'sit on mobs' plugins sometimes allow players to sit on NPCs.

Potentially Bad Line(s)

Starting Minecraft server on 0.0.0.0:25614 - server is offline but has no address bind. This might mean you're using a system level firewall, but if not, it means your proxy is bypassable by hackers. Either enable a system level firewall, or bind your server to localhost in server.properties via server-ip=127.0.0.1.
Caused by: java.lang.ClassNotFoundException: org.bukkit.craftbukkit.v1_21_R4.boss.CraftBossBar :warning: Log contains error messages.

jaunty orchid
#

!patchversion

covert gustBOT
# jaunty orchid !patchversion
Info: patchversion

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.20.6, the main version is 1.20, and the patch version is .6.
So if 1.20.6 is the latest patch version, then 1.20.3, and 1.20(.0) are all outdated patch versions, and therefore are unsupported.

Note that we do still support recent older main versions (such as 1.19 and 1.18) so long as you are on the latest patch-version of those main versions (like 1.19.4 and 1.18.2).

See also CitizensWiki/Supported_versions

jaunty orchid
#

Check #news for last built for 1.21.4

rapid thornBOT
#
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.)

#

@gray finch

gray finch
#

That worked ty