[CSIDE] The ChoiceScript IDE

Let’s start by trying to get you on the latest version – that’s the very first release of CSIDE which is now around 8 years old! No doubt the version of ChoiceScript included in it is very behind the one you’ve download from GitHub.

Can you check below the version that you’ve got an update channel selected? You may get the infamous “SSL” error message, which I can send you a workaround for (I’ll add you to a DM).


Yeah. CSIDE sometimes gets a bad rap for things not working quite right but 99% of the time it’s because people are using an old version of it and the “bug” is that the ChoiceScript version is massively out of date. Though I’ll hold my hands up there and say that’s often on me because of the update bug I can’t fix without a tech stack rewrite (lesson hard learned). A CSIDE “2.0” would be able to fix all of this and make it very clear that users need to keep updated.


If updating you doesn’t work, then I’ll ask you to share the files, but I’m optimistic that’ll be the difference.

2 Likes

Ah…thanks, @CJW. I last downloaded this CSIDE a year-ish ago when I got my new laptop. Right now I’m looking at the GitHub page that Google takes me to, and I see what look like two options: download a version called “v1.4.5_development” with a Pre-Release flair, or one that has a nice finished-looking English label of “ChoiceScript IDE - Public Release,” and a Latest flair, which in small print promises me the “Public release of CSIDE 1.0.1”.

I take it I should have picked option one, which would actually have got me the Latest Public Release… rather than just a Pre-Release in Development, which sounds like something that should only be used by your testers? :slight_smile:

I don’t use GitHub for basically anything else, so I’m not at all familiar with its conventions. But if 99% of your problems come from people still operating with CSIDE 1.0.1, my guess is that at least 80% of that problem could be solved by changing the GitHub presentation to encourage people to pick the actual latest version rather than the one currently marked Latest. :wink:

PS - and my Update Channel is Stable. I take it that should also be different? I’d thought that as long as I didn’t select None, I’d be getting the latest stable version, rather than e.g. the bleeding-edge one your testers were using.

1 Like

Actually, no. Option 2 is correct :sweat_smile:.
But the app should then prompt you to automatically update once installed and that’s where everything seems to fall apart as a lot of people see errors - or maybe in your case - no prompt at all to update?

I agree that publishing installers for later versions would help, but it’s significantly more effort (as I need to create those on each platform) than just shipping an update file from my MacBook that works for everything.

I’ve added you to the DM thread on how to update your current version - if the auto update isn’t triggering on stable.

Edit: to clarify, yes, stable should work just fine. If you change your channel (just reselect stable) it should either prompt you to update (great) or error (see the DM).

3 Likes

Thanks. :slight_smile: Yep, when I try clicking a different update channel, I get the error messages. Will take it to DM.

Edit: for the record, getting the latest CSIDE version solved the problem. Thanks again to CJW for all the help!

1 Like

I’m dealing with the same update issues

DM’d.

Coming from the support thread.

I updated (version 1.3.4) and ran another random test, but this time instead of crashing, it just froze a few seconds into the test. I don’t think it’s a hardware issue because while CSIDE is frozen, the other programs still work (and I also checked task manager to see if the RAM was overloaded but more than half was still available, same for the CPU).

Would you be happy to share your code with me via DM? Randomtest can be a bit of a beast and at the moment it runs on the same thread as CSIDE’s application code (quirk of JavaScript), so it can end up freezing the UI/causing the app to become unresponsive. You can also try a smaller number of iterations, which should help. I’m aware that performance of the tests isn’t the best in CSIDE and been thinking about ways to improve this moving forwards.

I usually run 100 iterations if running through CSIDE, for this very reason. If I want to run more iterations, I’ll use the HTML that’s bundled in the ChoiceScript ZIP file.

2 Likes

I was trying to get the average playthrough length so it isn’t a specific piece of code but the entire WIP (64k words without code).

Guess I will try that.

1 Like

Yep, that’s not a problem. If you’re happy to share, I’m happy to debug. But it probably is just the aforementioned performance issue.

1 Like

I thought I knew where to begin, but now I’m not so sure! Could someone share a link to find the most recent version of Choicescript IDE? I thought I had found it but it was version 1.0.0 and now I’ve seen comments saying the most recent one is 1.2.1.
Every time I load up CSIDE I get an error message that says ‘Failed to obtain update data from server’ and I wonder if it’s because I’m using an out-of-date verson.

Hi Sue, 1.3.4 is the latest public version.
I’ve sent you a DM to help you obtain it.

Could you send me as well, I’m having the same issue.