Andrei Mihu

Your log doesn't show anything useful, and also doesn't seem to contain anything that's in your screenshots. At this point it's looking like it's an issue with your setup or...

+1. Would love to have this on Maven Central!

@maciejmrozinski I think it's important to note relayed matches aren't really "created" in the sense this word might imply. The matchmaker only generates match join tokens. If you prevent (with...

Looks fine in both [Docker Hub](https://hub.docker.com/layers/heroiclabs/nakama-pluginbuilder/3.19.0/images/sha256-2158eedc44db27a4908a2aeb81007cb620444fa55f151b28f92d2c733e0b4fd3?context=explore) as well as pulling directly from the registry: ``` $ docker pull registry.heroiclabs.com/heroiclabs/nakama-pluginbuilder:3.19.0 3.19.0: Pulling from heroiclabs/nakama-pluginbuilder Digest: sha256:2158eedc44db27a4908a2aeb81007cb620444fa55f151b28f92d2c733e0b4fd3 Status: Downloaded newer image for...

Cannot reproduce, please re-open if you see this issue again or with later versions.

We are currently not comfortable integrating hot reloading into the server itself due to considerations around various existing running processes: match handlers, RPCs, before/after hooks etc. Our concern is it...

The allocation was already being done once, so resizing wasn't needed during the loop iterations if that's the concern. Do you have a little benchmark test that compares the two...

There is not enough information provided to understand why the server should process one additional message when an error is encountered with the socket connection. If you can provide this...

Discussed further [on the PR here](https://github.com/heroiclabs/nakama/pull/1165#issuecomment-2282810237).

After internal discussion, we determined the current behaviour is actually desirable: `"*"` must fail on any existing value even if fully identical. This allows Nakama to support use cases such...