[X] I have searched the existing issues and not found ones relating to my problem.
Version
0.5.7
What proxy/server software are you seeing this issue on?
Velocity
What proxy software version are you using?
3.4.0-SNAPSHOT-450
Current Behaviour
Embedded Discord messages that have the timestamp enabled will send a message using the timestamp saved by the EpochHelper of when the plugin starts up.
I believe this is due to the EpochHelper only returning the epochCache value saved on plugin startup and never being updated after that.
Expected Behaviour
The timestamp in the message should be the same as when the event happens.
Steps to Reproduce
Set up a proxy server with Velocity (3.4.0-SNAPSHOT-450) and SimpleProxyChat (0.5.7)
Set up any compatible Minecraft server (this issue was found in 1.21.1 and 1.21.3)
Set up Discord configurations in SimpleProxyChat
Start the proxy server and Minecraft server.
Watch the timestamps of the server events: player joins/leaves network and notice that the timestamp will always be the same.
Are you certain this is a bug report?
[X] I am certain this is a bug report, and not a feature request, improvement request, or a security vulnerability.
Is there an existing issue for this?
Version
0.5.7
What proxy/server software are you seeing this issue on?
Velocity
What proxy software version are you using?
3.4.0-SNAPSHOT-450
Current Behaviour
Embedded Discord messages that have the timestamp enabled will send a message using the timestamp saved by the EpochHelper of when the plugin starts up.
I believe this is due to the EpochHelper only returning the epochCache value saved on plugin startup and never being updated after that.
Expected Behaviour
The timestamp in the message should be the same as when the event happens.
Steps to Reproduce
Are you certain this is a bug report?