Could not register an instance for fr.neatmonster.nocheatplus.components.entity.IEntityAccessLastPositionAndLook

[molor]

Full output of /ncp version

[14:36:06] »Version information«
[14:36:06] Server:
[14:36:06] git-Paper-133 ~MC: 1.17.1~
[14:36:06] Detected: 1.17.1
[14:36:06] NoCheatPlus:
[14:36:06] Plugin: 3.17-SNAPSHOT-Updated-b105
[14:36:06] MCAccess: 1.13-1.17|? / Bukkit-API
[14:36:06] Features:
[14:36:06] blocks: BlocksMC1_4, BlocksMC1_5, BlocksMC1_6_1, BlocksMC1_7_2, BlocksMC1_8, BlocksMC1_9, BlocksMC1_10, BlocksMC1_11, BlocksMC1_12, BlocksMC1_13, BlocksMC1_14, BlocksMC1_15, BlocksMC1_16, BlocksMC1_17, MCAccessBukkitModern
[14:36:06] checks: FastConsume, Gutenberg, HotFixFallingBlockPortalEnter, AttackFrequency, FlyingFrequency, KeepAliveFrequency
[14:36:06] defaults: pvpKnockBackVelocity
[14:36:06] packet-listeners: UseEntityAdapter, MovingFlying, OutgoingPosition, KeepAliveAdapter, SoundDistance, WrongTurnAdapter, NoSlow, Fight
[14:36:06] Hooks:
ViolationFrequency~NCP~ 1.0
[14:36:06] »Related Plugins«
[14:36:06] ProtocolLib v4.7.0

Describe the issue

[14:34:22] [ProtocolLib] [PacketFilterManager] [NoCheatPlus] Unsupported client packet in current Minecraft version: FLYING[PLAY, CLIENT, 254, classNames: [net.minecraft.network.protocol.game.PacketPlayInFlying, net.minecraft.network.protocol.game.ServerboundFlyingPacket, net.minecraft.network.play.client.CPacketPlayer] (unregistered)]

How to reproduce the issue

Start the server.

Extra links/Videos (Including debug logs)

None

Any possible config options changed or plugins that may cause interference?

None

[MarkElf]

Would this work? https://github.com/MelonHell/NoCheatPlus/commit/5dd675044a2f8c2f69dd145d6c85a485a1678a94

[molor]

It seems that yes, but I can't check that now

[molor]

Another problem (?) in post-enable

[14:37:28] [NoCheatPlus] Could not register an instance for: fr.neatmonster.nocheatplus.components.entity.IEntityAccessLastPositionAndLook

[Lysandr0]

Would this work? MelonHell@5dd6750

Implemented, should be fine now.

[molor]

Tested, now only the warning in the title occurs

[xaw3ep]

Should be fixed in b107