@dkozlov This looks interesting but because it’s a fork of the game server it’s not really easy for the community to use.
Is there a reason you couldn’t implement this logic as part of library that developers can pull in to load features in their Go code or JavaScript code (or both)?
From what I can tell a lot of the functionality would be a perfect fit to be provided in that way. A good example of an experiment we’ve done like this was the party system prototype ahead of our official realtime parties feature:
Hello @novabyte! It was originally implemented as part of library challenge-league/nakama-plugin-challenge-league (nakama plugin) which was the recommended way according to the nakama documentation.
I am using nakama plugin as backend API and GitHub - challenge-league/nakama-go as client side frontend. In my situation client side is a discord bot that calls nakama backend API.
Regading the fork of the game server: if you look at changes (v0.1.0 · challenge-league/nakama@de15bea · GitHub) you will see that I have not modified the server but I have added the required dockerfiles and changed go.mod due to incompatibility with go.mod in my nakama-plugin.
@dkozlov I see I think I understand how you’ve laid out your code now. Your features are packaged as a library that can be consumed by game teams. I think there’s some improvements that could be made I’ll try to spend some time on a pull request if I get the chance over the next couple of weeks.
