instead of written different setups for every voc, we could edit a .json file and import it on user options
it will be easier to edit :D
Printable View
instead of written different setups for every voc, we could edit a .json file and import it on user options
it will be easier to edit :D
Not quite sure I understand what you're trying to describe? You want to distribute multiple json files to end-users along side scripts?
Save 4 default json files. When you create a script edit with notepad++ and gg.
lets say you have a config in json for the user edit options, per vocation well if you include this files to your library you could update the correct json
if voc = sorc then load(sorc.json) end
So you want something like this?
Remember you can also load files from the WindBot folder, that might make things even easier, although distribution could be a pain... Maybe distribute a setup script which creates the json files, then load them dynamically as you'd like... IDK, anyway, this feature already exists so I'm gonna mark it as such.
When I read this post I got another idea not like what post saying but something like Toolbox for JSON. it will be grateful
@hyderascripts
I think you like notepadd++ too much :D :D ;D