My setup

Backend

SignedVelocity 1.2.2
Purpur Latest 1.20.4
FreedomChat 1.5.2 (can reproduce without)

Proxy

SignedVelocity 1.2.2
Velocity 3.3.0-SNAPSHOT (git-9450e660-b310)

How to reproduce the bug

1. Add a plugin that cancels chat on velocity. For example, LibertyBans.
2. Add DiscordSRV for example in your backend
3. Mute yourself, and send a chat message. The message will not be shown in chat however you will be able to see it on discord (note: DiscordSRV does check if the event is cancelled)

Hello,
I've enable an option in DiscordSRV for the AsyncChatEvent, but when i restart my server, SignedVelocity doesn't detect this.

Maybe the code for this here.

When a user sends a message to the chat, nothing happens, I use the plugin on the proxy and on the backend server (Velocity + Purpur).

Hello there, i am currently using a plugin that is dependent on SignedVelocity. I'm encountering an issue that is not present when i used to use UnSignedVelocity, that causes all chat messages to be duplicated twice on my servers.

My environment :
HuskChat 2.7.1
SignedVelocity 1.1.0
Velocity Build 276

I have talked with the developer of HuskChat and made sure this was not a configuration issue on my side.

Hey would signedvelocity work for me if I'm running velocity proxy, 1.20.1 hub server and 1.12.2 prison server? I have installed the plugin with vpacketevents on my proxy & on the hub. but it seems like there is no version for older mc servers would I be fine with running it or would newer players connecting to my prison eventually get kicked?

I have an error for this piece of code:
commandManager.executeAsync(player,"/tp 20 20 20");

Error:
[12:41:48 ERROR]: Couldn't pass CommandExecuteEvent to signedvelocity java.util.NoSuchElementException: No value present at java.util.Optional.orElseThrow(Optional.java:377) ~[?:?] at io.github._4drian3d.signedvelocity.velocity.listener.PlayerCommandListener.lambda$executeAsync$0(PlayerCommandListener.java:40) ~[?:?] at com.velocitypowered.api.event.EventTask$2.execute(EventTask.java:91) ~[velocity.jar:3.2.0-SNAPSHOT (git-19abb909-b265)] at com.velocitypowered.proxy.event.VelocityEventManager$ContinuationTask.execute(VelocityEventManager.java:545) ~[velocity.jar:3.2.0-SNAPSHOT (git-19abb909-b265)] at com.velocitypowered.proxy.event.VelocityEventManager.fire(VelocityEventManager.java:604) ~[velocity.jar:3.2.0-SNAPSHOT (git-19abb909-b265)] at com.velocitypowered.proxy.event.VelocityEventManager.lambda$fire$5(VelocityEventManager.java:478) ~[velocity.jar:3.2.0-SNAPSHOT (git-19abb909-b265)] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?] at java.lang.Thread.run(Thread.java:1623) [?:?]

In the pre-existing Velocity API, canceling a chat event prevents it from being sent to the backend servers. Chat canceled on the proxy is therefore invisible to Bukkit plugins. However, using SignedVelocity fundamentally alters this behavior by forwarding all chat events, even if canceled, to the backend servers. While this makes the plugin work, it is a behavioral change from the prior status quo, and leaks the abstraction SignedVelocity employs to shore up chat handling in a post-1.19.4 world.

This can be confusing for users who are acquainted to the previous behavior. For example, it may cause certain proxy plugin features to stop working when switching from pre-1.19.4 to post-1.19.4 with SignedVelocity, since the behavior of chat events is now different.

Most of the time, however, uncanceling a canceled chat event doesn't make sense. Fortunately, SignedVelocity is in the unique position of knowing exactly when a chat event was canceled by the proxy but uncanceled by the backend server. I therefore propose SignedVelocity add another listener on EventPriority.HIGHEST to log a brief warning if behavior has fundamentally changed as a result of a backend plugin uncanceling the event. It should be relatively straightforward given you already have a queue of chat data, so no additional data structure overhead would be incurred. If you want to avoid annoying users, the brief warning can be one-time, or it can be disabled by a config option. However, I argue it should be enabled by default, because it presents a behavioral change from the typical Velocity API proxy plugins are used to.

Hi,

Since I did update from b327 to b330 of Velocity proxy, this plugin is not compatible anymore :

This is what I can get in the server log :

[11:45:37 INFO] [signedvelocity]: Starting SignedVelocity
[11:45:37 ERROR]: Couldn't pass ProxyInitializeEvent to signedvelocity
com.google.inject.ProvisionException: Unable to provision, see the following errors:

