I know that Skript is still in beta and those are still early builds for paper 1.17 but just so you known having an "on packet event" followed by any packet print a stack trace (the Skript severe error thingy which you can find here https://pastebin.com/fC6xvZtX)
Running paper 1.17 66, ProtocolLib 4.7.0-Snapshot-b526, Skript 2.6-beta1, on a blank server (only with skript-reflect but no scripts uses it) and Java 16.0.1 on Windows 10
To reproduce simply put an on packet event in any script and it should do the same. I didn't test if it's because of ProtocolLib,Skript 2.6-b1 or 1.17 though
I know that Skript is still in beta and those are still early builds for paper 1.17 but just so you known having an "on packet event" followed by any packet print a stack trace (the Skript severe error thingy which you can find here https://pastebin.com/fC6xvZtX)
Running paper 1.17 66, ProtocolLib 4.7.0-Snapshot-b526, Skript 2.6-beta1, on a blank server (only with skript-reflect but no scripts uses it) and Java 16.0.1 on Windows 10
To reproduce simply put an on packet event in any script and it should do the same. I didn't test if it's because of ProtocolLib,Skript 2.6-b1 or 1.17 though