Optional responses

[Magodra]

Hi,

I would like to have different lists of responses depending on quest states.

With this solution the response is enabled/disabled, and currently the best setup found so far.

Smith: Hello
- Response 1 => response_1
- Response 2 => response_2
- Quest Response for available quest [if is_quest_available("quest")] => quest_available_response
- Quest Response for active quest [if is_quest_active("quest")] => quest_active_response
- Godbye => END

I would rather have the responses not applicable removed from the list. Tried some variants of if statement, but all combinations seams to not keep the list of responses inteact. Might this be before off the different indentation level or something else? It ends up with Godbye not beeing included, in the list of responses.

Smith: Hello
- Response 1 => response_1
- Response 2 => response_2
if is_quest_available("quest")
    - Quest Response for available quest => quest_available_response
if is_quest_active("quest")
    - Quest Response for active quest => quest_active_response
- Godbye => END

[Fireye04]

Ah yeah I'm not fully happy with the state of response conditions at the moment (You can't have both hidden and disabled responses on the same object without tag shenanigans) HOWEVER, assuming you don't need to have disabled responses as well, this should be doable.

In your balloon there should be a dialogueResponsesMenu node that contains the following "hide_failed_responses" boolean:

godot_dialogue_manager/addons/dialogue_manager/dialogue_responses_menu.gd

Line 27 in ecc8e3b

@export var hide_failed_responses: bool = false

Toggling this to true will make responses with failed conditions hidden rather than disabled.

[Magodra]

Yes, that works good as an global filter to hide failed responses.

In case both hidden and disabled responses should be an option, would it be an option to allow the condition on the response to be marked as forced filtered (Or something like this)? Like the goto that use ! to alter the behaviour, the outcom of the condition could be handled different. Something like this:

Smith: Hello
- Response 1 => response_1
- Quest Response for available quest [if is_quest_available("quest")]! => quest_available_response

Parsing could add this as a flag is_forced_filtered (Or something similar) that would end up on the DialogueResponce in parallell with the is_allowed flag.

In the Dialogue Respose menu the filtering could be extended to either filter on the global flag or the forced filter flag:

if (hide_failed_responses and not response.is_allowed) or (response.is_forced_filtered and not response.is_allowed): continue

[Fireye04]

Just checked (ADHD whoops) & I did try adding something similar awhile back but got rejected in favor of a tag solution. #983

The tags solve the basis of this, but the main value of this kind of feature would be the seperatie condition evaluation in addition to the simple is_allowed. Eg:

A && B - shown, selectable
A && !B - shown, not selectable
!A && B - not shown
!A && !B - not shown

With just one condition this type of dynamic behavior can't exist without significant workarounds.

[Magodra]

True, the one condition will only be able select between shown and not shown. A second conditon will then be needed to select between selectable and not selectable (This is currently done through enabling or disabling the control based on the is_allowed).