1. [Guice/ErrorInjectingConstructor]: NoClassDefFoundError: com/velocitypowered/proxy/protocol/packet/ServerData
   at VPacketEventsAdapter.(VPacketEventsAdapter.java:12)
   while locating VPacketEventsAdapter
   Learn more:
   https://github.com/google/guice/wiki/ERROR_INJECTING_CONSTRUCTOR
   1 error
   ======================
   Full classname legend:
   ======================
   VPacketEventsAdapter: "io.github._4drian3d.signedvelocity.velocity.packet.VPacketEventsAdapter"
   ========================
   End of classname legend:
   ========================
   at com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:251) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1151) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1186) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at io.github._4drian3d.signedvelocity.velocity.packet.PacketAdapter.register(PacketAdapter.java:19) ~[?:?]
   at io.github._4drian3d.signedvelocity.velocity.SignedVelocity.onProxyInitialization(SignedVelocity.java:48) ~[?:?]
   at io.github._4drian3d.signedvelocity.velocity.Lmbda$8.execute(Unknown Source) ~[?:?]
   at com.velocitypowered.proxy.event.UntargetedEventHandler$VoidHandler.lambda$buildHandler$0(UntargetedEventHandler.java:56) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.velocitypowered.proxy.event.VelocityEventManager.fire(VelocityEventManager.java:597) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.velocitypowered.proxy.event.VelocityEventManager.lambda$fire$5(VelocityEventManager.java:478) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
   at java.lang.Thread.run(Thread.java:833) [?:?]
   Caused by: java.lang.NoClassDefFoundError: com/velocitypowered/proxy/protocol/packet/ServerData
   at io.github._4drian3d.signedvelocity.velocity.packet.VPacketEventsAdapter.(VPacketEventsAdapter.java:17) ~[?:?]
   at io.github._4drian3d.signedvelocity.velocity.packet.VPacketEventsAdapter$$FastClassByGuice$$175ded2.GUICE$TRAMPOLINE() ~[?:?]
   at io.github._4drian3d.signedvelocity.velocity.packet.VPacketEventsAdapter$$FastClassByGuice$$175ded2.apply() ~[?:?]
   at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:82) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:91) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:300) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1148) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   ... 10 more
   Caused by: java.lang.ClassNotFoundException: com.velocitypowered.proxy.protocol.packet.ServerData
   at com.velocitypowered.proxy.plugin.PluginClassLoader.loadClass0(PluginClassLoader.java:87) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.velocitypowered.proxy.plugin.PluginClassLoader.loadClass(PluginClassLoader.java:64) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at java.lang.ClassLoader.loadClass(ClassLoader.java:520) ~[?:?]
   at io.github._4drian3d.signedvelocity.velocity.packet.VPacketEventsAdapter.(VPacketEventsAdapter.java:17) ~[?:?]
   at io.github._4drian3d.signedvelocity.velocity.packet.VPacketEventsAdapter$$FastClassByGuice$$175ded2.GUICE$TRAMPOLINE() ~[?:?]
   at io.github._4drian3d.signedvelocity.velocity.packet.VPacketEventsAdapter$$FastClassByGuice$$175ded2.apply() ~[?:?]
   at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:82) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:91) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:300) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1148) ~[velocity.jar:3.3.0-SNAPSHOT (git-0993ce2f-b330)]
   ... 10 more

If you need someone to test a new release, I'm available to "beta test" it.
Same if you need some more infos, I'm here :P

Edit : Did some more tests :
Compatible until build 328 included.
Start to fail the initialization on build 329 and forward :)

Is this possible? No idea what this would require but just wanted to know if this could even happen?

Hello there,
I am trying to install SignedVelocity on my local network using CloudNet.
The proxy version works just fine, starts without errors and everything, but the PaperMC version always throws this exception:

[25.11 18:51:29.588] INFO: [Hub-1] org.bukkit.plugin.InvalidDescriptionException: Invalid plugin.yml
[25.11 18:51:29.588] INFO: [Hub-1]      at org.bukkit.plugin.java.JavaPluginLoader.getPluginDescription(JavaPluginLoader.java:178) ~[paper-api-1.19.2-R0.1-SNAPSHOT.jar:?]
[25.11 18:51:29.588] INFO: [Hub-1]      at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:155) ~[paper-api-1.19.2-R0.1-SNAPSHOT.jar:?]
[25.11 18:51:29.588] INFO: [Hub-1]      at org.bukkit.craftbukkit.v1_19_R1.CraftServer.loadPlugins(CraftServer.java:423) ~[paper-1.19.2.jar:git-Paper-307]
[25.11 18:51:29.588] INFO: [Hub-1]      at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:278) ~[paper-1.19.2.jar:git-Paper-307]
[25.11 18:51:29.588] INFO: [Hub-1]      at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1100) ~[paper-1.19.2.jar:git-Paper-307]
[25.11 18:51:29.588] INFO: [Hub-1]      at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:305) ~[paper-1.19.2.jar:git-Paper-307]
[25.11 18:51:29.588] INFO: [Hub-1]      at java.lang.Thread.run(Thread.java:1583) ~[?:?]
[25.11 18:51:29.588] INFO: [Hub-1] Caused by: java.io.FileNotFoundException: Jar does not contain plugin.yml
[25.11 18:51:29.588] INFO: [Hub-1]      ... 7 more

I am using the latest SignedVelocity version (Paper-1.2.1)
Server Version: 1.19.2
/ver-Output: This server is running Paper version git-Paper-307 (MC: 1.19.2) (Implementing API version 1.19.2-R0.1-SNAPSHOT) (Git: 476ef25)

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Package lookup failures

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update plugin idea-ext to v1.1.8
• chore(deps): update runvelocity to v2.2.4 (xyz.jpenilla.run-paper, xyz.jpenilla.run-velocity)
• fix(deps): update dependency org.slf4j:slf4j-api to v2.0.13
• chore(deps): update dependency gradle to v8.7
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• fix(deps): update dependency org.spongepowered:spongeapi to v10

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

https://spark.lucko.me/Ryze54w182

Plugins like MyCommand and DeluxeMenus (plus potentially others) do not bode well with SignedVelocity's command listener. Not exactly sure what to recommend here; however, I'm assuming this may have been an accidental oversight or unexpected occurrence.