[CSIDE] The ChoiceScript IDE

When I do so, the scenes load and I can edit them.

Alas, when I try to run the game, it says failed to fetch. :confused: and it does not run.

Hello again, I finally had a moment to check on this today and can confirm I’m seeing the same issue. It looks like something has changed on Dropbox’s side. Unfortunately I’m not seeing an immediate/easy fix (I’ll look into but I can’t give a timeline at this stage).

2 Likes

I’ve had a chance to look into this today. Unfortunately it looks like Dropbox have implemented rate-limiting on their API. Annoyingly, their SDK doesn’t seem very good at reporting back in this instance, so I can’t react to it. Best fix I can think to do in the interim is to artificially slow everything down - this seems to work, but it’s a rather disappointing outcome.

I’ll see if I can get this ā€œfixā€ implemented over the weekend.

2 Likes

Thank you, @CJW . You are number one indeed

1 Like

I’ve just pushed a fix for this. As mentioned above, you will unfortunately see a degradation in speed, but the app should be functional again. I can’t promise I’ve caught every case, so please let me know what action you were performing should you see any further issues.

2 Likes

Thank you very much for your efforts @CJW . I really appreciate them.

Hi there! Things seem to work fine. The only ā€œcuriousā€ thing I noticed is that the title ā€œMy First ChoiceScript Gameā€ remains there, even if I entered a different title for my game.

1 Like

Hmm, I don’t think that would be related to the changes I made. Was it working before?

1 Like

I was just playing around with things and noticed that as well!

1 Like

I am sure that now it shows this glitch. I’m sorry, but I don’t know how long before this happened.

Another thing I just noticed is that when an error occurs, CSIDE online now behaves differently than before.

Before now, every error was reported in a ā€œredā€ window that disappeared shortly but remained in a LOG that I could read by accessing the ā€˜!’ triangular button.

When an error occurs now, a WHITE window describes it. I must remember and jot down what it says because when the white window goes away, there is no trace of that error in the LOG anymore.

Thank you again for all the hard work, @CJW :heart:

Some screenshots of this would be helpful :pray:

Here they are.


Here’s how an error shows up now. When you click ā€œok,ā€ the error does not remain in the LOG.

This is the EMPTY log. Usually, I would find the same error here until I decide that the error is ā€œsolved.ā€

I hope this helps. Alas, I cannot provide screenshots of the situation BEFORE this. :disappointed:

1 Like

Hi, is there plan to add more functionality ?

Did you have something specific in mind? I can’t say I’m actively working on anything new at this moment in time.

The tile visual like in " Chronicler ", to see were the story one and were are the possible error and miss in our writing.

Is it possible to use quicktest/randomtest inside the IDE while using implicit_control_flow? Right now I get this error:

RANDOMTEST FAILED: Error: chapter1 line 154: It is illegal to fall in to an *else statement; you must *goto or *finish before the end of the indented block.

However, when I test my files myself using the index.html file it works perfectly fine. AFAIK this error is solved by adding *create implicit_control_flow true to the startup file, which I did. I’m guessing this has some basic solution but I didn’t find it in the forum.

Thanks for any help! Sorry for the noob-ish question!

edit: here’s the line just in case:

You'd met Sen too. There'd been an awkward interaction,
*if (sen_gender = "man")
  after which he'd grunted a syllable at you before leaving.
*else
  after which she'd mumbled something and left.
You'd figured out it was ${s_hisher} name,

The tests in CSIDE shouldn’t work any differently to tests outside of CSIDE. If you can confirm running randomtest.js outside of CSIDE passes, I’ll consider it a bug and take a look.

Otherwise I’m not sure why you’d be seeing this behaviour.

1 Like

Just wanted to thank you for putting so much work into this tool. I’ve been having some problems with my beloved laptop, which is sad, and has stalled my progress a bit, but being able to use the web version again will help me immensely. Appreciate it.

3 Likes

Newly contracted Choice of Games writer here, deeply grateful that this tool exists! Thank you for all the hard work that went into it.

I’m having what’s almost certainly a total noob issue, but one I know I’m not alone in. For things to preview with the correct spacing in CSIDE, I’ve had to put two *line_breaks to get typical blank-line-between-paragraphs spacing. When I got feedback from my editor on my first chapter, she asked me not to do that, to just insert a blank line and it should space correctly. But… it doesn’t. She said they’ve ā€œbeen seeing an increase in the double *line_break construction recentlyā€ and asked if it was a CSIDE thing, so I’m sure others are having this issue too. Am I doing something wrong? Is there a setting I missed?

Thanks, all!

3 Likes

Welcome MK! Can you post a sample of the code that’s not showing proper spacing? If you select it and click the ā€œpreformatted textā€ button above (</>) it should keep the spacing rather than being reformatted as a forum post by Discourse…

Edit: when you really need to force a paragraph break, there’s an alternative using *comment that I describe here. But it would be good to see what’s causing the issue with a regular double enter.

2 Likes