Porting check

The porting check is a small script that reads a folder of FiveM resources and writes a report. It never runs your code and does not send anything anywhere.

Run it

You need Python 3.10 or newer. No packages.

python3 scan.py /path/to/server/resources --out report.md
python3 scan.py /path/to/server/resources --json

The script is part of the GAMPEON SDK (porting-kit/scan.py). Ask the GAMPEON team for access while the SDK is not public yet.

What the report shows

For every resource:

• Runtime calls that GAMPEON already supports (events, exports, threads).
• Platform calls such as GetPlayerName, RegisterCommand or NUI that GAMPEON will provide in its own API.
• GTA natives that must be replaced, with how often each is used.
• Frameworks in use: ESX, QBCore, Qbox, ox_lib, MySQL, ox_inventory, target systems.
• ESX and QBCore calls (ESX.*, xPlayer.*, QBCore.Functions.*, Player.Functions.*) and which of them the RP Starter bridges do not cover yet. Functions that exist in a bridge but do nothing yet, such as weapons, count as missing.
• NUI pages and streamed assets. Streamed models and maps are flagged: check the rights and rebuild them, never copy them.
• An estimated difficulty from low to high.

Limits

The check uses patterns, not a full Lua parser. Global functions from other resources that start with a capital letter can be counted as natives. The result is an estimate for planning, not a guarantee.

What happens with the results

If you share reports with the GAMPEON team, the most used natives across many servers decide the order in which GAMPEON builds its game API.