Fairly new to UE5, I coded bunch of passing conversations, but this is getting a bit annoying
The ways I did it these:
Add delay to conversation:
Add buttons on top of each other and make the visible/invisible in order for each text:
Setting up one button and an integer to increase its count to let the button know how many times the button is clicked on:
But all of these gets messy when I want to have multiple long conversations, ideally I would love to have it like this, not sure if its possible on UE5 thou, as blueprint or c++:
Set text1
button(“continue when I am clicked”)
Set text2
button(“continue when I am clicked”)
Set text3
etc.
I found this on the wiki:
But I have no idea how this even works, let alone doesn’t seem to work in widgets to begin with.
How do you guys code passing conversations?
Ideally blueprint only answer since I haven’t looked into C++ side of UE5 yet but if that’s the only way, I will check it out.
I’m not quite sure what your problem is.
From what I can tell (though I can’t tell much since you’re so zoomed in), you can just increment your ConversationOrder number whenever the button is pressed and then trigger the dialogue play event.
Also, just as a tidbit- increment (++) sets the variable, so you don’t need to set the variable again after.
The diamond symbol means it directly changes the variable.
Although, I would strongly recommend watching a tutorial at this stage to create a robust solution that will be easy for you to add on to.
It seems like you’re manually adding every single dialogue line as a node rather than using an array or other solution.
1 Like
Basically I want a block of code that would hold my “signal” until I press a button to continue its path, and do that multiple time with the “same” button
Yeah, that was a code block from when I just started learning UE5, figured out how it worked later
Every tutorial I checked on the conversation topic either uses very basic, 1-2 lines of conversation, or uses a paid plugin which I don’t want to do before learning how base UE5 works.
Yes,uhhh, I just realized I am dumb, that would help me a lot actually, thanks!
Still I would prefer a “freeze the code from moving forward until I pressed a button” thingy.
