What Is the Extensible C++ API in open.mp?

Updated

The Extensible C++ API in open.mp gives you access to every server feature that is available in pawn, plus the wider universe of C++ libraries and frameworks. It is the right choice if you already write C++ or need functionality that pawn cannot easily provide, and you obtain it through the SDK repository on GitHub. If you only script gameplay logic in pawn, you do not need this API at all.

What the C++ API actually gives you

open.mp is a multiplayer mod for Grand Theft Auto: San Andreas that is fully backwards compatible with San Andreas Multiplayer. Its scripting system sticks with pawn, but the server itself is fully open source and exposes an extensible C++ API alongside it.

The key point is parity plus reach:

  • Full feature access — you can reach all the server features that are available in pawn.
  • Beyond pawn — you can also use the universe of C++ libraries and frameworks, which pawn does not offer.
  • Open contribution path — once you have mastered the API, you can help improve the server through the open contribution process on GitHub.

So the API is not a replacement for pawn scripting. It is a second, lower-level way to work with the same server.

When to use it instead of pawn

Situation Better fit
Writing gamemode or filterscript logic pawn
Reusing an existing AMX script pawn (loads out of the box)
Needing C++ libraries or frameworks Extensible C++ API
Extending or improving the server itself Extensible C++ API

If your goal is to run or adapt existing SA:MP scripts, pawn is the practical route — an old AMX can be loaded on the open.mp server straight out of the box and played on the SA:MP client. The C++ API becomes relevant when your requirements go past what pawn exposes.

How to get started

  1. Go to the SDK repository on GitHub (linked from the open.mp site as the SDK repository).
  2. Review the API surface there to confirm it covers the server features you need.
  3. Build against it using your existing C++ toolchain and libraries.
  4. Once working, consider contributing improvements back through the open contribution process.

The expected result is a component that has the same access to server features as a pawn script, with C++ tooling and libraries available on top.

Common sticking points

  • Assuming it replaces pawn. It does not. The scripting system remains pawn, with a new compiler engineered to make code more robust and more functions to manipulate the server and client.
  • Skipping the compatibility question. If your existing code is an AMX, you may not need the C++ API at all — test the backwards-compatible path first.
  • Treating contribution as optional. The server is fully open source and all contributions, big or small, are welcomed; bugs are expected and feedback is described as valuable.