New Choicescript extension for VS Code (2.0 now runs games!)

Hey this is super useful! Just tried it out and I think it is what I have been looking for. Like the others above, I also experienced an issue with the *image command, but I just commented it out when testing.

Thanks for giving me the push to update the extension! Version 3.0 is out now, and should automatically update in your version of VS Code. This has a lot of under-the-hood infrastructure changes thanks to @CJW. With luck it’ll work fine, but if you run into problems, or if my fixes for the *image command don’t work, please give me a shout.

9 Likes

Version 3.0 loaded like clockwork.

Thank you for your contributions towards the community @Sargent!

. :revolving_hearts:

1 Like

Amazing, thanks so much!

1 Like

Thanks so much! I dont suppose *temp_array and *create_array were added to the commands this update? Not sure if its my computer but VSCode always told me those commands didnt exist

Not yet, sorry.

1 Like

Version 3.1.0 has another big improvement thanks to @CJW: your games will now open in a separate tab in VS Code. It should be out to y’all shortly.

9 Likes

When you run a line like this: $${money_var} - so you want to see the dollar sign before the var displays, vscode doesn’t display the dollar sign. But if you run it on CSIDE or on cogdemos, it does. But I love this extension thank you!

Oh, huh! I see what you mean. Let me take a look at it.

2 Likes

@Sargent, you did amazing work! Thank you very much! I am using and loving it! :love_letter:

1 Like

@Sargent, I wanted to confirm if/when the plugin would properly support the checkpoint system implemented a few months back?

Thanks so much for everything you do!

2 Likes

Thank you for the reminder! I’ll add that to my to-do list for the coming weeks. If you don’t hear from me by mid-month, please feel free to remind me.

2 Likes

I’ve got an update for the plugin that should support checkpointing properly. I’d love for folks to test it before I push it to the VS Code Extension Marketplace. You’ll need to:

  • Download the vsix file
  • Inside VS Code, press Ctrl+Shift+P to bring up the command palette.
  • In that palette, start typing “vsix”. The command “Extensions: Install from VSIX” should appear. Select it.
  • In the file chooser window that appears, select the choicescript-vscode-3.1.1.vsix file that you downloaded.

Once it’s installed, give it a whirl and let me know what issues you find.

3 Likes

From a quick look, it seems to be running fine when playing the game in VS Code. Thanks so much for doing this!

The choice_saved_checkpoint_checkpointname variables do show as an error - I think because the variable doesn’t get created in startup the way normal ones do. If it would be possible to exclude variables with the choice_ prefix that would be a cool quality of life nice-to-have, as it means it’d be easier to find the real errors in the list.

Aha, good catch! I’ve not been doing a blanket exclusion of choice_ variables, since I want to be able to warn people about typos in those variables. However, this gave me the push to re-work that part so it handles built-in variables w/different names properly. As a bonus, if you try to *create or *temp a choice_ variable, that now gets flagged.

The fix is now available from the same place as before prior to me pushing it live.

1 Like

Is there anyway to get Grammarly to work with this?

As far as I know, Grammarly removed some API things and it stopped working in several places. The last day it worked for me was a week or a couple of weeks ago.

https://www.reddit.com/r/vscode/comments/1crtdg8/grammarly_extension_removed/?sort=new

If there is another way of making it work I would like to know cause it was super useful. Or even if it can be run locally, I don’t know. Specially in VSCode.

That works great!

1 Like

I’ll be testing soon! Picked a bad time to come down with COVID :joy:

Thank you again!

1 Like

Grammarly only runs in the cloud, and they shut down their API at the start of this year, so there’s no way to use or integrate it with VS Code.

It wouldn’t have the full capabilities of Grammarly, but you could get spellchecking by extending one of the existing VS Code spell check extensions to know about Choicescript. That’s doable, but not by me, I’m afraid.

3 Likes