tomkail
commented
1 year ago Hi! I’m afraid paths don’t work in the way you might hope; they also don’t get set immediately on loading a save state. This is more of an issue with ink than the Unity plugin. That said, I actually made a branch to try to fix this a while ago - check out “currentContainerPathString”. I can’t recall how robust it was but it seemed to work last I checked. You can also see the current path in the Ink Player Window when using it, handy for debugging.
On Wed, 19 Jul 2023 at 00:00, Paolo Pedercini @.***> wrote:
Hello everybody! Thank you so much for Ink (and inky). It's the best game making tool I've ever used and I'm building a big project around it. I've been banging my head against this bug or limitation. I don't know if it's due to ink or its Unity integration.
In some cases, after a story.continue() the path and the currentPointer are null, and there is no way to know where you are in the story, even if the story works fine.
Here's an example with nothing but debugging messages added to the Basic Demo. If you divert to a knot or a stitch made by a single line, the path is always null. If the knot is two lines, then the first line will have a path right after the continue. If the pointer is retrieved before the continue, it will be the id of the choice. Basically there is no state in which I get "c1" as pointer name or path. I understand that the path can be undefined if there are injections https://github.com/inkle/ink-unity-integration/issues/38#issuecomment-326230174 but this doesn't seem the case. It obviously knows where it is, but I guess something in the stack order overwrites the path before I can read it or waits to write it until the second line. Is there any workaround, any way to retrieve it?
[image: nullpath ink] https://user-images.githubusercontent.com/12369651/254411506-017a876b-0512-459a-8eb3-86b0ff8e1c21.png
— Reply to this email directly, view it on GitHub https://github.com/inkle/ink-unity-integration/issues/189, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJR3UACDXWLPJRVD6JOAR3XQ4BP7ANCNFSM6AAAAAA2PAITOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
molleindustria
Hello everybody! Thank you so much for Ink (and inky). It's the best game making tool I've ever used and I'm building a big project around it. I've been banging my head against this bug or limitation. I don't know if it's due to ink or its Unity integration.
In some cases, after a story.continue() the path and the currentPointer are null, and there is no way to know where you are in the story, even if the story works fine.
Here's an example with nothing but debugging messages added to the Basic Demo. If you divert to a knot or a stitch made by a single line, the path is always null. If the knot is two lines, then the first line will have a path right after the continue. If the pointer is retrieved before the continue, it will be the id of the choice. Basically there is no state in which I get "c1" as pointer name or path. I understand that the path can be undefined if there are injections but this doesn't seem to be the case. It obviously knows where it is, but I guess something in the stack order overwrites the path before I can read it or waits to write it until the second line. Is there any workaround, any way to retrieve it?