#(0TickPingo) weird exception on server start 1.20.4

22 messages · Page 1 of 1 (latest)

stray willow
pallid nightBOT
#

(0TickPingo) weird exception on server start 1.20.4

pallid nightBOT
#

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.

stray willow
neat emberBOT
# stray willow !checklog https://paste.denizenscript.com/View/118953
Server Version

Paper version git-Paper-346 (MC: 1.20.4)-- (Current build :white_check_mark:)

Plugin Version(s)

Citizens v2.0.33-SNAPSHOT (build 3293) -- (Current build :white_check_mark:)
Denizen v1.3.0-SNAPSHOT (build 6965-DEV) -- (Current build :white_check_mark:)
Depenizen v2.1.0 (build 850) -- (Current build :white_check_mark:)
dDiscordBot v0.7 (build 295) -- (Current build :white_check_mark:)

Checked For

@stray willow

Java Version

17.0.9 :white_check_mark:

Other Noteworthy Plugin(s)

ProtocolLib v5.2.0-SNAPSHOT-679

Possibly Relevant Plugin(s)

ViaVersion v4.9.2 - Mixed client vs server versions can sometimes cause packet-related issues.

Potentially Bad Line(s)

[16:18:27] [Server thread/ERROR]: Could not pass event ScriptReloadEvent to Denizen v1.3.0-SNAPSHOT (build 6965-DEV) :warning: Log contains error messages.

stray willow
#

oh yeah and half my scripts arent scripting

#

update, i think its just the command scripts that dont function

#

which would make sense looking at the stacktrace

bold forge
stray willow
#

wil try rn

#

yeah no exception with 6958

#

lemme try my commands

#

yup commands work

bold forge
#

Probably borked by 6959

dense mortarBOT
#
Changed to Bug

Thread is now a Bug thread. This indicates a core code bug that a developer must resolved, not an error message or other support topic. Please do not misuse the Bug label. Use </helpthread:1028674284870180883> to switch the thread back to a normal help thread if you are not 100% confident it is a code bug.

solar marsh
stray willow
#

ok

solar marsh
#

Should be fixed ref #commit-log message

dense mortarBOT
#
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.)

#

@stray willow