alforno

According to the docs (https://yarnspinner.dev/docs/writing/controlling/#options): > Options are usually at the end of the node, but they don’t have to be. For example, the options in the example above could...

My fork now has the runner handling options correctly. The problem was that options within a conditional (of the same nest level of a node) were being yielded instead of...

I've submitted PR #69 that resolves this issue.

It's the lexer and I've run into the same issue while implementing inline expressions. I'm working on a solution. As of today, the code is in lexer.js ``` const spaceMatch...

I've create a kludgey workaround that is now in my fork. https://github.com/alforno/bondage.js/commit/eeddb49def38d16f8bb0c54ad21e0b5c684784d9

I see the same issue trying to call a command as shown here in the documentation (https://yarnspinner.dev/docs/unity/working-with-commands/). It doesn't do anything but yield a CommandResult. runner.js line 137 yields a...

After looking at this closer, the parser and lexer would also have to be modified, because currently they only seem to be able to parse functions with arguments within a...

The source of the problem resides in the parser\node.js file ``` ArithmeticExpressionDivideNode: class { constructor(expression1, expression2) { this.type = 'ArithmeticExpressionDivideNode'; this.expression1 = expression1; this.expression2 = expression2; } }, ``` The...

That is called an inline expression. I'm working on implementing this in my fork. The lexer is having a hard time with the end brace token when testing with '{$test}'....

> I would very much welcome a PR that adds this feature :) even the basic ability to display the player name would be amazing. I am currently working on...