godot-demos-2022 VS godot-next

Demos repository: https://github.com/GDQuest/godot-demos-2022 (please leave a star!)

The demo on GitHub: https://github.com/GDQuest/godot-demos-2022 (please star the repository!) The demo's explanations: https://github.com/GDQuest/godot-demos-2022/tree/main/save-game#save-game-with-resources (video coming soon)

If you want easy access to the correct values, check out Vec2 from godot-next. Also check out Vec3. Also available for C# (Vec2, Vec3).

Recently I've gotten into customizing the inspector view for exports. It's a lot of fun, and godot-next is a godsend.

Godot has no built in support for ecs, behaviour or even btree. But you can work around this in several ways. There is a behaviour node in godot-next (https://github.com/godot-extended-libraries/godot-next/blob/master/addons/godot-next/resources/behavior.gd) that you can use, you can use a state maschine or you attach little behaviour script nodes as children that do the work. There is an GDQuest ECS tutorial for godot, that may come in handy (https://www.gdquest.com/tutorial/godot/design-patterns/entity-component-system/)

I can understand how a global signal singleton isn't satisfactory, but why not just write a string-based event dispatcher? In fact, I'm pretty sure Godot Next has one with a wrapper node for singleton usage. With a few tweaks, you could make message dispatches be handled via pattern matching on a RegEx for the message type, thereby letting you have wildcards and the like.

Variation on 2 that uses a tool script to procedurally generate properties on a class based on files that match a specific search criteria. This would prevent you from both needing to update file paths and from needing to even add entries in a record somewhere that the level exists. It would just be detected automatically by the tool script. You can procedurally generate properties by overriding the _get, _set, and _get_property_list methods. I have an example of this in Godot Next's ArrayMap class here. I also have a sample script that fetches a list of scenes in Godot Next's FileSearch class. You just call FileSearch.search_scenes() and it will return to you a Dictionary with keys containing filepaths and values containing another Dictionary initially just the path again (mapped to a "path" string), but which you can really make have whatever you want.