It’s time to make that indie C# game in Godot

There is a book that actually tells you not wait for Godot : https://en.wikipedia.org/wiki/Waiting_for_Godot

> Godot doesn’t fight you when you’re building scenes. Making a scene feels a lot like creating a class using composition, and scenes can even inherit from other scenes (using another scene as the the root node of a scene allows you to inherit from it and override its properties in the editor and in code), allowing you to express patterns you’re intimately familiar with from object-oriented programming.

I personally find the approach of nodes everywhere a bit odd.

In my mind, you'd typically use nodes for objects that are supposed to represent some sort of an object or concept within the scene, whereas the scripts would be the ones that actually give said object any number of behaviors, such as a certain group of functionality per script.

So you might have something like the following:

  EnemyObject
    PathfindingBehavior
    ShootingBehavior
    TalkingBehavior

Unity kind of vaguely got that "right" (e.g. in a way that's subjectively intuitive to me) with its component system.

Whereas in Godot you can only have one script per node, which would mean that in practice I'd have something like:

  EnemyObject
    PathfindingObject
      PathfindingBehavior (attached script)
    ShootingObject
      ShootingBehavior (attached script)
    TalkingObject
      TalkingBehavior (attached script)

It kind of feels like it would be nicer to be able to attach a number of scripts to the object that I actually want to control, instead of having Nodes that I don't really see much of a use for, apart from them being script containers.

Of course, maybe that's just because I'm used to the GameObject pattern that Unity uses, an entity-component system (of sorts), though that implementation has gotten a bunch of critique as well, with DOTS apparently being a better ECS approach, though also unfinished in certain aspects.

Just felt like sharing my thoughts on that particular aspect, which some might find curious and which might take a bit of getting used to (though personally not having a separate "prefab" concept and instead having more or less everything be a node is also pretty freeing, I have to say).

With a bit of love, using C# could also be pretty amazing, since GDScript does have certain limitations (performance comes to mind, for when you need it to be decent for number crunching but don't want to/can't use C++ due to knowledge or other restrictions, C# has your back there) and curious design choices (the integration with the engine is super nice and the Python like syntax is great, but having to define singletons in the editor IIRC is a bit silly https://docs.godotengine.org/en/stable/tutorials/scripting/s...).

How easy is building to mobile in Godot?

I have been a Unity dev for years and my main reason for using it is that I can build to most platforms with relative ease from the one engine.

> Is this actually true?

I'd say that yes, at least in the last 5 or so years.

I decided to make a scene which would contain a single copy of every single model that I'd like to use in a project of mine, for checking the textures, how lighting works, the scale of everything etc.

By the time I got to around 200 different objects (no high poly ones, by the way), it took like a minute to just open that scene.

Godot is an amateur project compared to Unity, it's not even close. What game actually shipped on Godot? I can't cite a single major game on it.

https://godotengine.org/showcase

Looking at any of thoses games looks bad tbh it's like weekend project / low indie games.