You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Velocity version: 3.3.0-SNAPSHOT-build410
FastMOTD version: 1.0.7
Use default configuration file (with check for updates turned off)
I am pleased to learn that the FastMotd plugin has been updated to address several previous issues. I have installed the plugin into my server's plugin folder and attempted to run it. However, upon pinging the server using Minecraft, I encountered a problem where the server continuously displayed 'pinging' and eventually failed to respond.
As shown in the picture:
I have identified a compatibility issue with the plugin: when it is installed alongside PacketEvents, an exception is thrown. Removing PacketEvents allows the server to be detected normally.
I believe this to be a critical bug since many plugins rely on PacketEvents for their functionality. I hope you can address this issue in a future update.
Can you try to reproduce this issue with the latest FastMOTD dev-build and direct-write enabled in the config? After some testing it seems that this issue was fixed. (but via ignoring PacketEvents)
Velocity version: 3.3.0-SNAPSHOT-build410
FastMOTD version: 1.0.7
Use default configuration file (with check for updates turned off)
I am pleased to learn that the FastMotd plugin has been updated to address several previous issues. I have installed the plugin into my server's plugin folder and attempted to run it. However, upon pinging the server using Minecraft, I encountered a problem where the server continuously displayed 'pinging' and eventually failed to respond.
As shown in the picture:
I have identified a compatibility issue with the plugin: when it is installed alongside PacketEvents, an exception is thrown. Removing PacketEvents allows the server to be detected normally.
I believe this to be a critical bug since many plugins rely on PacketEvents for their functionality. I hope you can address this issue in a future update.
This is my log file:
latest.log
The text was updated successfully, but these errors were encountered: