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
I was testing hou+ using the standalone compiler, and noticed two errors were output while compiling &opening.txt.
voidOpeningLaunch(){if(GetGlobalFlag(GVideoOpening)>=3){PlayOriginMovie();}}voidOpeningStory(){if(GetGlobalFlag(GVideoOpening)>=2){SetGlobalFlag(GVideoOpening,3);PlayOriginMovie();}}voidPlayOriginMovie(){if(GetGlobalFlag(GArtStyle)==2){// Play OG video if using OG artstylePlayVideo("video/mv13-pc.mp4",1920,1080);}else{// Otherwise play console art stylePlayVideo("video/mv13-cs.mp4",1920,1080);}}
The error is that PlayOriginMovie(); should actually be CallSection("PlayOriginMovie");
I'm not sure if this works anyway, even without the CallSection, as the movie does seem to play.
But I was wondering how we've been running CI/building the scripts without noticing this error. I then checked where the error was raised:
It looks like the error is just printed out, but there is no signalling during compile that an error occurred, so the compiler thinks everything is OK.
Will need to check whether this was done deliberately (as the script seems to work anyway under this condition).
But personally, since this only happens if there is a genuine error, I would want to throw an exception and tell the developer to fix the script (since it should usually be an easy fix).
Also check if this applies to previous chapters (apply this fix to the mod branch)
The text was updated successfully, but these errors were encountered:
I was testing hou+ using the standalone compiler, and noticed two errors were output while compiling
&opening.txt
.The error is that
PlayOriginMovie();
should actually beCallSection("PlayOriginMovie");
I'm not sure if this works anyway, even without the CallSection, as the movie does seem to play.
But I was wondering how we've been running CI/building the scripts without noticing this error. I then checked where the error was raised:
It looks like the error is just printed out, but there is no signalling during compile that an error occurred, so the compiler thinks everything is OK.
Will need to check whether this was done deliberately (as the script seems to work anyway under this condition).
But personally, since this only happens if there is a genuine error, I would want to throw an exception and tell the developer to fix the script (since it should usually be an easy fix).
Also check if this applies to previous chapters (apply this fix to the
mod
branch)The text was updated successfully, but these errors were encountered: