You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A particular Yarn file causes a compilation error.
Error on line 6 at position 10:
no viable alternative at input '<<set $s1.'
<<set $s1.pirateRespect to 0>>
..........^
The node in question looks like this:
title: S1
tags:
colorID: 0
position: 337,-9941
---
**<<set $s1_pirateRespect to 0>>**
<<set $s1_firstMate to "Kazuma">>
{$firstMate} takes the spyglass from his eye.
<<if Rapp()>>
Rapp: Check it out.<p> Looks like we found something.
<<else>>
Guido: Care to take a peek?
<<endif>>
{$firstMate} offers it to you.
...
The variable $s1_pirateRespect was changed from $s1.pirateRespect back when updating to YarnSpinner 1.0. So it appears to be... an old version of the file?
Reimporting triggers the following build errors, top to bottom:
Looks like the issue isn't actually in the node S1 in your file. In isolation, it compiles fine.
When I attempted to compile the full Yarn file you linked, I saw an exception when parsing the command <<p>> on line 386. (The same command also appears on line 1368.)
The issue is that commands that are a single character long (<<p>>) cause a crash in the compiler. As a workaround until a fix is shipped, replace the single-character command with something else (e.g. <pp>).
Technical details of the error!
It appears that <<p>> is being lexed as a COMMAND_START '<<', followed by a COMMAND_TEXT_END 'p>>'. This is incorrect behaviour from the lexer, because COMMAND_TEXT_END should only ever be >>.
It appears that the more directive in line 380 of YarnSpinnerLexer.g4 is causing the entire string p>> to be incorrectly matched against the token COMMAND_TEXT_END, when it should have been matched as a COMMAND_TEXT followed by a COMMAND_TEXT_END.
A particular Yarn file causes a compilation error.
The node in question looks like this:
Full Yarn file here.
The variable
$s1_pirateRespect
was changed from$s1.pirateRespect
back when updating to YarnSpinner 1.0. So it appears to be... an old version of the file?Reimporting triggers the following build errors, top to bottom:
The error is resolved if approximately the first 34 nodes in the Yarn file are deleted.
Build warnings for all other Yarn files are accurate.
The text was updated successfully, but these errors were encountered: