Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An event even before protocol version is checked #1374

Open
scrayos opened this issue Jul 6, 2024 · 2 comments
Open

An event even before protocol version is checked #1374

scrayos opened this issue Jul 6, 2024 · 2 comments
Labels
type: feature New feature or request

Comments

@scrayos
Copy link
Contributor

scrayos commented Jul 6, 2024

Requested Feature

I'd like to have an event that is even triggered before the protocol version check here:

Why is this needed?

So that incompatibilities in the protocol version can be checked within the plugin and handled accordingly. Currently, it is not possible to modify the message that is sent on a too recent protocol version within plugins. I'd like to specify an allowed range of versions and display a unified message on either too new versions or too old versions.

Alternative Solutions

Optionally, the check could be moved below the HandshakeEvent.

Additional Information

No response

@scrayos scrayos added the type: feature New feature or request label Jul 6, 2024
@Nacioszeczek
Copy link
Member

Nacioszeczek commented Jul 6, 2024

You can modify the message by overriding it in .properties files inside lang/.
Unless you also want to modify the message based on whether the client is too old or too new - which still wouldn't warrant a new event - I'm going to close it.

@Nacioszeczek Nacioszeczek closed this as not planned Won't fix, can't repro, duplicate, stale Jul 6, 2024
@Nacioszeczek Nacioszeczek added the resolution: won't fix This will not be worked on label Jul 6, 2024
@scrayos
Copy link
Contributor Author

scrayos commented Jul 6, 2024

You can modify the message by overriding it in .properties files inside lang/. Unless you also want to modify the message based on whether the client is too old or too new - which still wouldn't warrant a new event - I'm going to close it.

@Nacioszeczek The advantage of an event would be that more dynamic solutions would be possible. We would be able to track those connection attempts with Prometheus (to see the demand), we could display different messages based on the specific version. We could (theoretically) circumvent the IP limiter for certain, authorized IP ranges and many additional things.

Just modifying the language bundle is not flexible enough, in my opinion.

@Nacioszeczek Nacioszeczek reopened this Jul 7, 2024
@Nacioszeczek Nacioszeczek removed the resolution: won't fix This will not be worked on label Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants