SourcePawn highlighting and autocompletion for Visual Studio Code. Supports the SourceMod old and new syntax.
- Compile from VSCode with a simple button.
- Autocompletion.
- Go to definition.
- Symbol references.
- Symbol renaming.
- Function signature help.
- Call hierarchy
- Code outline.
- Upload to an FTP/SFTP server on successful compile.
- Automatically run
sm plugins refresh
on a successful upload. - Hover for details.
- Icons for
.smx
,.sp
and.inc
files - Automatically scan include files for natives, defines, methodmaps and more.
- Useful snippets.
- Detailed semantic highlighting for
.sp
,.inc
,.cfg
,.games.txt
and.phrases.txt
. - Parse sourcemod files from a custom location.
- Linter (error detection) for
.sp
and.cfg
files.
Details on how to use the extension available in the Wiki.
- Dreae's extension which is not supported anymore, and on which this extension is based on.
- Deathreus' extension which helped me to implement the linting feature.
- Everybody that has helped me improved the extension on the discord server.
- How can I donate ?
- How to install the beta build ?
- How to contribute ?
- How to run the extension from its source code ?
Thanks for considering this. But please remember that all of this wouldn't be possible without the Alliedmodders community. If you wish to make a donation for this community, you can make it here. If you prefer to make a donation to me for this project, you can buy me a coffee
- Open VSCode and go to the marketplace.
- In the search bar, type
SourcePawn
and select the extension. - Click on
Switch to Pre-Release
(see screenshot below).
This will install the latest development build of the extension.
Note that a new build might take a few minutes (up to 15) to propagate to the Marketplace after the commit has been pushed to the dev branch.
You can also install the latest pre-release by downloading the .vsix from the releases page and installing it manually.
Pull requests and suggestions are welcome.
- To make a suggestion or to report an issue, please create a new issue here.
- To make a contribution, fork the repository, make the desired changes, and open a pull request.
To run the extension from the source, do the following: