itch.io

Hello! Thanks for the feedback! I’ve logged these into: https://community.drafft.dev/tags/feature-request

• A customizable database: This has been brought before, while I don’t personally like the visual form approach I will consider it if there is enough interest. Having said that, I’m working on a better grid section, which will support more data types and images. It is not the same as you are asking as we don’t have support for nested properties (its just a 2d grid). In parallel we have this idea for “template”. It’s not very defined yet though: https://community.drafft.dev/questions/D1O2/template-system

• small diagram/flowchart maker I like this! I’ve added to the backlog for when I finish porting all the missing v1 editors.

• Zoom bug: I’ve noticed it too, something related about the available space changing. Added to the backlog

Thanks for your inputs!

Thank you for testing! Interesting… now I’m a bit lost why its not working on the app for you! Will do some test and get back,

Thanks for your help!

Beta available here: https://drafft.dev

No worries! If you can, just open the link and press shift+c and see if the content change to “MODAL CONTENT”

Thank you!

Hey thanks for the suggestions! I wrote a really long reply but lost it when I click a link …

• The edit toggle suggestion is great! I also considering moving that to the tabs toolbar: https://community.drafft.dev/questions/D1y2/fr-move-the-whole-lock-save-undo-area-to-the-actual-tab-toolbar

• +1 to everything! logged it here: https://community.drafft.dev/questions/D1z2/fr-dialogue-tree-0-0-indicator-and-a-button-to-re-center-the-graph

• The status bar idea is great, it could trigger the info panel (which I plan to overhaul in the future with comments, custom metadata, etc) did you found that? its “Show info panel button” in the toolbars

Loved the background concept! I guess it could be quite easy to implement via css and a file url.

yes, the primary color is an issue if the user uses a light color, maybe I should expose a “foreground color” picker as well.

I will keep the logo color idea, could look really nice!

Great suggestions, thanks for taking the time to write!

yes! next priority is the todo and items! I might spend some time on it to provide a better experience, if you have feedback/suggestions please let me know!

If you have time, could you try this example, and see if it works on your end? (or any shift key example in the page)

https://react-hotkeys-hook.vercel.app/docs/documentation/useHotkeys/basic-usage#keystrokes

thanks!

Great thanks for confirming! The dangling activation is a side effect for a fixed bug in v12. You can manage your activation here: https://app.lemonsqueezy.com/my-orders/ or let me know your email and I can do it. (can reach me via support@drafft.dev)

Thank you!

thanks! could you try v.11? I added a missing dependency. this is x64 right?

Hello Ether, thanks for the feedback and taking the time to reply!

1. Thanks for bringing this to my attention, email should be working now! I’m fine with keeping this place on itch.io but as the store has moved away it feels a bit… wrong! Still testing the community platform (apache answer) so it might not be a good fit, or maybe yes :)

2. Shortcuts: Strange! I’ll investigate, I think it might be related to the keyboard code for shift as seems like ctrl+p is working for you, have you tried left vs right shift?

3. I think that is a good Idea! I will see how crowded it looks, but it should be visible on node selected only so it should be fine, added to the backlog!

4. Docs: yes! I need to spend some time on docs. But for now I’m prioritizing bugs and hopefully bring the other editors from v1.

Thanks again !

I think I have a clue on what this is, there are some reports involving a username with long/special characters https://github.com/electron-userland/electron-builder/issues/6865 questions:

• can you run the uninstaller manually in: C:\users\youruser\AppData\Local\Programs\drafft?
• if it fails, can you delete the uninstaller file and try again?
• if it still fails, v2.0.9 uses the old name “drafft” without space, which might be the reason its not working, vould you try that?

Thank you!

Hello, thanks for reporting! I think I have a clue of what this is about, can you share info about your distro/architecture?

Thanks!

Hello! We do have yarn syntax highlighting for scripts but that’s all. That would mean that you won’t have dialogue trees out from the source text nor speech identification if you use their syntax.also the source text won’t covert to dialogue trees

Having said that, you could write and store your source files without issues. you will have to do the parsing outside of course, the app will give you a json file (or basic JSON api)

The demo is unrestricted do feel free to experiment with it!

I like this idea. Global variables. So when the document is in view mode it shows the value? In edit mode shows the real $variablename?

What about game export,I guess we render each var.

I think the idea of multiple .env files is also nice… Like a $(prod.server) or $(player.name) where prod and player are different .env files.

