Add simple variable to conversation branches

FinalStand

Conversations are cumbersome to build since you need pre/post scripts for many branches. It could be simplified greatly by adding a simple variable to branches instead of full scripts.

Currently:

What color do you like?
* Red [script s_selected_red]
* Blue [script s_selected_blue]
* dozen more options and scripts
OK, you picked Green

But with variables, you could just set Color=Red, Blue, Green, Etc when a player selects a branch. Then at the end just have *one* script that pulls the variable they selected.


Generally, that is a very common use case in PWs. Just selecting something from a conversation. You just need one variable to tell what the user selected, not dozens on scripts, lol

Dark_Ansem

I second this.

Lex23

Agreed, this would be great, cut down on the most tedious parts of conversation-writing by a lot.

xorbaxian

+1
this is giant.
this functionality [and more] is already available w/nwnx_events, but it'd be cool to get it ootb.

Dark_Ansem

@JuliusBorisov maybe this one?

JuliusBorisov

https://trello.com/c/M04A179q/213-add-simple-variable-to-conversation-branches

dunahan

Would it be possible to get the spoken text and use one script to get to info we need (like SetListenPattern and so on)?
Didn't tried it with text from NSCs yet.

meaglyn

z-dialog is your friend.

dunahan

Ah, I did take a look at this. But didn't tested it yet. So, if this could be implemented in vanilla NWN:EE wouldn't it be much more helpful than only a simple variable?

Japualtah

z-dialog doesn't help, I don't get why it comes up every time we talk about this. And yes it's quite often.
z-dialog is just a token system, exactly what we want to avoid.
Only 15 votes on the trello though, not many scripters nowadays and even fewer reading the boards/trello.
You'll get much more support if asking for freaking portraits

meaglyn

z-dialog allows you to make conversations that do what you want. It does not help you put a variable in the conversation per se. You use it to write the whole conversation that you needed to use a variable for. It removes the need to pass the variable in the standard conversation nodes because you are scripting it all. It's more than just a token system. It can save you literally thousands of tiny starting conditional and action taken scripts.

Clearly you have not actually used it. It's exactly perfect for the kind of dialog FinalStand used in the example. One script for the whole thing, done

fot1

In other thread there is also discussion about how to pass data from the conversation to scripts. Since this thread is the one linked on trello, I just want to paste a link to the other ideas discussed there: https://forums.beamdog.com/discussion/comment/1035890/