I once tried to use the dialogue extension in Gdevelop for a game, after months of trying to make it work, I ended up with my own similar self-made extension.
What I think the problem is: The dialogue extension easily breaks and not consistent. I know that there some good games that manages but this but it isn’t user friendly and frustrating.
This is my stance. I want to hear yours and a recommended solution (even on Gdevelop codebase).
Edit:
I mean that: There are problems with the extension isn’t the Gdevelop event side but the easily-breakable Yarn.
I do not feel that the bolded line is really accurate. Edit: or at least, nothing I’ve ever experienced matches up with that statement.
From everything I’ve seen over the years, the same events will always produce the expected behavior using Yarn dialogue, so long as your dialogue file is set up correctly.
As far as I’ve ever experienced, there’s only 4 events needed to start using dialogue.
An event with the “load dialogue” action
A separate parent event with the “dialogue is running” condition
A subevent with the “scroll clipped text” action (with whatever conditions you want)
A separate event that sets your text object to the clipped text.
The rest is up to how you use it (timers, conditions, etc) and will generally be as complex or as simple as you need it to be.
Having used Godot’s dialogue system and a few in Unity (including Yarn), generally the level of complexity is higher in their systems than in GDevelop.
I’ve made 3 examples projects of my own using dialogue, and another 2 that even use the yarn system for something completely unrelated (inventory descriptions). Behavior of the events are always identical so long as it is set up according to the documentation on the wiki and examples in the engine.
Every community video tutorial I’ve seen always overcomplicates (or confuses) what’s required, which could maybe cause issues for folks? The documentation and examples in the engine are pretty spot on and was all I needed to get it set up, so I always point people to that rather than any community videos.
Yes @RMDB and @Silver-Streak. I’ve used the extension for smaller projects before it worked fine. But on larger projects, any small problem in the yarn file (e.g a space at ending of a line in the yarn file and many other bugs) can break the entire dialogue. I am speaking from a very painful experience. The game I was working on was multi-language and had a lot of dialogue. The problem that caused me to do a little rework of the events is a space at the ending of a line with for some reason stopped the clipper.
There are problems with the extension isn’t the Gdevelop event side but the easily-breakable Yarn.