Visual Studio Code: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (→‎See also: Unicodifying, replaced: See Also → See also)
mNo edit summary
Line 1: Line 1:
{{WIP|[[User:Equalizer5118|Equalizer5118, an idiot who cant spel]] ([[User talk:Equalizer5118|talk]]) 12:30, 25 January 2024 (PST)|note=Currently rewriting the page to actually pertain to VSCode, and not a tutorial about VScript.}}
{{for|Setting up VSCode for Vscript|[[Visual Studio Code/Setting up Visual Studio for Vscript|Setting up Visual Studio for Vscript]]}}
This page describes how to set-up Visual Studio Code (VSCode) for [[VScript]] purposes.
This page describes how to set-up Visual Studio Code (VSCode) for [[VScript]] purposes.



Revision as of 13:30, 25 January 2024

Template:WIP

For Setting up VSCode for Vscript, see Setting up Visual Studio for Vscript.

This page describes how to set-up Visual Studio Code (VSCode) for VScript purposes.

Usage

Squirrel Squirrel

Click on the Extensions button in VSCode. This is represented as a icon of building blocks, usually on the left side of the window.

Search for "Squirrel" in the search bar. Install the following extensions:

  • Squirrel Language Supports (by marcinbar)
  • Squirrel Language Linter (by marcinbar)

Restart VSCode. Now the language is ready for use in the editor!

Autocomplete

For Team Fortress 2 Team Fortress 2, auto-completion of the game's built-in script functions and constants is also available.

Click on the Extensions button in VSCode. This is represented as a icon of building blocks, usually on the left side of the window.

Search for "VScript" in the search bar. Install the following extension:

  • TF2 VScript Snippets (by Sour Dani)

Restart VSCode. Functions and constants should now autocomplete!

Debugger

Demonstration of the debugger

This allows you to create breakpoints, step line by line, and view the state of all variables during each step. Download the extension from here.

See also

External links