C# users are second-class citizens in Godot. Many features such as web exports don't work with C# projects, and C# often has bugs specific to it and often lacks tutorials/documentation
... welp. So... any more details on this? I'm not learning a single-purpose language.
Edit: yes, GDScript seems nice, I know. Please stop recommending it though :P
The C# version of the project is separate from the main one. It is possible to entirely code a game in c++ though in the main one (you can use both c++ and gdscript in it in one game interchangeably). Gdscript is a really easy language to learn though and is similar to other scripting languages (the only things you really need to learn is some keywords godot added to make coding in it easier when using things in the engine. Stuff like node names etc you would have to learn regardless of the language you’re using)
Honestly GDscript is really easy to learn if you’ve got a programming background. The concepts are mostly the same so you can head over to the GDScript reference and learn to use it in less than a day. As soon as you get used to the syntax you basically know it already.
I'm sure you're right, and it looks serviceable. It's not really about that, though. I've done the "learn a new language" thing many, many times. It gets old and I'm sort of over it - it's not as fun as it once was, particularly now I have my favorite that I know well and am good at.
GDScript works almost 1-1 like Python. Any experience with Python almost instantly translates into knowing what to do in GDSCript, but not necessarily the other way around, as their script has a couple more builtin features.
Was going to say this but you beat me to it: if you know Python, you pretty much already know GDScript. It’s not at all like needing to learn another language from scratch.
If you’ve done it a lot then you know how easy it is to get up and running with a new language.
Really, it’s not that hard. GDscript is not some archaic clunker like COBOL with outdated paradigms, nor some esoteric joke language like Brainfuck that’s just pointlessly difficult. You’re going to be fine with it inside of a day.
I’ve been working in Godot for about 3 years now, and have never touched GDScript. I personally haven’t felt like a second class citizen, and have rarely run into C# specific bugs, or found the documentation was missing for C#, other than when I was using the GD4 betas.
That being said, I’m not currently targeting web or mobile with my hobby projects, and I know those are open issues with the C# support.
C# works fine, lots of Godot projects are using it.
That said, consider learning GD Script? Even if it’s only used by Godot, it’s simple, well integrated with the editor and is awesome for quickly building out your game.
Besides, it’s very Python-esque. Whether you know Python or not, it’s syntax is very straightforward and easy to work with.
GDScript is very similar to Python; if you know Python, learning GDScript takes about an hour.
declaring a function uses the func keyword instead of def
there’s an actual concept of variables and constants, in python you’d just say number = 3 but in GDScript you do var number = 3 or const number = 3.
the constants “true” and “false” aren’t capitalized like in Python
"match" is switch…case but slightly more terse.
No lists, just arrays. There are also enums. There are also several built-in data types like vector2 or vector3 which are handy for storing position and velocity data in 2D or 3D space.
There isn’t a module/library system; some things like random number generation, timing, math etc. are provided by the base language because they’re ubiquitous in game making, others, such as functions for audio playback, are provided by the node that your script extends. Right about here we get into territory where it’s more about how Godot works and less about how GDScript works, and concepts such as onready, signals etc. would be required learning no matter what language you use with Godot.
Personally I dislike using scripting languages as the primary language for any bigger project. The lack of proper static typing commonly causes issues with linting, code-completion, error highlighting and refactoring tools. Lack of namespaces can lead to name clashes with type names and such especially ones you start adding bunch of 3rd party plugins.
Also using having to include/preload any script files using string references like this: const Rifle = preload(“res://player/weapons/rifle.gd”) is not just plain bad in my books. Its just plain dirty compared to Namespaces in C# or Packages in Java.
I do like Python and I use it quite a bit at work to automate things as you can install and import bunch of ready made libraries for almost anything and just write script that is like sub 500 lines and does whatever. But the moment I need to make anything that contains multiple files and some object oriented practices things will get increasingly more annoying very fast.
Having interfaces is quite nice as well as it allows me to keep my code more loosely coupled. I try to keep my code as portable as possible by keeping much of my code in a separate project that has no dependencies to Godot. This way I can use nUnit in another separate project to do unit tests for the code and just write wrappers and whatever in Godot project. If Godot API changes I generally only need to fix the code in the wrapper classes.
“and it even adds the .gitignore for you!” I’m sold I hate trying to figure out what version of base gitignore I need for what version of Unity. Thank you for making this!
It’s definitely a big point for me too, using Git with Unity is a big pain. Even using the right gitignore I often have to upload large Unity-generated files to my github which might’ve pushed me to using Git LFS. Having something that just works is liberating.
You may want to change the fact that web exports don’t work on macOS. MacBook Pro M1 user here. I’m happily running my Godot 4.1 as web exports on my server. Setting the headers is required for any browser / operating system, but things seem to work fine for me on Mac.
According to that, you have to manually set the renderer to Metal* or it might freeze/crash your browser (or take minutes to load). I’ve personally had many mac users tell me that my web projects aren’t loading for them, I’m pretty sure the issue is still not resolved.
Great post! Definitely helpful with the Unity drama going on now. I had initially started my game dev journey on Godot, but recently switched to unity bc of console support. Really thinking about switching back, especially now that v4 is out.
The linked article literally says it is not officially supported though, so which one is right? Are you talking about W4 which sounds like some unofficial WIP workaround?
Iirc, console development requires signing an NDA or something, which is why there are no official docs on porting a Godot game to Xbox, PlayStation, or Switch. There are, however, third party companies that Godot vouches for that have a good track record of specializing in porting Godot games to consoles.
W4 isn’t unofficial, it’s literally the core engine devs who started a private company for the purpose of doing things the Godot Foundation can’t.
W4 doesn’t own Godot in anyway, but they can sign the required NDAs and gain access to the SDKs, which cannot legally be given out with an open source software like Godot.
The NTFS warning is a little disingenuous. I wouldn’t recommend people go with it if they’re choosing Linux only obviously, but I’m going to say with years of personal testing about 99.9% of things work just fine using an NTFS drive. I think it’s been years since I had any kind of issue with game data that I attributed (and maybe falsely) at the time to the NTFS filesystem.
In steam you’ll need to symlink your compatdata folder to a linux filesystem, but that’s about it.
I’ve tried this also. It works alright unless you write files in Windows, it will set the UID to the Windows SID. WHen you use a Steamlibrary and move back and forth, games that are updated in Windows can give you permission errors in LInux, etc.
It’s all workable and definitely an option, but WinBTRFS has a performance overhead, and the dualing permissions made it not a perfect solution.
Yeah I remember having permission issues that were easily fixed with chown but they were hard to notice. I haven’t booted to Windows in over a year now so I must’ve forgotten lol.
I’m pretty sure WinBTRFS’s readme has a section about properly setting up the user and group permission stuff. Essentially just providing the Windows UUID to Linux POSIX equivilant, which generally ends up fixing all the permission related problems. The only real caveat is it not working with SuperFetch, so files aren’t cached in memory and have to be loaded from disk with every read.
I see that you dedicated a paragraph to NTFS. There are quite a lot of people saying there are problems with gaming on Linux using an NTFS drive but I’ve rarely (never?!) seen anyone actually having problems with it. I myself have been dual booting for years and some games are on an NTFS drive shared between Linux and windows for convenience and I never had any issues besides the fact I had to disable fast reboot in Windows.
I’ve heard a lot of varying experiences but for me personally I just couldn’t get it to work, and I tried most of the workarounds like disabling fast reboot. It worked for a while but every now and then I’d constantly have to reset permissions for the entire drive, and even then games would not run sometimes. If someone knows more about this I’d love some info on it, but in general most of the Linux community agrees that NTFS causes more trouble than it’s worth.
When I still had a ntfs drive some games would play fine off of it but some would barely run or fail to launch completely. ESO didn't care about being on an ntfs partition and ran fine. I think it was Doom 2013 that didn't like it for me.
I used ntfs while ago and the driver included in kernel corrupted my drive :p It was also very annoying when almost every single boot windows was forcing sfc scan and linux had problems mounting with write permisions.
It’s been a while since I switched to btrfs but I do remember the permissions being an issue with NTFS. It was quite annoying because Steam wouldn’t trigger an error so it was hard to debug when the game never opened.
I recently realized that Unreal is Open-source. I’m curious why it doesn’t seem to get any love from the FOSS community? I would personnaly glady ditch unity, but I heavily rely on video tutorials for my very amateur projects . So I was actually moving to Unreal…
Unreal is “source available”, not Open Source. There’s a big difference. With any Open Source project you can legally fork the project, distribute your custom version of the code, create a community around your variant… “source available” has none of that. The Unreal EULA is more permissive than most game engine licenses (with the obvious exception of Godot) but it still comes with plenty of restrictions. For example:
You are permitted to post snippets of Engine Code, up to 30 lines of code in length, online in public forums for the sole purpose of discussing the content of the snippet or Distribute such snippets in connection with supporting patches and plug-ins for the Licensed Technology, so long as it is not for the purpose of enabling third parties without a license to the Engine Code to use or modify any Engine Code or to aggregate, recombine, or reconstruct any larger portion of the Engine Code.
Bookmarked for later. Right now my aging PC is Windows 10 but been seriously thinking going OpenSuse with my next build, since Proton is magic according to my Steam Deck.
popcar.bearblog.dev
Top