Currently, adjective, value, and other cascading logic arrays are stored in tales.js. Ideally, these could be stored in a separate document that would be editable without affecting the code itself.
Possible Solution
Consider creating a config file to store and manage this semantic data. tales.js could then call this externally stored data when necessary.
This can be done either by inserting a document into the HTML file before the tales.js file that the tales.js file then calls (example: adj.js on line x and tales.js on line x + 1. Alternatively, you could treat the config file as an API against which the data in question can be fetched.
Description
Currently, adjective, value, and other cascading logic arrays are stored in tales.js. Ideally, these could be stored in a separate document that would be editable without affecting the code itself.
Possible Solution
Consider creating a config file to store and manage this semantic data.
tales.jscould then call this externally stored data when necessary.adj.json linexandtales.json linex + 1. Alternatively, you could treat the config file as an API against which the data in question can be fetched.