Pixel Crushers Forum

Version 2.2.12 of the Dialogue System for Unity is now available on the Asset Store.

In addition to several improvements and bug fixes, this version has additional starter UI prefabs and some handy new utility windows, such as a Variable Viewer popout window that you can use to manage variables and watch their values at runtime. It's super handy to have it open alongside the Dialogue Editor window or while you're playtesting in play mode. The Dialogue Editor's Variables section can now also collapse grouped variables in foldouts by group, helping keep the lists more manageable.


Release Notes

Core:

• CHANGED: Deprecated dialogue UI prefabs have been moved out of the Dialogue System. They are available on the Dialogue System Extras page.
• Changed: Dialogue System Trigger's Start Conversation > Skip If No Valid Entries checkbox now defaults to false.
• Added: Variable Viewer utility window.
• Added: Variable Renamer utility window.
• Added: SMS style, Nuke, Computer, Old School dialogue UI prefabs.
• Improved: Lua wizards now provide shortcut to add new variable.
• Improved: Dialogue Editor Variables tab now has option to collapse variable group foldouts.
• Improved: Conversation properties can now override cancel subtitle/conversation inputs.
• Improved: Sequencer commands can now find inactive GameObjects by tag.
• Improved: Added C# method to set current selection in Selector.
• Improved: Updated DemoScene1 computer terminal to demonstrate world space dialogue UI.
• Improved: If dialogue UI instantiates missing EventSystem and using new Input System, now adds InputSystemUIInputModule.
• Improved: If editing an auto-backup database instead of the original, database name watermark will be bright red.
• Fixed: Bug with Delay() sequencer command when Dialogue System Trigger's Pause Game During Conversation was ticked.
• Fixed: SetDialoguePanel() didn't re-show continue button if it was previously visible.
• Fixed: Warm Up Conversation Controller with certain UIs would briefly show UI at start.
• Fixed: Sequence field Check button now allows sequences containing only a {{shortcut}} to pass.
• Fixed: Bug in SimStatus if loading saved game containing different SimStatus values for the most recent conversation and then playing same conversation.
• Fixed: If including invalid responses, [auto] tag now doesn't auto-select invalid responses.
• Fixed: QuestState fields can now be set to grantable at design time.
• Fixed: Automatic explicit response button navigation now bypasses non-interactable buttons.
• Fixed: Updated input field UIs in several example prefabs.
• Save System: Fixed potential timing issue with AutoSaveLoad and DiskSavedGameDataStorer.

Third Party Support:

• Action-RPG Starter Kit: Updated for 6.55b.
• Adventure Creator: Updated for 1.72.
• articy:draft: Fixed actor assignments for certain "decorator" nodes (jumps, pins, etc.).
• Opsive Controllers: Updated to allow specifying item collection by name; save min & max attribute values; save non-slot items.
• ORK: Added ORKGetQuestStatus() Lua function.
• PlayMaker: Added Bark action option to specify text instead of conversation.

I have a lot of variables so I'm very interested in this Group Foldout feature that was just added.

I have a number of variables that are named Group/VariableName but there are no foldouts showing up even after checking the menu item. How am I supposed to get the variables into groups so the foldouts can work their magic?

I'll add that in version 2.3 (which I'm working on). Currently if your variables have a period ( . ) then the part before the period will be treated as a group. I acknowledge that this isn't consistent with conversation titles and quest names. This was done because slashes in variable names were causing new users some confusion because they're translated to underscores ( _ ) in Lua.

BTW, version 2.2.12 also has a variable renamer utility. This utility will rename a variable in all dialogue databases, prefabs, and scenes in your project. In prefabs and scenes, it will rename variables that are used in Lua code in Dialogue System Triggers' Conditions and Run Lua Code fields, and in Increment On Destroy components.