case-study 2026-10-10 case-studyclean-roomghidrarustauthorized

GunZRs: clean-room Bevy port with REA/Ghidra helpers

Same compliance pattern as OpenBattlefield2: **engine/port without shipping game content**, bring a lawful install, keep REA/Ghidra as investigation helpers.

Source meta

0 GitHub stars (snapshot)

Language: Rust

License: Apache-2.0

Updated: 2026-10-10

GitHub source ↗

rea.run rating

5/5 — Clean-room + REA/Ghidra framework

Quality. Apache-2.0 Bevy port; BYO Steam install; no shipped game files; REA scripts/docs.

Evidence. REA+Ghidra via scripts/ and reverse-engineering docs; fixture timings mentioned upstream.

Limits. Needs a lawful GunZ install; not an online crack or server emulator guide.

For. Engine/rebuild hackers studying clean-room + agent RE loops.

What it is. Clean-room Rust port on Bevy that reads .mrs archives from a Steam install and never runs Gunz.exe. Demo media are captures, not redistributed game files.

Relation to REA. scripts/ and reverse-engineering docs wire REA+Ghidra for static investigation of binaries you supply from your install.

Workflow. Own Steam copy → build gunz-play → use REA helpers for Evidence on authorized binaries → feed findings into the open port.

Evaluation. Strong clean-room narrative. Stars still zero; treat as early but well-framed.

Compliance

Clean-room port reading YOUR Steam install only. No retail crack, no shipped .mrs/game binaries in the repo.

Takeaways

BYO install is the compliance key.
Ports must not redistribute game bytes.
Agent RE stays static-first on your copy.

Related on rea.run