Post by Nano Game Lab in Drafft v2: Development, Wishlist & Feedback

Viewing post in Drafft v2: Development, Wishlist & Feedback

Heres an idea for drafft 2

in the document editor having the language support variables so when it is viewed as a document the variables are displayed instead.

For example in a gdd or story concept:

var gamename = STEAK

here is my story about $gamename ! $gamename is a story about cows.

this would then read as here is a story about STEAK! STEAK is a story about cows!

just to simplify the changing of text objects in the text with out having to do it manually. What would be even better is to be able to have the variables stored in a different text file (like C++ header files). that way we could keep as many as we wanted but keep the documents clean. Use a maybe a #include gamenames.txt, it searches for anything in the same folder, if you want to search for any other file maybe use ## instead of #.

just a thought. could be useful.

baj2 days ago

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!

Nano Game Lab1 day ago

I think it has a lot of potential, im currently editing all 18 documents to replace names and some objects ive written about, so having it is definitely a real world issue solver lmao, instead i could just go to a variable table / header file (what ever you want to call it or refer to as) and change the variables once for all files that are reading from that table/file/data would be really useful. i think the simpler the better, as would be needed by non programmers and they may not have a good understanding of code, so making it simple syntax would be the best thing, id hide any data that appears complex unless directly “shown” by users (like my self) so it is not in non technical users face confusing them. making your software usable across the board. i think complex use cases need these sort of tools. but in a lot of indie cases, it could be hidden or behind an option.

maybe you could have a predefined document type that has everything already set, have an option for pointing docs to that header file (if not done with syntax) and have a table / list a non technical user can add or subtract from to add their variables. then those variables can be accessed from a modifier like “/” or “!”

and for complex users make it more code like where they can create any document type and just add what they want via #includes ##includes and variables with syntax for those that may need more flexible and more involved capabilities.

it could be in many different formats but i think that it could be massively valuable. especially if you can reference this from things like script dialog editor and quests etc.

itch.io

Viewing post in Drafft v2: Development, Wishlist & Feedback