Cool concept. I see potential, but at this point, it feels just like an early alpha where the execution leaves a lot to be desired.
The UI is serviceable, but it has minor and major issues (use <<NoBr>>, I lost count of how many times the empty lines forced me to scroll down and down and down to find the "done/back" button, fix the debugging error handling that mostly ends with the text behind the button), the character info screen is bad (Too many things, poor organization)
Inventory management is awkward and incomplete (Why do I have 20 buttons to use a medi-kit when one suffices? Why can't I move just that item instead of moving them all? How can I carry 50 tons of junk?)
The navigation is rough (no map/mini-map, unclear instructions) Exploration needs to be interesting and worthwhile, right now finding something is an exercise of frustration and repetition.
There are quite a few breaking bugs (unfinished or buggy passages with no "back" button) plus lots of annoying bugs (mostly item-related or due to coding issues like missing closing tags)
The project needs major coding refactoring to make the project viable, otherwise, it will become a humongous pile of spaghetti where finding bugs or places to add/edit something will be increasingly difficult.
Moving the code to JS and accessing the code through macros IS the way to handle a large complex project that is more than picking paths, tracking a few variables, and scoring points.
Something like ("Phone Recipes" passage)
A lot clearer, and you can easily spot things like calling the same thing CookingMama and CookingOutbreak without the messy and error-prone code (and with a simple block of good old JS that saves the intended output to a string and "wikify" it)
The UI is serviceable, but it has minor and major issues (use <<NoBr>>, I lost count of how many times the empty lines forced me to scroll down and down and down to find the "done/back" button, fix the debugging error handling that mostly ends with the text behind the button), the character info screen is bad (Too many things, poor organization)
Inventory management is awkward and incomplete (Why do I have 20 buttons to use a medi-kit when one suffices? Why can't I move just that item instead of moving them all? How can I carry 50 tons of junk?)
The navigation is rough (no map/mini-map, unclear instructions) Exploration needs to be interesting and worthwhile, right now finding something is an exercise of frustration and repetition.
There are quite a few breaking bugs (unfinished or buggy passages with no "back" button) plus lots of annoying bugs (mostly item-related or due to coding issues like missing closing tags)
The project needs major coding refactoring to make the project viable, otherwise, it will become a humongous pile of spaghetti where finding bugs or places to add/edit something will be increasingly difficult.
Moving the code to JS and accessing the code through macros IS the way to handle a large complex project that is more than picking paths, tracking a few variables, and scoring points.
Something like ("Phone Recipes" passage)
Code:
<img src="images/Player/smartphone.jpg" width="512px" height="768px" />
You have the following recipes on your CookingMama app.
<<PrintInventory "RecipeBook">>
You can add the following recipes to the CookingOutbreak app.
<<MakeItemList "recipe">>