lykanthrope wrote:I'm super excited that you're going to be supporting Ink, but I have a few questions regarding the integration of it. In the example file, neither story fully display the contents of their associated ink files. It's especially missing large segments with The Intercept.
It most definitely seems broken in Unity 2017.2. It works in Unity 5.6.0. I'll figure out what in Unity 2017.2 broke the integration and post a fix this week.
lykanthrope wrote:Also can Ink be injected into the CYOA Framework fairly easily? Or the Lifeline Extension?
It would take a bit of extra scripting. Currently the Dialogue System / Ink integration doesn't provide an easy way to jump back into a conversation at a savepoint in that conversation. I'll see if I can get this into the update, too.
The Dialogue System Extras page has an updated Ink Support package that works in Unity 5.6.0 - Unity 2017.2.
I should clarify a bit on saving, loading, and jumping back into conversations. The Dialogue System Ink Integration component does save the current state of all stories that you've assigned to its Ink JSON Assets list.
The Lineline Extension would require some small changes: disable the Remember Current Dialogue Entry and add a short script to manually restart the main conversation when loading a saved game.
But the CYOA Framework works without any script changes. Here are the steps I used to test it:
Imported Dialogue System, Ink Integration, and CYOA Framework.
Added Title and Story scenes to build settings.
In Title scene, changed Story Manager's Story Conversation to 'story' in lowercase so it matches JSON file.
Added Dialogue System Ink Integration component to Dialogue Manager.
Added the example 'story' JSON file to Ink JSON Assets.
Made sure Reset State On Conversation Start is UNticked and Include In Save Data is ticked.
Assigned Ink Example Database to Dialogue Manager's Initial Database field. This contains a quest that 'story' activates.
