Hi Ben,
I don’t know if this came up in the live steam on Friday as I haven’t had time to watch it yet.
You mention in the design docs that we’ll probably use a free third party asset to do the dialogue branching. Would it be possible to do a simple quick video in the course to explain how this can be done in code? I’m not against using third party tools but I do like to understand how I would go about doing things if the third party asset didn’t exist.
Kind Regards,
Steve
A followup question to this.
Is this a coding asset or a separate utility to do the dialogue branching before adding it into the code?
If so, any chance you tell us what utilities you are looking at so we can play with them ahead of time?
Rich
Actually, in the live stream Ben said he was going to stay away from 3rd party tools if possible. He would like for us to learn what he is trying to teach instead of plugging in addons.
I have already built a dialogue system so if Ben does an add-on of it, I could make a YouTube tutorial going over it if people want. But I don’t think Ben is going to do plugins. This is suppose to be a learning course after all.
Hi Garrett, that would be really cool if it’s not covered, thanks.
In the GDD on in the Early Access links, Ben mentions using Fungus, a dialogue branching ad-on, which is why I asked.
Ohh, I didn’t see that. Lol.
I wouldn’t mind doing a tutorial of it. The only other tutorial of it that I found which is okayish to understand is GamesPlusJames YouTube dialogue tutorials.
Garrett! That would be great if you could create a tutorial.
I actually think not using Fungus would be far better. Fungus is for non programmers and using it for the course is counter intuitive to everyone’s learning… It is better to be able to code things yourself or at least know how to code an add-on if you are going to use it. But what if you aren’t going to use Unity and you are planning to transfer to another game engine like Unreal, Gamemaker, or Cryengine etc? Trying to make a dialogue system in another game engine will be difficult because you wouldn’t have the know-how to code it.
Just saying that if we use this add-on, you aren’t going to learn much from how to code it yourself and you won’t have the know-how to make the dialogue system in other game engines/editors…
I don’t know what Ben is going to do but I hope he considers not using any “no programming needed” add-ons.