#(dr_eslam) Citizen can not enable

7 messages · Page 1 of 1 (latest)

dawn rampartBOT
#

(dr_eslam) Citizen can not enable

#

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.

brazen rivet
sudden oarBOT
# brazen rivet !logcheck https://paste.denizenscript.com/View/128464
Server Version

Paper version 1.21.1-131-ver/1.21.1@84281ce (2024-10-31T17:43:44Z)-- (Current build :white_check_mark:)

Plugin Version(s)

Citizens v2.0.36-SNAPSHOT (build 3637) -- (Current build :white_check_mark:)

Checked For

@brazen rivet

Online/Offline

Offline, but proxied.

Other Noteworthy Plugin(s)

WorldGuard v7.0.12+829a4a4, ProtocolLib v5.3.0

Suspicious Plugin(s)

LoginSecurity v3.3.0 :triangular_flag_on_post: (Offline login authenticator plugin)
SkinsRestorer v15.4.4 :triangular_flag_on_post: (Offline skins fixer plugin)

Problematic Plugin(s)

PvPManager v3.18.26 - :warning: PvPManager is known to cause issues related to Citizens and Sentinel.

Possibly Relevant Plugin(s)

TAB v5.0.1 - This plugin adds Below_Name scoreboards to NPCs.
ViaVersion v5.1.1 - Mixed client vs server versions can sometimes cause packet-related issues.
Multiverse-Core v4.3.14 - Multi-world configuration plugins may affect NPCs in unexpected ways.
GSit v1.11.2 - '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:19143 - 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_R2.boss.CraftBossBar :warning: Log contains error messages.

brazen rivet
#

Lol

deft questBOT
#

@brazen rivet

Thread Close Blocked

Thread was closed either automatically by timeout or by the Discord manual close button. If closing was intentional, please use </resolved:1028673926114594866> or </invalid:1028673926898909185>.