godot-fsharp-tools VS godot-proposals

Hello guys I am new in Godot and I am trying to install this plugin FsharpTools, but i am getting these errors:

For what it's worth, Godot can do the same: there's a Godot version of Arcadia for using Clojure, and Godot F# tools takes some of the tedium out of using F#, though you have to make a small tweak to the .fsproj file it generates because the Mono assemblies moved. It works via a cheesy little hack: you make a C# script in Godot that's just an empty class that does nothing else but inherit from an F# class, and the F# project builds at the same time by adding it as a dependency of the Godot-generated .csproj file. Godot doesn't know anything weird is going on and it just kind of works :)

For something OCaml-like but more approachable, it'd probably make more sense to try using the Godot game engine with F#. You can build the GUI itself visually, the godot-fsharp-tools plugin lets you piggyback on the C# support to write code in F#, and it's pretty easy to build for different platforms. The learning curve of figuring out how things work and translating it to F# is a bit steep, but can be mitigated by starting with the built-in GDscript and working in F# code where it makes sense as comfort and familiarity increases.

I looked at it before, but I'm generally more interested in languages like OCaml, F#, and Clojure (I tend to think and code in a more FP style so they suit me better) so I ended up using this plugin. I should probably give Nim another look since it has some features I like; I just really like the more advanced OCaml and F# type systems, making Nim seem like a step backward in that regard so I never gave it much consideration.

I haven't messed with it much lately but I was working from a combination of Godot F# tools and this 3-part blog post, plus a bit of trial-and-error. I don't have any good examples, I was doing a few tests to feel through how C# examples in the Godot documentation translated to F# and some random not-Godot-specific F# code setting up some data structures and logic. I'm more familiar with OCaml so I was basically trying to feel out F#/OCaml differences while figuring out F#/Godot integration, rather than make anything coherent enough to use as an example.

Godot was fine, for the most part, it's a good engine for small games. The main issue was around working together and resolving conflicts with git (Godot isn't really working and constantly kept changing IDs in resource files), and it kept losing data in scenes when the code changed so we had to rebuild things several times. On previous test games we also ran into huge performance issues in the editor when we wanted to do too much work in scenes, so we had to switch to doing most of the work in code.

The worst part was when I had to rip out a bunch of testing code that used @tool for release as it seemed to cause issues when doing a release build. The engine is generally not great when you want to follow clean software engineering (e.g. dependency injection is not possible, I opened a proposal to that end here[1]).

[1]: https://github.com/godotengine/godot-proposals/issues/8850

If we had a Mask2D, this would be super easy and straight forward.

So if that's what OP meant, clip_children property won't work. Instead OP needs to use a CanvasGroup parent and the Line2D (with CanvasItem Material in Subtract mode) and TextureRect as siblings, or any of the other methods explained here until we have a Mask2D node.

There is an open proposal to have a compile option for a LibGodot, as a Library https://github.com/godotengine/godot-proposals/issues/6267

Yes, there could be the option to open at least 2 tabs at the same time, when working with scripts. This has probably already been suggested in: https://github.com/godotengine/godot-proposals

I cannot tell exactly where the jitter is from the video, but if it is what I'm thinking of, it is a known issue, see here. There is a proposal to fix this, with tons of discussion here. Try some of the workarounds mentioned in these two links. Game looks great by the way!

It's in the release notes. Here is a link to the pull request, based on this proposal.

Currently not possible: https://github.com/godotengine/godot-proposals/issues/7213