itch.io

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!

Hello bojjenclon,

For the import process, so far most of the data works. The main idea on not “supporting” V1 is not to worry about backwards compatibility when adding more features. But I guess we will need some sort of “migration plan”. Unfortunately life got in the way so V2 is taking some time…

About the portable project, this is something I’ve been thinking for some time. The main problem with this is that the current database lives in the browser and we would have to “dump” it to have it in a file. I have A few ideas but not quite solid as a solution. Maybe… the db gets ‘dumped’ to a file by default on project/app close. And a special flag on each project like “auto import from dump” would do this reimport thing automatically on load. Git operations like pull/push/merge would be responsabily of the user outside of the scope of the app . This would make a project also work on a file share or Dropbox-like app. Thanks for the feedback!

Hello, glad to hear that you found it! For anyone else with this doubt in the future: there are zoom options at the lower right corner of the screen.

Hello, sorry to hear you are having issues.

I agree the software might not be for everyone, that’s why I decided to offer a full featured free demo, a shame you couldn’t try it beforehand. I think you can file a refund request on itch.io : https://itch.io/t/129454/how-are-refunds-handled

About the issues:

• There was a bug with import json into new project that it fixed now in v1.4.4. On 1.4.3 you can create an empty project and restore the project into that. (should be available for download soon)

• Make sure you are importing the json file, this was an issue for another user here

• Documentation is lacking, but we have a quick start here: https://drafft.aboni.dev/en/docs/documentation/quick_start.html

Also, I wouldn’t expect this app to provide the same level of features/polish of trello/gdocs!

Thanks for the feedback!

Hello! this is solved in 1.4.4, thanks for reporting!

Hello, search works for scripts only for now. Added to the backlog! Thanks!

Thanks for the support!!!

You can have a quick read about the branching dialogue tree here: https://drafft.aboni.dev/en/docs/documentation/quick_start.html#dialogues

It might give you some ideas.

Hello!

Thanks for the report, I can confirm about the edit bug in the timeline, it should serialize like the other actions when editing.

Honestly the whole timeline section is quite old, and might need a revamp/sunset, maybe its better/easier to use the branching tree which can have attached scripts and better ux…

About the folder, yes, Also if you have a document (not a folder) selected the new file/folder will be a sibling to that.

Thanks everyone for reporting. The issue is fixed in 1.4.3

Hi, can you give me more details about the issue? You need to use “Backup Database” to open the project in another machine

Hi! do you export with “Export Game Content” ? If so, you need to use “Backup Database” instead. The Export game content just export a json file intended to be used in the game engine. Let me know!

Hello, Hard to say really! My idea is to release on mid 2024, but I cannot commit to a date.

thanks! is there a possibility that both users have the same username?

Hello, hm this is strange, so you have a file locked, and when the app syncs it overrides those changes with old version? does this happen always? when you say sync, its the initial sync setup you do as a user, or the sync that the app does in the background?

Hello Thanks for the report, can confirm and logged it. Will fix in next release! Thanks!

Hi! the implementation is up to the developer, the app will only output a JSON file, or could be queried via a rest API. So the I guess the answer to the question is none, but can potentially work with any engine.

Not really, unfortunately life got in the way. But it is the first thing I’m fixing when I can get back at it. There is something wrong about the db attachments / electron builder / windows

Hello Olly,

Did you try the zoom options? (on the lower right) It should make the fonts bigger as well.

Hi! Actually I had a regression with that as I’m not very happy with the markdown editor and going back and forth with some tests. In essence I’m stuck now in deciding if the attachment should be serialized in base64 inside the doc as before, or do a proper attachment database, which will allow the users to sync any kind of binaries, even outside of the scope of the GDD text (a video file could be a GDD entry for example,,)

This however, brings the question if it is worth the effort, or the potential performance implications (using a db as a file repository ins not the best idea) and if it is, maybe it would make sense to migrate to a file based repository instead of the database approach…

With this idea, drafft could support any “file” and a simple file/folder hierarchy. Multi user sync would be done with third party apps like dropbox, git or similar… Integration with the game engine would be easier, even the game assets could be centralized and taken directly from the workspace…

Sorry for the brain dump!

As for reference, I have a version in dev which allow to reference any drafft object with a internal link (drafft://actor/actorname drafft://script/id_or_alias) etc, but I got a bit stuck with the previous topic that is related

Sorry for the inconvenience, and thanks for the tests!!! I will try to reproduce in a local environment and find a fix. It is definitely related to the electron build/packaging process and how it is retrieving the files.

Thanks

Hello! Not much really, just simple linear timelines/events/etc it is a really old feature but might be useful for mapping out a story. But honestly maybe the node tree editor is more versatile.

Thanks for the follow up! Hmmmm this is strange, are you using the portable windows version right? It seems that it is failing to get to the example jpg from the filesystem for a the new actor, for some reason, probably related to the Windows path filesystem and how it is resolved when packaged.

I have a theory, on what could be causing it, does it happen as well in the installer version?

Hello! Best I can offer right now is a link to the docs repo. You can download a zip and inspect the .md files. Not what you are asking, but better than nothing I suppose.

https://github.com/ajboni/drafft-docs

Hello Thanks for the feedback! Unfortunately I cannot reproduce #1 and #3, I’m in Linux. Are you in the latest version? If so, can you check if you get an error in the console when adding the actor and when auto-detecting? (ctrl + shift + I). I suspect is something related to the blob attachment.

About the export, I found a bug and fixed in 1.4.1, thanks! The quick export will start to working after an export has been made. (its the same command without the file picker)

Hello! Some updates about this feature, which is available in v1.4.0

It’s not exactly what we had in mind at first but might be helpful. The problem of running headless is that the local pouchdb is stored in the browser. Also electron requires a display to run headless so it a bit tricky. So for now, we have a REST API that runs when a project is loaded (if enabled in the options) that can get you a game export and a database dump.

Docs: https://drafft.aboni.dev/en/docs/documentation/api_docs.html

Other thoughts:

• I’m planning to make a little cli app does the fetching but any standard GET request method would work. This tool could probably have some mechanism to dump from a remote couchdb instance as well.