Every executor quotes a UNC or sUNC figure and almost nobody explains what it measures. It is the most useful number available when choosing one, and it is also routinely misread. This covers both.
The problem it solves
A script is code written by one person. An executor is a program written by someone else. For the script to run, it has to be able to call functions the executor provides — and historically every executor named those functions differently, or implemented them slightly differently, or not at all.
The result was that a script written for one executor would not run on another, and script authors had to write compatibility shims for every tool. UNC exists to stop that.
What UNC is
UNC stands for Unified Naming Convention. It is a community-agreed list of the functions an executor should expose and what each one should be called.
If two executors both implement UNC, a script calling a standard function works on both without modification. It is an interface agreement, in the same way that two different web browsers agreeing on JavaScript means one page works in both.
UNC checks names, not behaviour
This is the important limitation. A UNC test can confirm a function exists under the right name. It cannot confirm the function actually does the right thing when called.
What sUNC adds
sUNC — strict UNC — is the response to exactly that gap. Rather than checking a function exists, it calls it and verifies the result is correct.
This matters because an executor can trivially score highly on a name-based test by defining stub functions that exist and do nothing useful. Under sUNC those stubs fail, because the test checks what came back.
| UNC | sUNC | |
|---|---|---|
| Checks | Does the function exist? | Does it behave correctly? |
| Can be gamed by stubs | Yes | No |
| Typical scores | Higher | Lower and more meaningful |
| Predicts real compatibility | Loosely | Considerably better |
When an executor quotes both, the sUNC figure is the one worth reading. A tool advertising 99% UNC and a much lower sUNC is telling you, without meaning to, that a lot of its surface is nominal.
How to read the numbers
These are self-reported
There is no neutral body publishing verified scores. Developers run the test suites and report their own results. Treat a quoted figure as a claim from an interested party, not a specification.
That does not make them worthless — they are still the best signal available, and a developer quoting a modest sUNC figure honestly is telling you something useful. But two things follow.
- Compare tiers, not decimals. The difference between 60% and 90% means something. The difference between 94% and 96% is noise.
- The failing functions matter more than the percentage. An executor missing something niche is fine. One missing a function your script depends on is unusable at any score.
What this means when you are buying
- Find the script first and check what it requires. Some state a minimum sUNC level; some name specific executors.
- If the script names executors, buy one of those. That is a tested answer and beats reasoning from percentages.
- If it states a requirement, match it. Do not assume a higher headline number covers a specific requirement.
- If it says nothing, a broadly compatible executor is the safe default — and a script with no stated requirements is usually a simple one.
Of the executors we carry, Isaeva advertises full sUNC support and is the one to look at if you are running demanding scripts. Volt is the broader default for mainstream community scripts. Both are on the products page with current pricing.
IsaevaAdvertises full sUNC support. The compatibility-first option.View →Why a high score still does not guarantee anything
Compatibility is necessary but not sufficient. A script can fail on a fully sUNC-compliant executor because the game updated, because the script targets a different game version, because it was written against a non-standard function outside the convention entirely, or because the executor is stable in testing and not under load.
sUNC tells you the executor speaks the language. It does not tell you the conversation will go well.
Common questions
What does UNC stand for?
Unified Naming Convention — a community standard for what functions an executor exposes and what they are called.
What is the difference between UNC and sUNC?
UNC checks a function exists under the right name. sUNC calls it and checks the result is correct, so it cannot be passed with stub functions.
Is 100% sUNC possible?
Developers claim it. Since scores are self-reported and the test suites change, treat any figure as a claim rather than a verified measurement.
My script does not run on a high-sUNC executor. Why?
Compatibility is only one failure mode. The game may have updated, the script may be out of date, or it may rely on something outside the convention.
Do I need to care about this if I only run simple scripts?
Not much. Simple autofarms use common functions that almost every executor implements. It matters as scripts get more demanding.