go-plugin VS shotcaller

I am looking forward to a mix of both - I am hoping to add a concept called "operator" which would be a go-plugin [1], just like terraform providers, but build backends. So, someone would be able to, say, write a Slack plugin (in Go, or anything over RPC) which sends a message once a build is complete - like Jenkins/GitHub actions, or just scripts that we can reuse like GitLab CI through `modules`.

Perhaps a new registry where we can push custom modules and providers (operators in this case), I'm curious to know about if we have any existing implementations we could reuse for the registry.

[1]: https://github.com/hashicorp/go-plugin

I'd recommend looking into a different approach for plugins such as hashicorp/go-plugin (which uses multiple process PIDs and RPC communication between them) or traefik/yaegi (which implements a Go-compatible scripting language that can be interpreted at runtime and which still supports most Go modules).

You'll never fully protect your code from someone who's dead-set on reverse-engineering it, however, you can use https://github.com/hashicorp/go-plugin or a similar RPC technique, which will let you ship binary plugins and will also be less fragile and janky compared to something made with `-buildmode=plugin`.

The plugin system that hashicorp uses for all their projects works very well. It's essentially a local RPC implementation. https://github.com/hashicorp/go-plugin

can you try older go-plugin versions? The only major change in v1.4.4 was a bugfix for automtls. https://github.com/hashicorp/go-plugin/blob/master/CHANGELOG.md

As for a project using these, see: https://github.com/amethyst/shotcaller and https://github.com/jojolepro/minigene :)

We do indeed intend to be on the lookout for such opportunities for standardization. Our main R&D project in this regard is Shotcaller, which is made with bracket-lib by people who have previously worked with Amethyst Engine.

https://github.com/amethyst/shotcaller

We’re happy to help any newcomers along on our Discord: https://discord.gg/qvJyTYM

I’m building a minimalistic, 1v1 MOBA game (Dota/LoL) that’s all about grand strategy at the macro level, like chess. It is designed from scratch to accommodate AI development.

OpenAI gave up after beating 99% of players in a limited version of DOTA2. They essentially just figured out how to out-micro human players. We want to let players play alongside AI assistance, like a racing car driver backed up by their team of mechanics and engineers.

https://github.com/amethyst/shotcaller

Make a new 🦹 Leader or 📦 Item!

Make a new 🦹 Leader or 📦 Item!

I’m working on one such modern RTS game: https://github.com/amethyst/shotcaller

It’s a MOBA-style game that is played 1v1, with the 5 “players” on each side controlled by autonomous bots. This design accommodates AI development as part of the sport, much like a F1 driver and their team of engineers and mechanics.

The game is written in Rust and will use WASM for scripting to accommodate a wide range of languages for both game modding and AI code. While it’s only 1v1 in its initial iteration, I agree that there’s immense value in cooperative and more micro-level play, so we do intend to incrementally move towards that as an alternative game mode.

I’d love to chat more with anyone interested in this particular design or RTS/MOBAs in general. You can find my email on my GitHub.