David Duarte
David Duarte
> Well we are MineWowFus and the gameplay would be better if we were MineWow or Dofucraft Better we don't know without comparing, and for now we can't compare
> @DeltaEvo can you give more details about this issue ? There is not much details to add, we will close this when we think that we have the minimum...
I observed that too. The root issue for me is that the "actions" stream and the reduce body should never throw errors, currently I guess that this is an unwanted...
As the inventory order is not something that we care much we can store that data on the Redis (only the order)
It's really weird since https://github.com/PrismarineJS/minecraft-data/blob/master/data/dataPaths.json#L910 it should be the same protocol
Ok so after investigating this is a bug in node-minecraft-protocol, the client is ended since the protocol version don't match https://github.com/PrismarineJS/node-minecraft-protocol/blob/1796b9693d02be5fa8e6e4a03c547e430b0bf21d/src/server/handshake.js#L18 and since we are changing the serializer the connection...
> Set defaultMaxListeners to infinity. May be risky? Yes I think it's not how we want to solve that as this warning is useful, it's just that the default value...
Yep this is (I think) when we reach the limit for mobs state listeners, for that one we are maybe leaking event emitters
Waiting for #332
Another solution could be to use a service that already has this feature like [netlify](https://www.netlify.com/), [vercel](https://vercel.com/), [cloudflare pages](https://pages.cloudflare.com/), ...