Bot protection
Clickers, macros and private bots stop looking invisible. The system spots odd input, builds confirmations and leaves the call to you — no fairy-tale "100% detection".
Bots go where the anti-cheat can be talked into it
Shilen Guard never asks the client whether it is honest. Every session has to present a hardware signature, launch integrity and a live Edge verdict. No proof, no world entry.
7 days free · no prepayment · integration for your build · Interlude → Essence, L2J and PTS
TPM 2.0
hardware session signature
0
replay answers accepted
SHA-256
byte-exact client update
C1 → Essence
chronicles and builds
01 / CAPABILITIES
What Shilen Guard does
We do not promise "protection that cannot be cracked". We raise the cost of a bypass until farming and bot farms stop paying off.
Hardware-bound sessions
Every login must prove real hardware. On TPM PCs the session is signed in hardware — a stolen answer or a replay simply does not pass.
Hardware bans
We build a deep device fingerprint — not one serial, but a linked set of hardware signals. Swapped the SSD? We still recognise it.
Window and farm limits
You decide how many windows one machine may run. Virtual farms are cut off before they enter the game.
Integrity and memory
A swapped client, foreign modules and memory tampering do not go unnoticed. Edge stops that session from going further.
Cost of bypass
Competitors shout "forever". We say it straight: many things can be broken — but hours of work plus a hardware ban make it pointless for a bot farmer.
02 / COMPARE
Compare the promises
On the left — typical promises from other protections. On the right — how it actually works here.
They claim
What we actually do
"Forget bypasses. Your economy is protected forever"
Forever does not exist. We do something else: make bypass uneconomical — reverse work, hardware-ban risk and a live Edge verdict hit the farm business.
"Military-grade crypto. Licences sealed in TPM"
"Military-grade" is yesterday's marketing. Ours is the modern stack: X25519 + AEAD, Edge pinning and a TPM signature on every session. A replayed answer simply does not get in.
"AI bot detection, 99.97% accuracy"
Made-up percentages ban nobody. We accumulate repeatable input anomalies and show them to you — you choose the sanction by project policy.
"Hypervisor-level blocking"
Sounds loud. We cut farms differently: Anti-VM and environment checks before world entry plus an Edge verdict. No magic in the name.
"0 ms latency · SIMD 4× faster"
Zero milliseconds is marketing. We use AVX2/SSE2 and caching: heavy checks run aside, so players barely notice FPS impact.
"Integration in 5 minutes"
Not in five minutes — but for your L2J or PTS build, with a test loop and our help at every step.
03 / CHANGELOG
Changelog
Only changes that affect session proof, detection and the server-side verdict.
TPM challenge-response and session protocol
- [Hardware] TPM 2.0: one-time challenge, hardware key, nonce and Edge-side replay rejection
- [Protocol] Hard session version: mandatory auth proof and client version check
- [Integrity] HTTPS launcher auto-update with exact SHA-256 and controlled rollback
Behaviour loop and SIMD hashing
- [Anti-Bot] Input statistics: accumulate confirmations and evidence for the admin
- [Perf] BLAKE3 with runtime AVX2 / SSE2 / scalar dispatch — outside the game loop
- [Edge] Live heartbeat and server verdict for the whole session
Device graph and Anti-VM
- [HWID] Device graph: hardware anchors, identifier-change history and account links
- [Anti-VM] Environment checks: VM / sandbox / hypervisor before world entry
- [Policy] Blocks scoped to a project and a specific GameServer
Edge channel and memory control
- [Crypto] X25519 + AEAD, Edge certificate pinning and channel anti-tamper
- [Memory] Control of executable memory, modules and external process access
- [Session] Previous client version kept per project for safe rollback
04 / COMPATIBILITY
Chronicles and builds
Client and panel are universal. Server integration is tailored to your build.
Chronicles
InterludeHellboundGraciaHigh FiveClassicEssence
Server builds
L2JLuceraaCisMobiusPTS
05 / PLANS
Pricing
Transparent, no hidden fees. One licence per game server.
Start
€20/ mo
- 1 game server
- Client protection
- Hardware bans
- Monitoring panel
- Updates
Popular
Pro
€35/ mo
- Everything in Start
- Server-side protection
- Window limit
- Client file protection
- Priority support
Project
Custom
- Multiple servers
- Custom rules
- Help with your build
- Dedicated manager
Risk-free start
- 7-day trial with no prepayment
- Test loop on your own build
- Compatibility and load report
- Not a fit? Simply do not renew
Prices are indicative. Exact terms via Telegram / Discord.
06 / FAQ
FAQ
The environment is checked before world entry. You choose the response to VMs and sandboxes: log only, close the client or block.
No. On compatible PCs TPM adds hardware-backed session proof. When TPM is unavailable, the other independent checks keep working and the fact itself is visible in the panel.
No. It starts in shadow mode only: it collects statistics and shows confirmations to the admin. No automatic sanction is applied from a single behavioural signal.
Checks are time-bounded, repeated results are cached and hashing uses available SIMD instructions automatically. Heavy work never runs in the hot game loop.
Supported L2J builds use a ready integration. For PTS and custom builds the connection is tailored to the specific architecture.
Edge stops confirming the live session, after which the GameServer applies the configured project policy.
Yes. The project owner picks consequences per class: log only, close the client or block for a defined period.
The project runs through the Shilen Guard panel with active sessions, event history, device links, releases and blocks.