Shane Freeder

You are more than welcome to submit a PR

such a thing should generally be within a seperate PR

It's worth noting that there are already libraries to handle this at runtime, https://github.com/jpenilla/reflection-remapper I'm not sure if this is something we will bother with, given our intent to move...

Guess of the translation but that port is already in use by another program, you'll need to change the port in the config or find what is using the network...

Each instance of JSONAPI needs to be on a different network port, this can be changed in the configuration files for the plugin. > On 2 May 2016, at 13:19,...

I think that we generally won't support the older syntax, but, not exactly against it being on the page as ref as many people end up for some reason creating...

This was long on the list of stuff that I wanted to look into, given that we're not rewriting this stuff, I did wanna look into adding a mechanism to...

I mean skip the decode + handle + encode chain for unneeded packets in certain configs; if we're not rewriting entity metadata, then we can skip a bunch of work

True, but part of it was for other stuff like scoreboards, etc; it's probably not a big deal, and probs not something I'm ever going to care to get to...

That API is currently in a weird state due to the fact that it relies upon legacy behaviours, it's not currently planned on what we want to do for it...