Serialization is incredibly important to games, and often painfully difficult to implement well. Unless you just like building serializers, you may find yourself putting off developing a save/load system, especially if you need more than just a simple "what level am I on?" mechanism.

About a year and a half ago, starting a project with Godot and C# was a brave choice. There's always been a C# channel in the main Godot Discord server, but information and tutorials (let alone demos) were all but non-existent.

Now that it's 2024, let's take a look and see how far we've come.

Game architecture, like all software architecture, tends to be neglected or forgotten as a project goes on. Scalable, enjoyable, production codebases are so rare they're almost mythical.

The game engine company Unity has once again gained notoriety for offending its users. This time, they've announced a $0.20 per install fee for games that surpass $200,000 in revenue. Of course, how they determine what constitutes a valid install is not something they're willing to share.

Almost every day, someone asks "Should I use GDScript or C# to make my Godot game?"

A lot of amazing advice has been given out on the Godot Reddit, the forums, various Discord servers, and just about anywhere people are talking about Godot — so let's write it up, once and for all!

Godot is a viable alternative to Unity — not just for early adopters, but for game developers and artists across the entire skill spectrum.

You've always dreamed of making that C# game, but engines have always made it too difficult — until now.