Per request: drop framework-level comparison, drop arguments based on
field/class/method names (those are renamed during deobfuscation and
do not prove plagiarism by themselves). Keep only the 14 modules
listed by the user plus the utility classes, and back every claim
with actual code blocks placed side-by-side so a reader can see the
two snippets are the same thing.
Modules included: AntiBots, CrystalAura, AntiFireball, Scaffold,
FastWeb, Stuck, AutoMLG, SafeWalk, Disabler, AutoTools, ChestStealer,
InventoryManager, ChestESP, Compass, Projectiles, plus a utility-
class section (ChunkUtil, RotationUtil, BlockUtil, MovementUtil,
RayTraceUtil).
The evidence now hinges on three categories of artefacts that
deobfuscation cannot fabricate: string literals ("Fake Staff Detected!
(", "Stream limit didn't work.", "点击使用", "Normal"/"Telly Bridge"
/"Keep Y", etc.), magic constants (+1337, (0.88,1.88,0.88), > 2 &&
< 0.0001, i*i+1, 72000, 0.6/0.2/1.2, +1.62, RGB (173,12,255)...),
and signature import/dead-code fingerprints (antlr-runtime's
OrderedHashSet used in a rotation util; MovementUtil.getDirectionAngle
copied verbatim despite being a private unused method).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Populate paste/README.md with a per-module / per-subsystem comparison
between OpenZen (this repo, deobfuscated from Zen client) and
Naven-Modern (github.com/Margele/Naven-Modern). Findings collected by
running parallel agents against both source trees:
- Functional modules: 30+ Zen modules trace back to a 1:1 Naven
counterpart, either same-named or renamed (e.g. KillAura<-Aura,
CrystalAura<-AttackCrystal, ESP<-Glow, InventoryManager<-
InventoryCleaner using Naven's @ModuleInfo internal name). Setting
strings, default values, ranges, RGB constants, and even Chinese
literals like "点击使用" survive verbatim.
- Framework: EventBus/EventTarget/EventPriority are the renamed twins
of Naven's EventManager/EventTarget/Priority (same DarkMagician6
EventAPI shape, identical default byte priority 2). Module,
ModuleManager, Setting/Value, CommandManager, util classes (
RotationUtil keeps Naven's odd antlr OrderedHashSet import,
ChunkUtil keeps "Stream limit didn't work.") all line up.
- Fingerprints that can't be hand-waved away: +1337 magic offset in
Stuck; the typo 'Recorvey' carried over from rewrites; the
Projectiles RGB triplets (173,12,255)/(255,238,154); identical
sensitivity-GCD formula scaled*scaled*scaled*1.2F.
The doc also tabulates module-level severity ("line-by-line" / same-
name+rewrite / not plagiarized) so readers can skim before diving in.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
README: clarify that the deobfuscated jar is the latest one as of
2026-05-21 (rather than an old build, as some users seem to assume),
collapse a stray hard wrap, and link to a new paste/ subtree that
will track which modules were lifted from the Naven client.
Also rename KillAura.aimRange to attackRange to match the user-facing
'Attack Range' label and how the field is actually used in the in-FOV
check.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Shirona1337