vScript IDE is a code editor for writing Lambda point_script JavaScript files, the scripts that run in maps and custom games. It gives you a full editor with type checking against the lambda_script/point_script API, a local workspace with folders and tabs, and one-click export of your scripts into a map's BSP.

If you are new to map scripting, start with the Intro to Lambda vScript documentation.

The Workspace

Your workspace is a set of .js files stored locally in the app. It is saved automatically and will still be there next time you open the IDE; nothing is uploaded anywhere.

• Files and folders: Create, rename and delete script files, and organise them into folders (paths use /, e.g. zoo/mdlchange.js). File and folder names may use letters, digits, dots, dashes and underscores.
• Tabs: Open several scripts at once; open tabs and the active file are remembered between sessions.
• New scripts start from a template that imports Instance from lambda_script/point_script and logs a message, so they are valid point scripts from the first line.
• Theme: Switch between light and dark; your choice is remembered.

The Editor

The editor is Monaco (the VS Code editor) configured for point scripts:

• Type checking and IntelliSense are driven by the bundled point_script.d.ts declarations and tsconfig.json, so you get completion and error squiggles for the point_script API. These two reference files are read-only parts of the workspace and are never exported into maps.
• Scripts are plain JavaScript with // @ts-check enabled by the template.

Exporting your Scripts

Export as ZIP

Export ZIP downloads your whole workspace as vscripts.zip. The zip also includes point_script.d.ts and tsconfig.json, so it unpacks as a drop-in scripts/vscripts/ folder that also works with desktop editors like VS Code.

Export to BSP

Export to BSP embeds your scripts directly into a compiled map:

1. Click Export to BSP. A dialog lists every map found in your Garry's Mod garrysmod/maps folder; use the search box to filter, then select a map.
2. Click Export. Your scripts are written into the map's pakfile under scripts/vscripts/, replacing any files with the same names, and the .bsp is updated in place.

Exiting

Use the exit action to return to the dashboard. Your scripts are saved in your local workspace and will be there when you return; exiting does not lose work.