Godot Card Game Framework VS builder

Good luck for you, there is a card game framework, though I have never used it so I cannot speak for its quality.

It's under AGPL license (have fun reading through this ugly monster). Among other things like telling you what to do when you sell or merge your company, using means you would have to make your project open source and AGPL too, if you take stuff from it.

If you plan on using this, be sure to check and try to understand the monstrosity of a license you can only use it under. Unlike the vast majority of assets shared on the Asset Library, this particular one is not available under the simple, easy to understand and permissive MIT license.

There is actually a card framework which might be helpful, never used it though: https://github.com/db0/godot-card-game-framework

I have found Godot_Card_Engine, a plugin by BraindeadBZH, and Godot Card Game Framework by db0, and was curious if anyone has had experience with either. Are these the best options or is there something else out there I may be missing?

https://github.com/db0/godot-card-game-framework and a framework

As others mentioned, I have created a card game framework on Godot which would fit all your requirements. I also have 2 different games in progress with it. One is like Slay the Spire and the other is a more traditional CCG style, called Fragment Forge. You can use them as reference.

Godot [0] is super intuitive, so I recommend it wholeheartedly. And then you ought to look at the Godot Card Game Framework [1], which I've also used for a uni project.

The author has a couple of examples (check their Github repo), which you can play online [2][3]. Also, join the Discord (check the repo for a link). The community is very friendly and helpful (just be sure to learn Godot first, though).

0. https://godotengine.org/

1. https://github.com/db0/godot-card-game-framework

2. http://fragmentforge.dbzer0.com/

3. http://dreams.dbzer0.com/

We have a partnership with Hathora (https://hathora.dev/) so that our infrastructure can scale globally with high performance so we can provide the best user experience possible despite the realities of playing games over the internet. We also have some big plans around using rollback that we've covered elsewhere that we're cautiously optimistic about.

For multiplayer/server-less games, try Hathora

I cofounded Hathora (https://hathora.dev/) last year and we've been working on making it easier for smaller teams and individual developers to build scalable multiplayer games. We think the serverless model is the simplest approach, allowing you to dynamically provision a new instance of your game server when users or your matchmaker requests a new session.

We made this .io style demo to showcase this approach, and we're releasing the source code and documentation alongside with it.

Hey I'm the creator of https://hathora.dev/ which aims to provide a super simple deployment and scaling experience for session-based games. It's based on containers and can deploy any kind of game server. Check it out and see if it meets your needs!

At Hathora, our mission is to make it easier for developers to build, launch, and scale multiplayer games. One of the core technologies we have built is the Hathora Coordinator, which is our fully managed multi-tenant implementation of a Stateful Router.

Hi there! I started a company this year focused on multiplayer server infrastructure. We also built a multiplayer game framework for Typescript that has gotten 400+ stars on Github in the past few months: https://github.com/hathora/hathora

Would love to connect and exchange notes about multiplayer development -- if you're interested, my email is on my profile.

I've been working on my own realtime networking engine[0] and I think there are a few important points related to network syncing that are not mentioned in this article:

1) Bandwidth. The users internet can only handle so much network throughput, so for fast paced games (where you're sending data to each client at a rate of 20+ frames per second) it becomes important to optimize your per-frame packet size. This means using techniques like binary encoding and delta compression (only send diffs).

2) Server infrastructure. For client-server games, latency is going to be a function of server placement. If you only have a single server that is deployed in us-east and a bunch of users want to play with each other in Australia, their experience is going to suffer massively. Ideally you want a global network of servers and try to route users to their closest server.

3) TCP vs UDP. Packet loss is a very real problem, and you don't want clients to be stuck waiting for old packets to be resent to them when they already have the latest data. UDP makes a major difference in gameplay when dealing with lossy networks.

[0] https://github.com/hathora/hathora

I built a bunch of multiplayer games in the past and am now working on a framework to try and make it easier for others to do so: https://github.com/hathora/hathora