but when I copy and paste this *exact* example into a passage the new passage it links to is named wrong: http://i.imgur.com/D697KUX.png
OK to answer your specific question, this is a Twine 2 issue where the automatically created passages are messing up the passage name.
Create the passage first, then link to it. Don't rely on Twine to create the passage for you. Alternatively just rename your passage to the proper name of Grocery and everything should be fine.
So even after re-naming it appears to work but not visually "link" or update the passage with the correct title.
Creating the passage first doesn't fix it either unfortunately.
The first issue is a Twine issue, not Sugarcube. Twine only draws arrows via standard links and not any other code. It doesn't otherwise affect the story. I'm not sure what you mean by the second issue. How does it not update the passage title after renaming?
This last shot is taken *after* updating that auto-created passage. So any manipulation of the auto-created passage fails to appear on the main view screen.
If i delete the auto-created passage and create my own passage "Grocery" the story works fine, but if I ever edit the original passage (just open it and close it again) It turns red because it thinks there's a broken link.
I guess I"ll just work in Harlowe instead, though I really wanted to use Sugarcube. Do you know when this might be fixed?
Edit: Holy crap this bug has been in there since Jan? I guess Sugarcube isn't being supported at all. Back to Harlowe it is. That's disappointing, since I really like having the save and sidebar features of Sugarcube.
Edit: Holy crap this bug has been in there since Jan? I guess Sugarcube isn't being supported at all. Back to Harlowe it is. That's disappointing, since I really like having the save and sidebar features of Sugarcube.
It depends on what you mean.
If you mean SugarCube itself, then that's simply not true. Regardless of how most would classify the support that SugarCube receives (I'd like to think that it has fairly good support), it certainly is supported.
If you mean the bug in Twine 2 (and it is a bug in Twine 2, not SugarCube), then yes, I suppose it's fair to say that Twine 2 is somewhat lacking in the support department.
Edit: Holy crap this bug has been in there since Jan? I guess Sugarcube isn't being supported at all. Back to Harlowe it is. That's disappointing, since I really like having the save and sidebar features of Sugarcube.
You cannot expect story format developers to solve general bugs in the Twine 2 app. The bugs you describe have little to do with SugarCube. Harlowe has the same issues when you try to do things that will similarly trigger this bug.
Also remember that there are only a few situations where you absolutely need to use setter links. You can also use other tools like PassageReady to do this sort of thing, or simply put the <<set>> command in the new passage if appropriate.
If someone could up vote for me for fixing this, that would be awesome. I've already got too many accounts and signing up for another one just to add a vote to get this one done is a bit much. Thanks to those talking about workarounds, but a fix would be ideal. Otherwise, my maps turn to spaghetti and I only want that for eating and for my westerns.
Comments
OK to answer your specific question, this is a Twine 2 issue where the automatically created passages are messing up the passage name.
Create the passage first, then link to it. Don't rely on Twine to create the passage for you. Alternatively just rename your passage to the proper name of Grocery and everything should be fine.
Creating the passage first doesn't fix it either unfortunately.
I submitted a bug report on the Sugarcube source repository.
The first issue is a Twine issue, not Sugarcube. Twine only draws arrows via standard links and not any other code. It doesn't otherwise affect the story. I'm not sure what you mean by the second issue. How does it not update the passage title after renaming?
Starting by creating one passage with the complex link: http://i.imgur.com/6XTJXNa.png
It creates the wrong passage title. I go and edit the title: http://i.imgur.com/lOovz9D.png
Then when I exit the passage title on the tree is not updated:
http://i.imgur.com/2AMQRlp.png
This last shot is taken *after* updating that auto-created passage. So any manipulation of the auto-created passage fails to appear on the main view screen.
If i delete the auto-created passage and create my own passage "Grocery" the story works fine, but if I ever edit the original passage (just open it and close it again) It turns red because it thinks there's a broken link.
I guess I"ll just work in Harlowe instead, though I really wanted to use Sugarcube. Do you know when this might be fixed?
Edit: Found the issue alread submitted on the Twine bitbucket: https://bitbucket.org/klembot/twinejs/issues/104/setter-link-syntax-is-not-recognized-by
Edit: Holy crap this bug has been in there since Jan? I guess Sugarcube isn't being supported at all. Back to Harlowe it is. That's disappointing, since I really like having the save and sidebar features of Sugarcube.
If you mean SugarCube itself, then that's simply not true. Regardless of how most would classify the support that SugarCube receives (I'd like to think that it has fairly good support), it certainly is supported.
If you mean the bug in Twine 2 (and it is a bug in Twine 2, not SugarCube), then yes, I suppose it's fair to say that Twine 2 is somewhat lacking in the support department.
Look at this link if you want evidence of SugarCube's support: http://twinery.org/forum/discussion/1486/sugarcube-releases#latest
You cannot expect story format developers to solve general bugs in the Twine 2 app. The bugs you describe have little to do with SugarCube. Harlowe has the same issues when you try to do things that will similarly trigger this bug.
Also remember that there are only a few situations where you absolutely need to use setter links. You can also use other tools like PassageReady to do this sort of thing, or simply put the <<set>> command in the new passage if appropriate.