- Aug 5, 2019
- 164
- 148
I got the same Javascript error as noted here.Feebs, a very minor issue:
You don't have permission to view the spoiler content. Log in or register now.
I got the same Javascript error as noted here.Feebs, a very minor issue:
You don't have permission to view the spoiler content. Log in or register now.
Yes, please. Though ideally not spamming this thread. There's a channel on Discord for it, or maybe send via a notepad/DM if you'd prefer to avoid Discord. Druid64 has found a lot for us recently, and those'll be included in 0.2.5.At at least 2 points while Zoe is undercover as Sharon, people refer to her as Zoe. Since Feebs seems to read the thread often, figured I'd post it here in case no one else has.
If you see this Feebs, want me to point out other writing mistakes and/or spelling errors if/when I find them?
This will be part of the 0.3.X dev cycle and probably a few months away.Is there a sense of when you'll be able to revisit the New Eden mission to get all the scenes you missed? I'm hesitant to keep playing the new content if it turns out that I missed some important characters there. Also, is there any sort of guide for that whole quest? I fell like I missed a ton of stuff. (I know it's not all available in one play through)
Once the spa is built, you should be able to go inside it and click her portrait when she's not otherwise engaged.Hey guys! Not sure how to progress with Ruby (Aubree). I got her taboo path, but can't trigger spa and the next scene. Any advice?
Yup, built the spa. Got a scene with Vanna, but when clicking on Aubree she just restores fatigue.Once the spa is built, you should be able to go inside it and click her portrait when she's not otherwise engaged.
v0.2.5 now live. Changelog in the OP.
It's mostly bugfixes, but does move Megan forward a little.
Outside of any critical bugfixes, this will be the last update in this substory cycle, and I'll now be focusing on main story content for 0.3.0. The next release is therefore likely to be a couple of months away.
0.3.0 will focus on the council and reveal more of the ongoing world story and hint further towards how you came to be embroiled in it. Though I'm sure many have worked that out for themselves already!
The error doesn't appear to reoccur on loading the save.<<script>> setup.scriptpromise.then(function () { getTooltips(); if (settings.volume != undefined) $("video").prop("volume", settings.volume); if (settings. NumberedOptions == true) { $('#passages .choices').ready(function() { let i = 1; $('#passages .choices .link-internal:visible').each(function() { let txt = $(this).html(); if (i == 10) i = 0; $(this).html(txt + " <span class='i'>"+i+"</span>") ; if (i == 0) вернуть false; i++; }) }) } }) <</script>>
View attachment 3442290
That's funny. The code copied by tepkom seems to come from the passage "PassageFooter", which contains:The error doesn't appear to reoccur on loading the save.
But, I note the script you've quoted has some Cyrillic script in it... but my code has none natively.
Everything about the code and other elements of the engine should not have Russian, he stupidly does not see it. I myself faced such a problem when I was making a game in Russian.That's funny. The code copied by tepkom seems to come from the passage "PassageFooter", which contains:
if (i == 0) return false;
But in the copied message, this has been partially translated from English to Russian:
if (i == 0) вернуть false;
This explains the error appearing in red in the screenshot: "Unexpected token: 'false'" because the parser sees 'вернуть' and interprets it as an identifier instead of a reserved word like 'return'. In that position, an identifier can be followed by some parenthesis if it is a function call, or by an assignment operator if it is a variable assignment, or by an array index or other types of symbols, but not by another identifier such as 'false'. Hence the "Bad evaluation" error.
Of course the root cause of the problem is this strange partial translation to Russian...
Aye, it's certainly not something added at my end.That's funny. The code copied by tepkom seems to come from the passage "PassageFooter", which contains:
if (i == 0) return false;
But in the copied message, this has been partially translated from English to Russian:
if (i == 0) вернуть false;
This explains the error appearing in red in the screenshot: "Unexpected token: 'false'" because the parser sees 'вернуть' and interprets it as an identifier instead of a reserved word like 'return'. In that position, an identifier can be followed by some parenthesis if it is a function call, or by an assignment operator if it is a variable assignment, or by an array index or other types of symbols, but not by another identifier such as 'false'. Hence the "Bad evaluation" error.
Of course the root cause of the problem is this strange partial translation to Russian...
That's a concern, it'll be false positive. I had a similar issue with 0.1.0 but once Defender had 'seen' it enough it seemed to be okay with it. I'm not really sure what's caused it tbh. Right at the start I was quite frantic looking for it, but then it suddenly seemed okay, so I thought it had sorted itself out.If I try to download the 0.2.5 update, Windows Defender flags it before it can even go in my downloads folder. I've tried from multiple sites and in different browsers.
It's actually very simple, I use chrome's built-in rus-eng translator. There was no such error in the previous version. That's why I wrote.That's funny. The code copied by tepkom seems to come from the passage "PassageFooter", which contains:
if (i == 0) return false;
But in the copied message, this has been partially translated from English to Russian:
if (i == 0) вернуть false;
This explains the error appearing in red in the screenshot: "Unexpected token: 'false'" because the parser sees 'вернуть' and interprets it as an identifier instead of a reserved word like 'return'. In that position, an identifier can be followed by some parenthesis if it is a function call, or by an assignment operator if it is a variable assignment, or by an array index or other types of symbols, but not by another identifier such as 'false'. Hence the "Bad evaluation" error.
Of course the root cause of the problem is this strange partial translation to Russian...
The translator itself does not break the code in the engine. You probably sent an error which translator translated when the error window appeared. It is better to restart the page and send the original error text without a text translator.It's actually very simple, I use chrome's built-in rus-eng translator. There was no such error in the previous version. That's why I wrote.
I don't really understand the reasoning behind it. This error is not present in version 2.4. Now I compared the code between the versions. Everything seems to be similar, but the error is present only in version 2.5. Without translation the error disappears.The translator itself does not break the code in the engine. You probably sent an error which translator translated when the error window appeared. It is better to restart the page and send the original error text without a text translator.