Qynari - Development Progress

An update on some of the issues/feedback that has been reported. Note that there is a feedback button in the site header to send quick feedback directly to us, and that’s usually the best way to report simple bugs/ui issues etc. - but I’m also happy to have more involved discussions here, just reply to this thread.

  • @jwalrus Regarding the technical documentation - it’s not comprehensive docs but I’ve added an article listing the basic features.
  • @sparkletwist We discussed the anonymous-editor options but decided against it for now, since it would add too many edge-cases, educating about the limitations, garbage-collection on media storage, disabling of some features like collaboration and dead-end-suggestions… registration also acts as a filter for users who aren’t likely to actually play/use/engage.
  • Re. flickering reports: I’ve now seen this, someone sent me a video of it happening in Safari. It seems to work fine in Chrome/Brave, but I obviously need to do wider browser-testing and look into this specifically. Also it gave me an idea to add explicit scene-transitions, so the creator can have more control over that (which will become more relevant when we add looping background video/audio).
1 Like

I’ve added two more templates that show:

  • How to use Jump Nodes to keep your story organised on the canvas.
  • How to use conditional-availability on intents to create a dynamic menu based on variables/conditions.

The new conditional intents feature is the main thing that’s been added, but also I’ve done a lot of quality-of-life improvements, UI consistency, reorderable intents, fix rubber-banding when moving a large multi-select of items around the canvas… that sort of thing. Enjoy.