I’m revisiting this thread. Specifically, I’m intrigued by the possibility that Twine can be entered in ParserComp.
As reference, ScottKit works in this format: MATCH-COND-ACTION
MATCH is matching the commands given by the parser, such as OPEN DOOR . COND is checking the necessary condition that needs to be satisfied before action is taken, such as HERE DOOR .
ACTION is the code that needs to be executed in the game to reflect changes to the world model, such as SWAP DOOR OPENDOOR .
Now, I know Twine runs on HTML/JS, which presumably has Array and conditional output. So, I have this idea (taken from RPN calculator discussions, bonus for maximal score here @mla): what if we change the order around? What if we do: COND-MATCH+ACTION?
if (HERE DOOR)
LINK "OPEN DOOR" {
SWAP DOOR OPENDOOR
"You open the door."
}
The first thing that comes to mind is that “You can’t do that, yet.” is no longer possible, as is any invalid command. The fact that Command is only visible/clickable if the condition is satisfied, means that Authors no longer have to worry about silly, non-sense commands. That helps a lot in producing IF works quickly. (fast)
Another thing to consider is that VERBs should be limited, unless you fancy scrolling through hundreds of choices! This helps to streamline the story and focus on the puzzles. (easy)
Then there’s the matter of not duplicating commands, daemon, etc. Issues that are common to implementing Design to Platform.
But what do you get in return?
- Fast development time. ScottKit is fast and easy.
- Multimedia that is HTML+CSS+JS
- Portable Online and Offline publications
- Possibility of serial IF publications!
Bonus: Entry in ParserComp 2022!