Blueprint Dialogue System

[Brum]

@Grogger;387009

Upcoming Update:
I have finalized the changes and testing for v1.2 of the Blueprint Dialogue System and have submitted it to Epic for updating. I will update this post and the front page when it has been updated.

v1.2 Changelog:

General Changes:

• Upgraded the project to 4.9
• Improved Use Scanner performance

New Features:

• Added a new Mouse Use Scanner for cursor interaction
• Added SetSpeakerId script function to allow changing the name and portrait inline. It can also be used in the prescript column (this can be useful if there is a conditional statement to set the speaker id).
• Added gamepad support and input type switching. The default is Mouse and Keyboard and it can be changed at runtime or in editor
• Added Unmanaged input mode support to allow external input management (eg. Showing/hiding mouse cursor, setting the Input mode, managing key-binding, etc…).
• Added a new convenience operator ‘>>’ to easily create multiple branch partitions in a single row in the data table (eg. “This is branch one >> This is branch two >> This is branch three”) . The sample has been updated to demonstrate this.

[INDENT]Note: to display >> in the text, use the escape character: >>
Note2: Pre actions will run before the first partition, and Post actions run only at the end of the last partition.

Fixes:

• Fixed an issue that would cause the system to lock up all player input if the Close function was not called and no valid branches were provided.
• Fixed SetSpeakerPortrait to be usable from the PreScript column
• Fixed escape character '' being printed for text and responses (to print a backslash, use two. Eg. \ displays one )
• Fixed a bug that wouldn’t find variables at the beginning of a text line

Documentation:

• Added information about gamepad controllers in F.A.Q
• Added information about the New Page operator >> in F.A.Q
• SetSpeakerId function docs
• Added a section for Speaker Attributes (portraits/names)

[/INDENT]

I have attached to this post the gritty details of the update for those who have edited the core files (avoid doing this if possible).

Glorious! Really looking forward to it. Regarding the bug, i’ll ask one of the programmers that found out and will report as soon as I know :).

Question though: is it easy to update an existing project with the update?