I'd prefer using any arbitrary jsonobject as the status packet payload to support third-party modloader fields.
The implementation keeps support for the typed json data, but allows the user to additionally provide any json object they want.
I don't think this is outside of the scope of the project as this could allow people building a MCPL client (like me) to detect if a server to connect to is a forge server to enable different logic/prevent joining due to different protocol.
my current workaround is registering my own status data packet, which is a thing i wanna stop doing
I'd prefer using any arbitrary jsonobject as the status packet payload to support third-party modloader fields. The implementation keeps support for the typed json data, but allows the user to additionally provide any json object they want. I don't think this is outside of the scope of the project as this could allow people building a MCPL client (like me) to detect if a server to connect to is a forge server to enable different logic/prevent joining due to different protocol. my current workaround is registering my own status data packet, which is a thing i wanna stop doing