Maybe the misc collection can be upgraded to a metadata collection where we can have a customizable list of documents that can be directly accessed via this specific syntax. Like meta.env.xx or meta.menu.startgame etc etc… Or… Maybe this syntax is a shorthand for displaying any value of any document of any collection. Similar to the new picker feature , but it could target any prop.

$(items.sword-01.description) or $(actors.kenji.properties.height) or even $(script.script-1.modifiedDate)

This would give items/misc/quest a whole new value specially when used in god/scripts.

The main issue is finding a good typeable name as the name is not unique and the id is quite long. Maybe the doc alias should be user editable.

Great idea!

Thanks Alex! Hopefully I’ll have the beta version ready to download soon.

Hello! do get any error message?

Thanks, I was actually working on this yesterday! great suggestions!

• Grid snapping
• New nodes
• Notes on every nodes + a “notes” node
• customizable input/outputs for every node.

Sorry, missed this! Unfortunately, I cannot support Ipad (or android) as I rely on electron which doesn’t support it.

hm this issue leads me to apparmour profile again and also a strange case where the appimage has a space in the path.

do you have any space in your path? https://github.com/electron/electron/issues/44414 https://github.com/electron/electron/issues/41066

BTW: Electron builder 26 which have apparmour support/fix will be stable soon apparently.

Sad to hear about the flood damage! Hope everything is ok! I’ll set a docker compose and add it to the documentation as the “official” setup.

I’m not sure about your environment (are you running Debian?), bu maybe you can try:

Possible Solutions

1. Run with No Sandbox (Quick Fix): ./drafft-appimagefile --no-sandbox
2. Use the –disable-setuid-sandbox Flag: ./drafft-appimagefile –disable-setuid-sandbox

Or this? https://authmane512.medium.com/solve-the-suid-sandbox-helper-binary-was-found-but-is-not-configured-correctly-3-solutions-4f1425a9a76c

I got you. I think it makes sense! I’m actually adding a notes/comments panel on every document in v2 (no matter what type of doc it is) so it’s actually developer notes instead of content. This might be also useful on multiuser setup with the potential of becoming some sort of comment/review thing in the future

Hello! Can you explain a little bit more? You mean the line numbers in the scripts?

this might be trickier than it sounds! do other apps resize as well for you?

Hello, unfortunately not!

hey did you ended up creating a docker compose after all?

Thanks! I get what you mean, and I will definitely try to add something in the future, once I get this v2 stable. My take is that we want to have some sort of “idea tracking” utils: mind-maps, storyboards, moodboards, scratchpads or a combination of those.

About the tabs: v2 does not have split layout (yet?) but we do have full multi tab support and I thinks it is a huge step up:

Thanks for the feedback! great suggestions!

• Grid snapping. +1

• sub-graph node (or grouped node with it’s own input and output), (+1)

• comment node (or note). (+1)

• Scripts: Repeatable properties should be easier to input. – Yes, have autocomplete for actors and commands in scripts. I’m considering some sort of template system for the other editors

• More node types like purpose node, condition node, random node (for success rate), trigger node (link to quest for event trigger).

About the last bit, how would differ with the script node? I wouldn’t want to try to cover all the possible nodes logic, and should be implemented by the user. Maybe some sort of node labeling for the common script node?

Thanks for the feedback! git support is a bit of challenge, but I’m always thinking about it. In parallel I’m thinking of offering some sort of hosted db offering.

Thanks as usual for the feedback!

In v2 we have a registered protocol drafft:// which is used by internal links and the app will use them to route to a document if it founds it. this has the benefit of being used even outside the app, (a chat message for example – need to test it in different platforms yet)

so drafft://scripts/script-unique-id will focus the app, create a new tab, load that document on it, and focus that tab.

this is also usable in gdds (with a nice ui picker) to link between differt documents

New endpoints are a great idea, add it to the wishlist.

This is a great suggestion! I want to integrate some sort of (very basic) sketch thing as well

Thank you again!

Yes I can see the issue, in my case, in arch, I use appImageLauncher which conveniently moves the .Appimage into a specific folder and “integrate it” into the system. But I agree this goes against the appimage portable principle :)

I took the liberty of using your explanation (with credits) on the new website (wip) , hope its ok! https://drafft.dev/docs/troubleshooting/app-armour-issues

Thanks for the info! It seems that it might get solved in newer builder version. Will try! https://github.com/electron-userland/electron-builder/issues/8635

Hello! Well I need to start building new pipelines for v2 quite soon. so I can definitely give this a shot, and snap as well. They seems to be supported on electron builder . Added to the backlog! Thanks for the suggestion!

Welcome to the Drafft v2 discussion thread!

