When splitting choice from story, it assumes three options will be pulled from the text. If ChatGPT's response omits the correct number of "!!"s the entire thing could crash due to an indexing error. I added in a fail safe that defaults the options to nothing if this problem were to occur to avoid a crash.
Additionally, I replaced "tags.json" with a variable and defined it at the top of the page. I don't want to hardcode a file name in the middle of function and this makes it easier to change in the future.
Only four TODOs remain in the code.
Changing climax to an int instead of bool (optional)
Changing climax description to account for this change
Fixing the routes to avoid redundancy in main
Updating tag weights
None of these should have any impact on how things function and can be safely ignored unless we decide to fine tune stories.
When splitting choice from story, it assumes three options will be pulled from the text. If ChatGPT's response omits the correct number of "!!"s the entire thing could crash due to an indexing error. I added in a fail safe that defaults the options to nothing if this problem were to occur to avoid a crash.
Additionally, I replaced "tags.json" with a variable and defined it at the top of the page. I don't want to hardcode a file name in the middle of function and this makes it easier to change in the future.
Only four TODOs remain in the code.
None of these should have any impact on how things function and can be safely ignored unless we decide to fine tune stories.