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
Describe the problem related to your feature request.
It would be nice if NetworkCallbacks::login implementors could send/receive LoginQueryRequestS2c/LoginQueryResponseC2s packets to allow dealing with clientside mods and whatever else
What solution would you like?
The login callback could receive a reference to PacketIo as a parameter. The struct could also have a convenience function for both sending a query and awaiting a response from the client (according to wiki.vg at least it's always supposed to send one back)
What alternative(s) have you considered?
Outside of modifying/replacing default Valence crates, none
Additional context
-
The text was updated successfully, but these errors were encountered:
wiki.vg's article on Packet Channels lists a few mod examples, but I don't know how up to date they are, or how many of them are supposed to be done during Login state. It's also used by Velocity, and that's where valence_network uses those packets itself. Otherwise I'm actually not really familiar with that
We already have support for velocity built in, but I suppose it would be better to make it extendable by users. Let's have this be low priority for now.
Describe the problem related to your feature request.
It would be nice if
NetworkCallbacks::login
implementors could send/receiveLoginQueryRequestS2c
/LoginQueryResponseC2s
packets to allow dealing with clientside mods and whatever elseWhat solution would you like?
The
login
callback could receive a reference toPacketIo
as a parameter. The struct could also have a convenience function for both sending a query and awaiting a response from the client (according to wiki.vg at least it's always supposed to send one back)What alternative(s) have you considered?
Outside of modifying/replacing default Valence crates, none
Additional context
-
The text was updated successfully, but these errors were encountered: