Internal-tooling material. A photographed editor viewport with wireframe and navmesh overlays, a blockout-stage build frame, and a 900-line build log that names every level-streaming zone.
Collected by Cyberleekers · August 27, 2026
The editor screenshot was on a contractor’s LinkedIn portfolio for roughly six hours. It shows a 3D viewport with a Vice Beach street scene, green navmesh polygons, wireframe overlays, and an outliner panel with a tree of zone names. We have blurred the outliner text in the FIELD copy because it contains what look like internal codenames.
The blockout frame shows the same street at an earlier stage: grey geometry, checkerboard placeholders, a T-posed character. It came from a Glassdoor review attachment that was pulled. The camera angle matches the editor screenshot closely enough that we believe it is the same scene months earlier.
The build log lists streaming zones with load times. There are 41 zones. We can map 33 of them to the community map; the remaining eight are in the north-west and support the second-city theory in CL-006.
Field access required
Hold ≥ 10K $CYBERLEEK
Photographed off a monitor. Outliner text blurred in this copy.
Archive access required
Hold ≥ 100K $CYBERLEEK
Same photo with the outliner panel unblurred. Zone codenames readable.
Field access required
Hold ≥ 10K $CYBERLEEK
Grey geometry, checkerboard placeholders, T-posed character. Camera matches the editor shot.
Archive access required
Hold ≥ 100K $CYBERLEEK
Zone names with load times. Eight zones do not map to the current community map.
Archive access required
Hold ≥ 100K $CYBERLEEK
Tooling source from a deleted repo. References the same zone naming scheme as the build log.
Source access required
Hold ≥ 1M $CYBERLEEK
Everything from the deleted repo and the Telegram channel, unmodified.