THE ORB
Uruchamiam studio

Most Skryptów: poradnik i samouczek

ESX, QBCore, Qbox, standalone: przenieś skrypt między nimi.

Poradnik wideo pojawi się wkrótce

Do tego czasu poradnik poniżej przeprowadzi cię przez każdy krok.

Na razie ten poradnik jest tylko po angielsku.

What it is

Script Bridge takes a script made for one framework and gives it back working on yours. A framework is the base your server runs on (ESX, QBCore or Qbox): every job, shop and inventory script talks to it, and a script written for one does not start on another. You drop the resource in, a free analysis tells you whether converting it is worth it and what it costs, and if you go ahead you download the whole resource back, rewritten for your framework, with a report of anything left for you to check.

Who it's for

  • Server owners who bought a script for ESX but run QBCore or Qbox, or the other way round.
  • Anyone moving a whole server from one framework to another, one resource at a time.
  • People who want to know before paying whether a script will convert cleanly, or whether it already runs on their server.

Before you start

  • The resource you want to convert: a .zip of it, or the folder itself. A resource is one folder inside your server's resources/ directory.
  • To convert (not to analyse): a THE ORB account on a paid plan, and enough credits. See pricing.
  • A test server where you can try the result before your live server.

Upload the resource and pick where it should run

The tool works on one resource at a time. If you drop your whole resources/ folder, each script inside it would be its own analysis and its own price, so pick the one you want to convert.

  1. 1

    Open Script Bridge

    Go to Script Bridge. The left rail shows the four steps: Upload, Analysis, Convert and Download.

  2. 2

    Choose the target framework

    In the panel, under Convert to, pick what the script should run on when you are done. Qbox is selected by default. You can change it later: re-reading is free and instant.

  3. 3

    Drop the resource

    Drag the .zip or the folder onto the box that says Drop your resource here, or use Choose a .zip or Choose a folder.

  4. 4

    Wait a few seconds

    You see four stages: reading the resource, reading the Lua, working out what belongs to the framework, and working out which database tables it uses. Nothing has been sent anywhere at this point.

