Post by MegaMasterX in Drafft v2: Development, Wishlist & Feedback

Viewing post in Drafft v2: Development, Wishlist & Feedback

Been noodling on this for a bit.

I don't think AI is necessary for Drafft, AI is already diminishing enough as it is and feels like it'd unnecessarily bloat the tool. I've floated the idea of templates for many parts of Drafft, and still think that'd be awesome to have and save a bunch of time.

I'd love to see the API expanded a bit more.

My wishlist would be:

- Endpoints that can be called that force Drafft to navigate to a specific category or even a specific element or document within that category. (Use case would be a game editor tool that can call to Drafft which then opens up a specific dialogue, as an example.)

- Endpoints that can create a new entry and prepopulate it or write into sections like grids or scripts.

Looking forward to v2!

Nano Game Lab36 days ago (2 edits) (+1)

I have to agree, ai is apart of everything and giving it access to NDA covered information might be bad, Not just that ai is generally terrible at producing quality. It can do quantity very well. But I find when ever I use anything with ai it just causes more work and more issues for me later on. Being creative needs less hand holding and more encouragement. that said, it is a popular selling point for many available software choices. from an artists and business end point customer side, i see it as a risk of leaking and data scrape where any ai is considered. but as a business ownder i can see why Ai is attractive to put in to a product. its a double edge thing and could be beneficial or detrimental.

Not to mention its heavy for local machines and a risk if done with remote servers.

The api, I agree could definitely do with some update to the docs.

Main thing i wish for is git and optional use of server. if i could use this software with git, id be over the moon.

baj14 days ago

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.

baj14 days ago

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.

itch.io

Viewing post in Drafft v2: Development, Wishlist & Feedback