S
Partial coverage
Solara
ScriptBunker records 59% sUNC and Detected. A much larger gap, but the same question: which functions are missing, and does your script need them?
01
What 98% actually means
Synapse Z passes 98 of the 100 standard sUNC tests. That means 98 functions are implemented and working. It does not mean 98% of scripts will work, because scripts depend on specific functions, not on the average.
The two missing functions are not a random sample. They are a specific gap. A script that needs one of them will fail completely, regardless of how many other functions pass.
02
The missing functions
ScriptBunker's test page records the total: 98% sUNC and 99% UNC . The individual function results are not published in the same detail as the totals. What is documented: the test runs 100 functions, and 98 pass.
getgenvpasshookfunctionpassreadfilepassDrawing.newpasssetclipboardpassgetrawmetatablepassmissing #1failmissing #2failThe named functions above are illustrative. The two failing functions are not named in the public test summary reviewed here. A script that depends on either of them will not run on Synapse Z.
03
The detection flag
ScriptBunker marks Synapse Z as Detected. The same page carries a caveat that applies to every tracker entry: "Not marked detected" is not a guarantee of safety, and ScriptBunker does not verify the upstream data . The caveat works in reverse too. "Detected" means the anti-cheat recognizes the executor. It does not mean the executable contains malware.
A 2024 Roblox DevForum post from an anti-cheat release thread names Synapse Z among executors that were detected and could not bypass Hyperion . That is a forum comment from two years before the current tracker entry. It is a historical data point, not a current verdict.
04
The delivery path
The GitBook page documents the installation steps: download the Synapse Z Installer from z.synapse.do, enter a purchased key, press Install, then Launch Roblox. After injection, press F1 to open the Internal UI .
A download link on a GitBook page is a delivery instruction, not a source audit. The page tells you where to get the file and how to use it. It does not tell you what the file contains, whether the link resolves to the same binary the developer built, or whether the key system has been compromised.
Sources: ScriptBunker Synapse Z · Rscripts executor list · GitBook installation page . The sUNC score, the detection flag, and the delivery path are separate records.
Why 98% is not "almost 100%"
sUNC is not a percentage of quality. It is a count of functions. 98% means two functions are absent. A script that calls either of them will throw a runtime error, regardless of how many other functions pass.
The practical consequence depends on what you run. A script that uses only the 98 passing functions will work exactly as it would on a 100% executor. A script that depends on one of the two missing functions will not work at all. The average is meaningless for the individual script.
This is why comparing executors by sUNC percentage alone is misleading. A 98% executor and a 100% executor are equivalent for the 98 functions they share. They differ only on the two functions that one has and the other does not. Without knowing which functions those are, the percentage does not tell you whether a specific script will run.
Why the delivery path is a separate record
The GitBook tells you to download from z.synapse.do and enter a key . That is a commercial distribution model: the file is gated behind a purchase, and the installer handles the key validation. The tracker records the version and the function score. The GitBook records the purchase and installation flow.
Neither record tells you whether the binary served from z.synapse.do matches the build the tracker tested. That gap is not unique to Synapse Z. It is the standard gap between a tracker entry and a binary delivered through a commercial channel. The tracker measures the output. The GitBook describes the input. The file in between is not audited by either.
The record, with its gaps marked
| Attribute | Value | Source type | Confidence |
|---|---|---|---|
| Version | 1.0.3.7 | Third-party tracker | Recorded |
| sUNC | 98% | Third-party tracker | Recorded |
| UNC | 99% | Third-party tracker | Recorded |
| Detection | Detected | Third-party tracker | Recorded |
| Delivery | z.synapse.do | GitBook | Project docs |
| Missing functions | Not named | — | Unknown |
| Sandbox score | Not found | — | Unknown |
"Recorded" means the source published the value. "Unknown" means no source was found at review time. Neither is a safety rating.
What this page does not claim
- This page does not claim Synapse Z is malware-free. A 98% sUNC score measures function coverage. It does not audit the executable.
- This page does not claim the GitBook link to
z.synapse.dodelivers a safe file. It documents that the link exists . It does not audit the binary behind it. - This page does not claim the 2024 DevForum comment about detection is still accurate. It is a historical data point from a forum thread, not a current status report .
Synapse Z questions, separated from the lineage marketing
Does 98% sUNC mean almost every script works?
No. It means 98 of 100 standard functions pass. A script that calls one of the two missing functions will fail completely. The percentage is an average across functions, not a probability that a specific script will run.
What does "Detected" mean for Synapse Z?
ScriptBunker marks the build as Detected, with the standard caveat that "not marked detected" is not a guarantee of safety . Detected means the anti-cheat recognizes the executor. It is a ban-risk signal, not a malware verdict.
Can I see which two functions are missing?
The public test summary reviewed here does not name the two failing functions. It records the total: 98% sUNC and 99% UNC . The individual function results are not published in the same detail. A script that depends on either missing function will not run.
Is the GitBook an official source?
It is a project-controlled documentation page. It describes the installation steps and links to z.synapse.do for the installer . A project-controlled page can describe how to obtain a file without describing what the file contains.
Can I download Synapse Z from this page?
Not yet. The Download button is a placeholder. When you have a confirmed source and choose to link it, replace the href. Until then, this page serves no file.
Why does this page look different from Potassium's?
Because the evidence is shaped differently. Potassium has a distribution model and six independent facts. Synapse Z has layers of related evidence: a coverage score, a missing-function gap, a detection flag, and a delivery path. The layout stacks those layers vertically so each one is read on its own terms.
Related profiles
W
Tracker only
Wave
ScriptBlox records 100% sUNC and a team change from 2025. Full coverage does not resolve the continuity question.
P
Tracker only
Potassium
Discord-gated distribution, kernel-level injection, Triage 6–7/10. The channel is documented. The file is not on a public page.