System requirements by tier.
Every tier is designed around Obscurity's kernel driver, which is planned and not built yet. Core adds no other platform requirements. Advanced and Elite require TPM 2.0, Secure Boot, memory integrity and an active IOMMU, each checked on its own; on Elite the driver starts with Windows instead of with the game. This page explains what each one establishes, what it does not, and how a player can check their PC.
Status: in development. The verification described here is being built and is not yet enforced for any game. The requirements of each tier are fixed; details of the checks may change before release.
Principles
- Evidence over claims. A game client saying "Secure Boot is on" proves nothing. The decision is based on a statement signed by the PC's TPM in response to a fresh server challenge.
- A failed requirement is not a cheating accusation. It is a compatibility result with a specific reason and a way to fix it. It never leads to a ban on its own.
- We never change your settings. Obscurity does not modify firmware, boot, virtualization, disk-encryption or Windows security settings. If something needs changing, we explain it and you decide.
What each tier asks of a player's PC
The studio chooses the tier for its game. Players cannot pick a lower one, and Obscurity never switches off security features a PC already has.
| Core | Advanced | Elite | |
|---|---|---|---|
| Windows | Windows 11 (x64) on a release Microsoft services. Windows 10 22H2 (x64) is under evaluation. |
Windows 11 (x64) on a release Microsoft services. Windows 10 22H2 (x64) is under evaluation. |
Windows 11 (x64) on a release Microsoft services. |
| TPM 2.0 | Not required by Obscurity | Required | Required |
| UEFI Secure Boot | Not required by Obscurity | Required | Required |
| Memory integrity (HVCI) | Not required by Obscurity | Required | Required |
| IOMMU DMA protection | Not required by Obscurity | Required | Required |
| Obscurity kernel driver In development | Runs only while the game is running | Runs only while the game is running | Starts with Windows. Installing or updating it needs a restart. |
| Administrator rights | Needed once, to install the driver. Not needed to play. | Needed once, to install the driver. Not needed to play. | Needed once, to install the driver. Not needed to play. |
Not supported on any tier: Windows on ARM, 32-bit Windows, Windows Server. Virtual machines and most cloud-streamed PCs cannot satisfy Advanced or Elite, because a virtual TPM has no manufacturer-issued certificate to verify. Windows 10 22H2 has been outside standard Microsoft support since 14 October 2025.
TPM 2.0
A Trusted Platform Module is a security chip, or a protected function of the processor, that holds keys the operating system cannot extract and records measurements of the boot process.
What it establishes
A key that never leaves the TPM signs the evidence. The TPM's identity is certified by its manufacturer, so the server can tell a real TPM from software pretending to be one.
What it does not
A valid signature shows that a genuine TPM vouched for a boot state. It does not, by itself, prove that this TPM sits in the PC running the game, and firmware TPMs have had published vulnerabilities. Sessions are bound to the evidence to narrow that gap; it is not closed.
Check your PC
Press Win + R, type tpm.msc and press Enter. "Specification Version" should read 2.0 and the status should say the TPM is ready for use. If no TPM is found, look for a firmware setting named Intel PTT, AMD fTPM or Security Device Support.
UEFI Secure Boot
Secure Boot makes the firmware verify the signature of the boot loader, which in turn verifies the Windows kernel, before any of them run.
What it establishes
The PC started through a signed, unmodified boot chain. The firmware records the Secure Boot state in the TPM, and that record is covered by the signed evidence.
What it does not
Secure Boot protects the PC until the Windows kernel has loaded. It says nothing about software that runs afterwards.
Check your PC
Press Win + R, type msinfo32 and press Enter. "Secure Boot State" should read On and "BIOS Mode" should read UEFI. If BIOS Mode reads Legacy, the system disk must be converted before Secure Boot can be enabled: back up first and follow your PC maker's instructions.
Memory integrity (HVCI)
Hypervisor-protected code integrity uses Windows' built-in hypervisor to decide which code may run in the kernel, from a place the kernel itself cannot tamper with.
What it establishes
Kernel memory cannot be both writable and executable, and only validly signed drivers load. This removes the simplest ways for a cheat to run its own code in the kernel.
What it does not
A correctly signed but vulnerable driver can still be abused. Windows maintains a blocklist of known vulnerable drivers, which is enforced when memory integrity is on, but no blocklist is complete.
Check your PC
Open Windows Security, then Device security, then Core isolation details. "Memory integrity" should be On. If Windows lists incompatible drivers, update or remove them first, then restart. On older processors this feature has a larger performance cost.
IOMMU DMA protection
An IOMMU (Intel VT-d or AMD-Vi) controls which memory a hardware device may read or write directly. The requirement is that it is enabled in firmware and in use by Windows' hypervisor.
What it establishes
Devices cannot use direct memory access to read or alter the memory of the hypervisor and the secure kernel, which is what keeps memory integrity itself trustworthy.
What it does not
It does not wall off all game memory from every internal device. We do not require the separate "Kernel DMA Protection" setting to read On, because that feature depends on how a PC was built and its owner cannot switch it on. Its state is recorded, not required.
Check your PC
In msinfo32, "Virtualization-based security" should read Running and its "Available Security Properties" should include DMA Protection. If not, look for a firmware setting named Intel VT-d, AMD IOMMU or AMD-Vi.
Possible results
Each requirement returns exactly one of these, so players and support staff always know what happened.
| Result | Meaning | What the player is told |
|---|---|---|
| satisfied | Verified evidence shows the protection is active. | Nothing; the session starts. |
| feature_disabled | The PC supports the feature but it is switched off. | Which feature, and how to turn it on. |
| hardware_unsupported | The PC lacks the hardware for this feature. | That this PC cannot meet the requirement, and why. |
| os_unsupported | The Windows version or edition is not supported. | The supported versions. |
| verification_unavailable | The check could not be performed on this PC. | The specific obstacle and what to try. |
| evidence_invalid | Evidence was stale, malformed or failed signature checks. | To restart and retry. Repeated occurrences are reviewed, not auto-punished. |
| service_unavailable | Obscurity's verification service could not be reached. | That the problem is on our side and to retry shortly. |
Technical detail for developers: how verification works and what remains client-reported.
The Obscurity kernel driver
Every tier includes a Windows kernel driver, so that protection on the player's PC does not rest only on code a cheat can reach. On Core and Advanced it is loaded when the game starts and unloaded when the game exits. On Elite it is loaded early in Windows startup, so it can also report tampering that happens before the game is launched. It is our own implementation, and it is not built or distributed yet.
What it is not
It is not firmware-level protection and it does not run before Windows. Even on Elite it starts with Windows, after the firmware and boot loader, and it cannot see everything. It does not make cheating impossible.
What we commit to before release
Microsoft's driver certification, compatibility with memory integrity, testing on physical machines, a narrow documented interface, staged rollout with rollback, complete removal through Windows' normal uninstall, and a documented recovery path.
Your PC stays yours
The driver gates admission only to games protected by Obscurity. It must never block ordinary use of the PC, and if it fails Windows must still start and work normally. It does not change firmware, boot, disk-encryption or Windows security settings.