Pawn tooling, in one place

Build and maintain Pawn projects without guesswork.

Start with a practical guide, or search the standards and generated references used by PawnKit tools.

Guides

About this site

PawnKit is maintained by people building tools for the Pawn, open.mp, and SA-MP communities in their spare time. This site puts the shared guides and reference material in one p...

CI and editors

Use the same checks locally and in CI. This keeps editor feedback from drifting away from pull-request results.

Choose a PawnKit product

Most Pawn developers need the editor extension, the pawn command, or both. The smaller tools are included behind those two entry points.

Compatibility report

The August 4 signed set passed the PawnKit workflow on Linux, Windows, and macOS. It is the current set used by PawnKit Actions and editor tooling.

Getting started

PawnKit tools work with existing Pawn projects. You do not need to move files or adopt every tool at once.

Migrate an existing project

Commit or stash current changes before running a migration. pawnmigrate checks the working tree, but a clean commit is the easiest rollback.

PawnKit SDK

The PawnKit SDK is a set of Go modules for building Pawn tools. Pick the module that owns the data you need instead of rebuilding that layer in your project.

Run a packaged server

pawnserver installs versioned open.mp and SA-MP server bundles. A bundle records its binaries, checksums, entry points, configuration, and persistent paths.

Support

Check the maturity, tested platforms, and known limits for each repository.

View repository support

Reference

Browse RFCs, schemas, release sets, API data, and lint rules from their owning repositories.