Pawn Forge

Pawn development tools for VS Code and Zed, built for the open.mp / SA-MP Pawn ecosystem.

What is implemented

• .pwn, .inc, .pawn, and .p language detection.
• Tree-sitter-backed parsing using the stable tree-sitter-c grammar as the first parser layer.
• Pawn-specific highlighting queries using standard Zed captures such as @keyword, @function, @type, @string, @number, @comment, @variable, @operator, and @punctuation.
• Language-provided tasks for pawncc and sampctl.
• A bundled Node-based Pawn language server derived from openmultiplayer/vscode-pawn.
• Completion, hover, signature help, and go-to-definition from the existing Pawn parser.

Why the C grammar

This is deliberate for the first milestone. Zed themes already have strong C-family styling, and the Pawn syntax is close enough to C that it gives us a useful, fast parser while we build a Pawn-specific grammar.

The highlight queries do not define colors. They use Zed's normal capture names so the active theme decides the palette.

Build tasks

The extension contributes these tasks:

• Pawn: Build current file using pawncc from PATH.
• Pawn: Build with sampctl.
• Pawn: Build sampctl profile dev.
• Pawn: Build sampctl profile release.

For a custom compiler path or custom arguments, copy the task into the project's .zed/tasks.json and change command and args. Zed also supports ZED_FILE, ZED_WORKTREE_ROOT, and related task variables.

Source reference

The language-server implementation is based on openmultiplayer/vscode-pawn in vscode-pawn-master supplied for this project. The original project provides the Pawn syntax definition and the parser used for completion, hover, signatures, and definitions.

Next milestone

Replace the C parser layer with a real tree-sitter-pawn grammar while keeping the same Zed capture vocabulary. Then add compiler-aware diagnostics and explicit Pawn build/compile configuration so pawncc and sampctl can be selected independently.

pawn-development

VS-Code extension for Pawn language Originally created by Indian Ocean Roleplayเน‚ย„เธ‚ (samarmeena)

Features

• Go To Definition
• Hover Definition
• Parameter Helper
• Syntax Highlighting
• Auto Code Completion
• Custom Inline Snippets
• Format Document
• Format Selection
• VSCode Regions
• Generate Numbers

Define Custom Snippet Anywhere

You can define two types of snippet *Note: second type support autocompletion of parameters.

//#snippet new_cmd CMD:cmd_name(playerid, const params[]) {\n\treturn 1;\n}

//#function CreateCar(vehicleid, Float:posX, Float:posY, Float:posZ);

Usage of .pawnignore

Right click on on your files to add to .pawnignore, this way you'll tell extension not to parse these files for auto-complete and intellisense. *Note: syntax works exactly like .gitignore.

Installation

Search for "Pawn Forge" in the VS Code Extensions section and install it. Alternatively, you can check out the source code or view the marketplace page:

• GitHub Page
• Marketplace Page

Creating tasks.json

Press Ctrl + Shift + P or F1 and then type >Initialize Pawn Build Task

Explanation

• "command": "${workspaceRoot}/pawno/pawncc.exe", is the important part here, this is the path to your Pawn compiler and I've assumed most of you have a left-over pawno folder from that long dead text editor! This folder not only contains Pawno but also the Pawn code compiler (pawncc.exe). You can safely delete pawno.exe forever.

• "args": [...], is also important, this is where you define the arguments passed to the compiler. Pawno also did this but you might not have known. The defaults have always been -;+ to force semicolon usage and -(+ to force brackets in statements. If you store your Pawn compiler elsewhere, just replace the entire command setting with the full path to your compiler. Also, if you want to disable debug symbols (you won't be able to use crashdetect) just remove -d3 from "args".

• problemMatcher is the part that allows recognising the Pawn compiler output and presenting it in the problems panel of the editor. This doesn't work well with external includes because the paths change from relative to absolute.

Define single gamemode file that always compile on build task

1. goto .vscode/tasks.json
2. replace ${relativeFile} with ${workspaceRoot}\\gamemodes\\mygamemode.pwn
3. all done

Compiling Pawn Code

To actually compile after you've set up the tasks.json below, press CTRL + Shift + B (Windows) or CMD + Shift + B (Mac), or alternatively open up the command palette with CTRL + Shift + P (Windows) or CMD + Shift + P (Mac) and type Run Task, hit enter and select build-normal.