Resources protected by escrow (Cfx's encryption for paid scripts) are refused. Their code cannot be read, so it cannot be analysed or converted. The tool says so instead of trying.

Which target to choose

OptionWhat you getPick it when
Native QboxThe script calls Qbox directly.Your server runs Qbox.
Native QBCoreThe script calls QBCore directly.Your server runs QBCore.
Native ESXThe script calls ESX directly.Your server runs ESX.
Universal BridgeA small bridge/ folder is added to the resource and works out at startup which framework the server has.You are not sure, or you may change framework later.
StandaloneNo framework at all. Money and job calls become empty hooks in config/hooks.lua.Your server has no framework. Someone has to fill those hooks in.

Community Bridge also appears in the list, marked as coming soon. You cannot pick it yet.

Read the analysis: is it worth it?

The analysis is free and runs entirely in your browser. It answers one question first, in a coloured verdict at the top:

VerdictWhat it means for you
Worth doingThe script converts cleanly. Expect little or nothing left to check.
Doable, with caveatsIt converts, but some parts will need someone to look at them afterwards. The reasons are listed under the verdict.
You may not need thisIt already runs on what you picked. For example, most QBCore scripts already run on Qbox. Try it on your server first.
Not convertibleThere is nothing to sell you, so there is no price and no button. The reason is shown (see below).

Under the verdict you see four numbers: how many times the script talks to the framework, how many of those have a known equivalent, how many need reasoning, and how many files will be rewritten. Below that, folded sections list the things that will need your attention, the database tables the script keeps its own data in, and every file with its line count.

  • A resource with no Lua, or with no framework code in it, is not convertible: there is nothing to change.
  • A single file over 1,400 lines cannot be converted in one go. If every file that touches the framework is over that, the resource is refused.
  • More than 12,000 lines of framework code in total is too big for one conversion.
  • If a large share of the files cannot be read as valid Lua, it stops there. One or two broken files only show a warning.

Changing the target in the panel re-runs the analysis on the spot. You do not need to upload again.

Check the price before you pay

When the verdict allows a conversion, the panel shows the Price row with the exact number of credits and your balance. Nothing is charged until you press the button.

  1. 1

    Open the Price row

    It says how many lines ORBIE will rewrite and in how many files. Only the files that actually talk to the framework count: the rest of the resource is not part of the price.

  2. 2

    Open How this price is worked out

    The price is 3 credits to start, 1 per file that has to be rewritten, and 1 per 45 lines of framework code, with that last part multiplied by how much judgement those lines need. The reasons for the multiplier are listed.

  3. 3

    Check what leaves your browser

    The panel lists it: the files that touch the framework and the manifest (fxmanifest.lua) are sent to be converted. Images, language files and the NUI page stay on your computer.

Converting is for paid plans. On the Free plan the analysis works, but pressing convert opens the plans window. If your credits do not cover the price, the button says Not enough credits and a link to get more appears under it.

Convert it with ORBIE

  1. 1

    Press Convert with ORBIE

    The price is on the button. You must be signed in. The credits are taken at this moment.

  2. 2

    Keep the tab open

    The screen shows how many files are done out of the total. Each file is rewritten, then read back and compared with the original, function by function and event by event, to make sure nothing was lost.

  3. 3

    Read the result

    When it finishes, the viewer says how many files were rewritten for your framework and, if some did not make it, how many credits came back.

If a file's conversion does not pass the checks after a second try, your original file goes in the download instead, untouched. Those files are listed as left exactly as you wrote them, with the reason.

If the price changes between the analysis and the click (for example, because the files changed), the tool re-analyses and shows you the new price instead of charging the old one.

Understand what came back

The result screen has up to four sections. They are what someone should look at before the script goes live:

  • Files left exactly as you wrote them: the conversion did not hold up, so your original is in the zip.
  • Places left for you to decide: spots the conversion deliberately did not touch. Each one is marked inside the file with -- @bridge:TODO, so whoever reviews it can search for that text.
  • Files to read before deploying: files that came back with low confidence (under 60%).
  • What changed, file by file: the notes for each converted file and its confidence.

Press Download resource in the panel. The zip is put together in your browser from the converted files and the parts that never left your computer.

What you download

You download one .zip named after the resource and the target, for example my_script_qbx.zip. Inside:

  • The whole resource: rewritten files where something changed, every other file exactly as you uploaded it.
  • fxmanifest.lua with its dependencies pointed at the new framework. Without that the resource would refuse to start on your server.
  • BRIDGE_REPORT.md: what changed outside the code, what to check before starting it, which files could not be converted, which came back with low confidence, and what happens to your data.
  • For Universal Bridge and Standalone: a bridge/ folder that the manifest loads first. Standalone also adds config/hooks.lua.
  • If the script keeps its own data: sql/install.sql, which creates its tables if they are missing.
  • If the old and new framework identify players differently: sql/migrate.sql, which links the rows already saved to the new player key, so nobody loses what they had.

Install it on your server

  1. 1

    Back up first

    Copy the old resource folder somewhere outside resources/. If the script has its own tables, back up your database too.

  2. 2

    Replace the folder

    Unzip the download and put the resource folder in resources/ in place of the old one. Keep the same folder name so your server.cfg still finds it.

  3. 3

    Run the database files if there are any

    If the zip has sql/install.sql, read it and run it in your database. If it has sql/migrate.sql, run it after your backup. It only adds columns and never deletes anything, and its last query shows how many rows matched.

  4. 4

    Start it on a test server

    Start the server, or type ensure followed by the resource name in the server console. The converted script has not been run by us: try it before your players do.

  5. 5

    Check the open points

    Have someone search the files for -- @bridge:TODO and read the files listed as low confidence in BRIDGE_REPORT.md.

Do not reorder the bridge/ entries the tool added to the manifest. They have to load before the rest of the script.

Common problems

It says the resource is escrow-protected.

The code is encrypted by Cfx and cannot be read, so it cannot be converted. Ask the seller for a version for your framework.

The verdict is Not convertible and there is no price.

Read the reason under the verdict. Usually the script has no framework code (it already works anywhere), a file is over 1,400 lines, or the whole thing is over 12,000 lines of framework code. Nothing was charged.

Pressing convert opens the plans window.

Converting comes with a paid plan. The analysis stays free. See pricing.

The resource does not start after converting.

Look at the server console for the first red line and paste it into Server Fixer. Also check that you ran sql/install.sql if the zip had one, and that you did not move the bridge/ lines in the manifest.

Players say their items or progress are gone.

The script stores data under each player's key, and the new framework uses a different key. Run sql/migrate.sql from the zip (after a database backup). If the report says some rows complete when the player joins, those fix themselves the first time each player logs in.

Some files came back untouched.

Their conversion failed the checks twice, so you got your original instead of something broken. The credits for those files came back automatically. Those files still need someone to convert them by hand.

Questions

Is the analysis really free?

Yes. It runs in your browser, needs no sign-in, and nothing is sent anywhere until you press convert.

What is sent when I convert?

Only the files that talk to the framework, plus the manifest. Images, sounds, language files and the NUI page never leave your computer. The zip is built in your browser.

What if the conversion fails?

If nothing usable comes back, you get all your credits back. If only some files fail, you get back the part of the price for those files. The 3-credit start is only kept when something was delivered.

My script is QBCore and my server is Qbox. Do I need this?

Usually not: Qbox runs most QBCore scripts as they are, and the analysis says so. You can still convert if you want native Qbox calls.

Can I close the page while it converts?

Keep the tab open. The download is assembled in this tab from your original files, so closing it means uploading again.

Does it convert the NUI (the on-screen menus)?

No. Only the Lua that talks to the framework is rewritten. If the script sends framework data to its menu, the analysis warns you, because the menu's code may expect the old format.

Checked against the tool on November 15, 2026.

Wypróbuj Most Skryptów teraz

Kupiłeś skrypt pod zły framework? Upuść go i odbierz działający na twoim, razem z uczciwym raportem o tym, czego nie dało się przenieść.

Więcej poradników: Skrypty