mcoms
mcoms
It's a great idea, but it's not good for us to just implement it right away, as that was [why](https://github.com/GlowstoneMC/Glowstone/pull/352#issuecomment-266331081) the packets branch PR was closed. It would be better...
Yes, unfortunately, in the time that we've had, we've found other things to do that to us felt more valuable for us to do in that time than the packet...
@DenAbr If my comments make you think that I'm not interested in having a packet API, please understand that I am completely supportive of a packet API. But also understand...
Could you upload an example?
Yeah, a standard benchmark could even be coded in.
We already have metrics, but I guess we can add more recorded data. http://mcstats.org/plugin/Glowstone
I honestly think the sounds map is useless for 1.11+, so that should be removed as well. Instead, there should be a map of sound ID exceptions.
What is "Yarn" in this context?
Of course not, nor would they even be useful. We don't touch Mojang code at all, and the CLA prohibits Mojang code structures in Glowstone. Now, it may be useful...
Referring to other code can be useful, as long as it is done under their own license/terms. Please also keep in mind that some servers do not have the same...