Originally reported by: tryguy (Bitbucket: tryguy, GitHub: tryguy)

Hi, this may be related to the fact that I installed pre3 within Japanese mode (on win7), or it could not be related to that.

But, I've now put my locale back to English and tried again, and I can't see any of my pre-existing stories. It comes back with an error.

If I make a new story, it makes it and puts it in the correct directory, but if I exit and reload, it doesn't appear. (But it's still in the correct folder, so the actual stories are safe. They're just not showing up in library view).

• Bitbucket: https://bitbucket.org/klembot/twinejs/issue/203

I was trying to include some spiffy new components and found that the project is still on vue 1.0.18 (and the old vuex)

If I started this work, is there any interest in getting this merged? Is someone already doing this? Has someone tried and failed?

I'm starting work on this on my own fork and wanted to see if there was any traction here.

There's a bug that create duplicates of the same story; however, the duplicates have different progress on them. Whenever I try to edit a story, some of it is saved, and it is distributed between the duplicates. There is no one copy that holds all of my changes.

Twine version: 2.3.5

Originally reported by: Thomas M. Edwards (Bitbucket: tmedwards, GitHub: tmedwards)

Received an error upon startup.

Message: Failed to execute 'setItem' on 'Storage': Setting the value of 'twine-passages-4c3eb472-7213-4e46-bc46-839024f97fd0' exceeded the quota.
File: unknown
Line: unknown
Column: unknown
Stack: 
Error: Failed to execute 'setItem' on 'Storage': Setting the value of 'twine-passages-4c3eb472-7213-4e46-bc46-839024f97fd0' exceeded the quota. at Error (native) at Object.savePassage (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:1362:1051) at chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:1353:997 at Array.forEach (native) at chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:1353:964 at Object.update (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:1362:394) at Object.onMutation (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:1353:838) at chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:1320:6987 at Array.forEach (native) at o.value (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:1320:6900)

It seems to have been caused by a 5.4 MiB story.

• Bitbucket: https://bitbucket.org/klembot/twinejs/issue/269

I have a strange issue with Twine 2.3.0 for Windows. As soon as I test the project using the «Play» button, adding new passages with the «+Passage» button just stop working. It works only once, but the new passage replaces the starting one (although its content remains the same). And after that the button stops responding. I also cannot move passages, some UI elements are not responding either (can't press «Play» again, for example).

First, I made two simple links:

Then check it with the «Play» button. Then I add a new passage and see this:

This «Untitled passage» actually contains the text of previous starting passage, which he replaced: ...but links in it just don't work, as seen in the previous image. And this passage kinda «stuck» in place, it cannot be moved.

P.S. Sorry for my English, I hope I explained correctly. :)

Originally reported by: PeterLyberth (Bitbucket: PeterLyberth, GitHub: PeterLyberth)