This is the place to share your thoughts, ideas, and feedback as we work on shaping the next version of Drafft. Here’s what you can do here:

• Discuss key features like Scripts, Dialogue, and Game Design Documents (GDD).
• Share your wishlist for new features or improvements.
• Provide feedback on what you’d like to see in the alpha release.
• Share your thoughts on potential AI integration and how it could enhance Drafft.

Your input is invaluable in helping us make Drafft v2 the best it can be. Feel free to share your feedback publicly in this thread or reach out privately

Update 2025: Thank you everyone for sharing feedback here and via email.

Here is the new website: https://drafft.dev/ and x profile https://x.com/DrafftApp where I will also share development progress. You can join the waitlist for v2 beta there as well.

v2 is taking shape, still deciding on licensing and feature set, but it will be free forever for all v1 owners before launch.

Key Themes from User Feedback:

• Dialogue trees, scripts and GDD are considered the most important features. Others are nice to have.
• Collaboration: some friction on the diy collaboration aspect, hosting server, etc. Many users struggle with the current server setup and want easier collaboration options (e.g., Git integration, cloud syncing, hosted offerings).
• Most users do not want AI integration
• Quality of Life additions, like better undo, manual saving, better hotkeys, autocomplete
• Better docs.

Hello! Are you referring to couchdb right?

The easiest way is to just run the container as stated the docs:

docker run -p 5984:5984 -d couchdb:2.3.1

then you can access it via the web: http://localhost:5984/_utils/

I always run it like that. I don’t have a docker compose, but creating it should be quite easy, found this online, maybe you can use it as a guide?

Also note that there is a new version 3 that requires to set up a user and password before running the container

*************************************************************
ERROR: CouchDB 3.0+ will no longer run in "Admin Party"
       mode. You *MUST* specify an admin user and
       password, either via your own .ini file mapped
       into the container at /opt/couchdb/etc/local.ini
       or inside /opt/couchdb/etc/local.d, or with
       "-e COUCHDB_USER=admin -e COUCHDB_PASSWORD=password"
       to set it via "docker run".
*************************************************************

hope it helps!

Hello There! Thanks for the feedback, means a lot!! I wish I had better news for v2 but I have lost a bit devlopment momentum. Won’t reach the initial eoy idea. Feel free to leave ideas/bugs/pain points though!

Hello! Thanks for the idea, it was supported but not exposed in the UI. It is now available in v1.4.5

Hello there, thanks for the interest! I’m quite happy on how the development has progressed so far, but unfortunately it is a bit delayed at the moment due to life events. I would love to have something before eoy, at least a minimal version. But I cannot commit to any date.

Thanks for chiming in and the support!

I agree on the list view approach. However I wouldn’t be able to provide a full featured task management. I think having a list view complementary to the Kanban view would be quite useful indeed.

Hello, first of all, thanks for taking the time to test and leave very useful feedback! Really appreciated, I’ll try to reply below on some of your topics.

• Team License: everyone on the team can try the demo, which is fully functional, for as long as they want without issues until you decide if it fits your workflow or not.
• Timelines: Honestly, I’m considering removing timelines for v2 as they are poorly implemented and might be redundant with the node based dialogue tree. (which is far more powerful), alternatively I’m also peeking at some libraries like this or this
• Improved Markdown editor: This will be the new editor in v2 which I think will cover most of the writing needs. I also added better image support and internal document linking. However v2 is taking a bit of time…
• Sortable list of projects: Good idea! Added to the backlog.
• Backup: You can backup the whole database of a project as a json file with the “Backup database” action, or just the game content with “Export game content”. The whole app data lives inside %appdata%/drafft or ~/.config/drafft folder. Although there is no supported or easy way to use that folder as a backup. Its better to use the previously named options. There is also the “Auto Export Project Backup “ to save a fresh db backup when loading a project. You can also get a db-dump via the basic API
• Version control: this is tricky, as the database lives in the ‘browser’ as an in-memory database (not file based). However I have an idea on how to make a ‘semi portable’ version. this will DISABLE the real time editing benefits of course.
• Better Task management: Big fan of ClickUp here! As much as I’d love to see a full featured task management with @mentions @assignees, notifications and the usual goodies we should expect from it, I’m afraid it would be a big effort to implement correctly, especially in this “self hosted” approach. What I will consider is to add a “list-based” basic task manager (emphasis on BASIC) to complement the Kanban view.
• Streaming/recording: go for it! Also, if you have useful clips to share I would love to watch/link them on the site.

Also thanks for the support and recommendation!