What feedback helps

Any feedback helps. A few things make it much easier to act on.

The most useful things

• What you were trying to do. “I wanted to move a scene to the end of act one” tells us more than “drag doesn’t work”.
• What you expected, and what happened instead.
• The steps, if you can make it happen again. “It happened once” is still worth telling us.
• Where you got stuck, guessed, or had to look something up. These are the rough edges we can’t see ourselves.
• Your version and system. About Cold Open ▸ Copy version info copies them. Report a problem… fills them in for you.

Files and scripts

• Never send a script you don’t own, even a draft you were sent. Scripts are copyrighted, and issues are public.
• Write a short scene of your own that shows the problem. A few lines that go wrong are better than a whole script.
• For an .fdx that won’t open or saves wrong, send the output of coldopen repair your-script.fdx copy.fdx --json. It lists what was wrong by code and position, and holds no script text.
• Screenshots help with how something looks. Crop out anything private or copyrighted.

Crashes

If Cold Open crashed, the next start offers its crash report. Look at it, then Send on GitHub or Send with the form, and paste the report into the page that opens. It holds no script text. Tell us what you were doing when it happened, if you remember.

Ideas

Tell us the problem before the solution: “I can’t see which scenes are night scenes” lets us find the best answer, and maybe one you’d like better than your first idea.

What’s less helpful

• “It’s slow”, with nothing more. Which action, on what computer, with how long a script? Measure performance in the palette gives us numbers.
• Long lists of things another app does. Tell us which ones you’d miss most, and why.

Thank you for taking the time.