After the latest update(2.10) I am unable to close the program without using the task manager. After closing the program using the TM, the stories are not present(they have not been saved from the previous writing session.

I have followed the guide regarding the closing issue present on on this bug tracker, but to no avail.

Any idea as to what the problem might be?

• Bitbucket: https://bitbucket.org/klembot/twinejs/issue/354

Originally reported by: Heitor Tremura (Bitbucket: Superechidna, GitHub: Superechidna)

Upon opening the Twine 2.1.0 program it displays only white inside the screen. It has been stuck like this for 5 minutes, and opening the program again simply opens the white screen. The last change I made that may have affected this is switching to the dark theme. I have tried restarting my computer to see if it was maybe a temporary issue but it remains.

I am currently running Windows 10 on a 64 bit system using the 64 bit version of Twine.

If there is something else I can provide to help recreate the issue, please let me know.

• Bitbucket: https://bitbucket.org/klembot/twinejs/issue/331

Originally reported by: Leon Arnott (Bitbucket: L, GitHub: Unknown)

The next version of Harlowe will have slight backwards-incompatibilities with the previous version, so I'm wondering how to communicate to present users that this new version is available, and whether their H1.0.1 stories should or should not be automatically promoted to use H2.0.0.

I think that, on upgrading to a new version (determined by saving a "last version opened" LocalStorage bit, I guess) and opening a story, a pop-up message over the story menu should appear, warning authors that a new version of Harlowe/Snowman is present, with both bugfixes and API changes, and they can switch to it now (if they haven't been upgraded automatically) or switch back to the previous version (if they have).

Ideally I'd like this to be in place in time for the next Harlowe version (which I'm working to get out within the next week or three).

• Bitbucket: https://bitbucket.org/klembot/twinejs/issue/124

Describe the bug.

Creating a link with a [[ ]] bracket markup will dynamically auto-generate a linked passage with the title of the link. Editing this link text will, every few seconds, automatically generate another new passage titled with the current name of the link, leaving the original passage present. This results in multiple unwanted new passages.

Steps to reproduce:

• Open a new passage.
• Type a link with double square bracket markup. E.g. [[TEST]]. This creates a linked passage called TEST.
• Without closing the passage editor, edit the link within the square bracket to [[TEST 2]]. After a second or so, the passage view refreshes with the new passage TEST 2. The TEST passage remains as an orphaned link.
• Further edits create further new passages and more orphaned passages.

Expected behavior:

Either auto-generated passages should be created only on closing the passage editor.

Or, possibly, the auto-generated linked passages should rename dynamically when the link text is edited.

Additional context on this problem.

I have replicated this issue on the Windows and browser version.

Twine version number

2.4.0

Does this problem occur with the web version of Twine or the desktop app?

Desktop app

What operating system does this problem occur on?

Windows

If this problem is occurring with the web version of Twine, what browser does it occur on?

No response

Presubmission checklist

• [ ] I am interested in working on code that would fix this bug. (This is not required to submit a bug report.)
• [X] I have done a search and believe that an issue does not already exist for this bug in the GitHub repository.
• [X] I have read and agree to abide by this project's Code of Conduct.

Originally reported by: John Tapsell (Bitbucket: john_tapsell, GitHub: Unknown)

I have placed a static non-twine html file "startingpage.html" in the Documents/Twine/Stories folder. It has nothing to do with Twine, and in Twine 2.0 it's been absolutely fine.

But when I launch the new Twine 2.1.0b5 beta, I immediately get:

TypeError: Cannot set property 'id' of undefined at IMPORT_STORY (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:41:19603) at i.(anonymous function) (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:91:5845) at r.value (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:91:4841) at dispatch (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:91:4102) at importStory (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:9:25334) at chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:48:10972 at chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:48:10861 at Object.loadAll (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:48:11018) at chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:60:31781 at Object.init (chrome-extension://jbeclgngiacjdjjokiegbkjcpibcdcic/twine.js:61:11)

At a guess, I moved the static html file out of the way, and that resolved the problem.

• Bitbucket: https://bitbucket.org/klembot/twinejs/issue/314

Originally reported by: furkle industries (Bitbucket: furkle, GitHub: furkle)

I've found that, in my large story, when I attempt to move large numbers of passages, some of the passages will end up moving correctly, and some will end up either not moving or moving to the wrong place, with the editor "forgetting" where they are and failing to redraw the connectors. I have a series of pictures depicting the issue.

before, ready to move:

after, successfully-moved passages:

after, failed-moved passages:

This is occurring on the stand-alone, non-web version, but I've been having similar issues since I was on the web version as well.

• Bitbucket: https://bitbucket.org/klembot/twinejs/issue/184

Description

Updated the german translation to be ready for Twine 2.6 as requested over the mailing list. Also changed a few wordings of some lines.

Credit

Please put an X in one of the squares below only.

[X] I would like to be credited in the application as: Julian Brehmer (I'm already credited so this can be skipped, thanks)
[ ] I would not like my name to appear in the application credits.

Presubmission Checklist

Put an X in the squares below to indicate you've done each step.

[X] I have read this project's CONTRIBUTING file and this PR follows the criteria laid out there.
[X] This contribution was created by me and I have the right to submit it under the GPL v3 license. (This is not a rights assignment.)
[X] I have read and agree to abide by this project's Code of Conduct.

Is your feature request related to a problem? Please describe.

I would love to see some more tools for organising passages in the editor.

I usually really like to plan out my story in blocks (separating it into space for chapters, utility passages for scripts, temp passages that i may come back to, or those that need some refining later) first and then flesh it out. This works in the beginning, but as the story grows, it gets somewhat confusing to manage and reorganise the whole workspace.

Describe the solution you'd like.

It would be great to be able to draw comment blocks in the workspace. They would be only for editing with a clear thick border and a title on top that we could edit for adding comments.

The main idea would be to replicate the behaviour of Comment Boxes in Unreal Engine blueprints editor. This should be an editor feature only. Just drawing an empty node, adding coment text to the title bar of it and allow to change its position and size.

That will be useful for story organisation, making easy to understand templates, reusing parts of the game

Additionally it could be extended in the future: make all nodes inside a block comment to be moved when you move around the group node itself, similar behaviour with copy&paste, etc.

Describe alternatives you've considered.

Other example would be Frame Node used in Blender 3D software. Documentation here. It is very similar to UE4 comment boxes but also has ability to change background colors.

Additional context on this suggestion.

No response

Presubmission checklist

• [ ] I am interested in working on code that would implement this feature request. (This is not required to submit a suggestion.)
• [X] I have done a search and believe that an issue does not already exist for this idea in the GitHub repository.
• [X] I have read and agree to abide by this project's Code of Conduct.

Describe the bug.

i have worked to long for my story for a assignment for school and then when i open twine POOF its gone please bring it back.

Steps to reproduce:

e

Expected behavior:

e

Additional context on this problem.

e

Twine version number

idk

Does this problem occur with the web version of Twine or the desktop app?

Web

What operating system does this problem occur on?

Other

If this problem is occurring with the web version of Twine, what browser does it occur on?

Chrome/Chromium

Presubmission checklist

• [X] I am interested in working on code that would fix this bug. (This is not required to submit a bug report.)
• [X] I have done a search and believe that an issue does not already exist for this bug in the GitHub repository.
• [X] I have read and agree to abide by this project's Code of Conduct.

Is your feature request related to a problem? Please describe.

Mac is continuously updating on its own in a way that sadly causes software to become obsolete or broken not infrequently. This is a tradeoff to continuously having security updates among other things (that's a whole other discussion) but so long as automatic updates are debatably one of the better ways to use Mac, software needs routine updates too.

I only use Twine a couple times a year, but I often dive into it not infrequently over the last half decade. Most of the time I have to manually update on Mac first. This takes away from how quick Twine is to jump into easily. It doesn't help that reinstalling Twine means giving permission again on Mac to open an "untrusted file" and jumping through hoops there too.

Describe the solution you'd like.

I would love to see Twine officially on the Mac App Store. Like iOS, this store supports Automatic Updates so that any time a developer changes their app to match new system requirements, the software itself silently updates to whatever the dev has done to match that. It makes life seamless for users even though it comes at the expense of developer time. It would be incredible if Twine had the option to download from the Mac App Store so that those of us who use twine consistently but infrequently can have a more seamless experience.

Describe alternatives you've considered.

Downloading Twine manually is not a huge hassle, but I do lose 10-20min every time that I first realize something odd is happening, search Google only to find inconsistent results, learn that it might be based on a Mac update, and then go and manually update the software myself, then undo Mac's protections to allow this one unsigned "new" software to be trusted again. That's possible, but usually my twine experiments are only 60min of development time to begin with, so spending 50% of that troubleshooting and reinstalling is no fun.

Another alternative is creating a custom shell script to automatically check for new Twine updates and installing Twine via Terminal instead. I could have the updates regularly, but it would take some time to make the script and it would not universally benefit the community. While a shell script can be shared online, it's much more obscure and would help only 1-10% as many people I imagine. A Mac App Store app would instead be more widely available not only to programmers, but to a more casual audience too. It could also increase Twine's accessibility to new audiences that wouldn't find it otherwise.

Additional context on this suggestion.

I have 100% fallen for the seamless Apple environment - that's definitely my bias here. But in a world where software updates happen more and more continuously over the years, I personally would prefer to see my favorite apps join in the mission to find a stable way to provide continuous seamless software updates and slowly whittle down the flaws with that approach instead of staying in the old manual system that might be a more known reliable, but doesn't come with the benefits of this new approach. I do think a world of continuous seamless software updates is more likely to be the future, and I'd love to see Twine more integrated into that.

Presubmission checklist

• [ ] I am interested in working on code that would implement this feature request. (This is not required to submit a suggestion.)
• [X] I have done a search and believe that an issue does not already exist for this idea in the GitHub repository.
• [X] I have read and agree to abide by this project's Code of Conduct.

Bumps express from 4.17.1 to 4.18.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps qs from 6.5.2 to 6.5.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.