I’ve had a working plugin with nakama-2.7.0 for a few months now, however I recently added some functionality to it and in doing so, I added the dependency for some Agones libs. This caused Nakama to be unable to load the plugin due to “different versions of …” errors. Since my Nakam was out of date, and things were broken anyway, I decided to take this opportunity to upgrade to Nakama 2.9.0 and upgrade my plugin to use nakama-common-1.3.0 at the same time
The upgrade was simple enough, however when I try to run Nakama with my plugin, I still get weird dependency conflict errors. What’s more, is the dependencies in question aren’t even in the go.mod/go.sum files of either my plugin or Nakama.
So Im at a loss right now as to how to proceed.
One approach is to create a separate service that uses the agones api and simply call it via HTTP from nakama plugin
I did this with another layer that also caused (different kinds of) issues, however I’d rather not have to do this every time I want to add functionality to Nakma
For some reason the error messages were being interpreted as links so I am unable to post them here as I am a new user. As such, I have created this pastebin link with the errors.
It should also be noted that I am building my plugin in a docker container with the exact same base image as Nakama-2.9.0 so I know that the same go version is being used.