What is sUNC and Why It Matters for Roblox Executors
sUNC measures whether an executor's functions actually work. It replaced UNC because UNC was easy to spoof. An executor's sUNC score is the single most useful number on its page.
What sUNC Stands For
sUNC stands for senS' Unified Naming Convention. It is a tool designed to check if an executor can properly run essential global functions [citation:2]. The test suite is maintained by the sUNC project and published at docs.sunc.io.
The "senS" part refers to the developer who created the test. The "UNC" part is inherited from the older Unified Naming Convention standard that sUNC replaces.
Why UNC Wasn't Enough
The original UNC is now outdated and prone to spoofing. Executors could fake their environment to appear to pass UNC tests without the underlying functions actually working [citation:2].
A script that checked "does this executor have the writefile function?" would get a "yes" from an executor that had registered the function name but whose implementation crashed when called. The function existed in name only.
This made UNC scores meaningless. An executor could advertise 100% UNC and still fail on real scripts.
How sUNC Is Different
sUNC tests functions as if they were being used in a real scenario. It doesn't just check that a function exists — it calls it and verifies the result [citation:2].
The test suite runs a standardised set of checks against the executor and reports how many pass. On ScriptBlox, for example, an executor page shows both the sUNC percentage and the number of functions that passed, such as "86 of 86 functions pass" for a 100% score [citation:16].
How to Read sUNC Scores
| Score | What it means |
|---|---|
| 100% | All standard functions work. The executor runs almost every script. |
| 90–99% | Minor gaps. Some advanced scripts may fail. |
| 80–89% | Standard baseline for most farming scripts. |
| 70–79% | Noticeable function gaps. Many scripts will throw errors. |
| Below 70% | Basic functionality only. Expect failures on most scripts. |
RageInject marks scripts as requiring "80%+ sUNC" or "90%+ sUNC" based on the functions they use. If your executor's score is below the requirement, the script will not run correctly.
Where to See Live sUNC Scores
sUNC scores are tracked on every major executor listing site:
- Rscripts — lists sUNC scores on every executor page [citation:3]
- ScriptBlox — shows both sUNC percentage and passed function count [citation:16]
- sUNC.io — the project's own test results
RageInject references these sources on every executor page rather than self-reporting scores, because third-party testing is more trustworthy than a vendor's own claim.
Why This Matters for You
If you download a script that requires 90% sUNC and your executor scores 75%, the script will fail. It will throw errors like "attempt to call a nil value" for missing functions, and the failure will not be obvious unless you know to check the score.
Before downloading a script, check its sUNC requirement. Before running it, check your executor's score. If your score is too low, either use a different executor or find a script that requires less.
- Check the script page for its sUNC requirement
- Check your executor's sUNC score on Rscripts or ScriptBlox
- If your score is lower, switch to a higher-sUNC executor
- If your score meets the requirement, the script will run
Frequently Asked Questions
What does sUNC stand for?
sUNC stands for senS Unified Naming Convention. It is a test suite that checks if an executor can properly run essential global functions [citation:2].
Why is UNC outdated?
UNC is prone to spoofing. Executors could fake their environment to pass UNC tests without the functions actually working. sUNC tests functions as if they were used in a real scenario [citation:2].
What sUNC score should I look for?
100% is ideal but not required for most scripts. 80% or higher runs the majority of scripts on RageInject. Below 70% you will hit missing-function errors on many scripts.
Where can I see live sUNC scores?
Rscripts and ScriptBlox track sUNC scores on every executor page. The sUNC project itself publishes test results at sunc.io [citation:3][citation:16].