Add ProtocolChangedEvent to the API

[Outfluencer]

ProtocolChangedEvent is called when the encode or decode protocol of any Connection is changed.

We now can detect if a 1.20.4 player is changing protocol to config or play via API, but it is also possible to detect if the InitialHandler changes protocol from Handshake to Status or Login

[Outfluencer]

Bump

[Outfluencer]

version notice for what?

[Janmm14]

Uhm I was wrong, I only thought this was related to 1.20.2+ somehow

[Janmm14]

If the connection of the event is a server, I am quite sure it is impossible by API to find out to which user the server connection belongs to.

[Outfluencer]

If the connection of the event is a server, I am quite sure it is impossible by API to find out to which user the server connection belongs to.

thats right

[Outfluencer]

If the connection of the event is a server, I am quite sure it is impossible by API to find out to which user the server connection belongs to.

i'll add api for that

[Outfluencer]

do you think we could just add
ProxiedPlayer getPlayer();

in Server.java?

the current docs would need a change,
in the current api design we would need to do this to get the Player of a Server

ProxiedPlayer player = server.getInfo().getPlayers().stream().filter( ( p ) -> ( p.getServer() == server ) ).findAny().get();

[Janmm14]

do you think we could just add ProxiedPlayer getPlayer();

in Server.java?

the current docs would need a change, in the current api design we would need to do this to get the Player of a Server

ProxiedPlayer player = server.getInfo().getPlayers().stream().filter( ( p ) -> ( p.getServer() == server ) ).findAny().get();

Sounds like a valid option to me, could maybe also help certain applications of Server<->Bungee plugin messages.
I would name the method something like getConnectedPlayer() tho, to not get confused too easily as to what the class represents.

[Outfluencer]

I don't like getConnectedPlayer as the player can connect to another server and is not connected anymore, but the api would return the player, also returning null if the player is disconnected seems like a bad idea for me