广州增城 （Zengcheng）Lv8.06

广州增城 (Zengcheng) Lv8.06 – a five-map campaign through a real city

This Chinese-language campaign has gathered over 1.51 million subscribers and takes survivors through five maps (zc1_m1 through zc1_m5) modeled on the real street layout of Zengcheng near Guangzhou — a remaster of the older v7.3 release with a reworked fourth chapter: cleaned-up alleys, extra loot and spawn points, and a new safe room as a checkpoint. The author openly lists known crash and performance issues per map, and links earlier versions (v7.3, v5.12, v2.11) for players who prefer them.

As a full campaign, this map needs to sit on your rented L4D2 server as well as on every connecting client, or the join attempt fails outright.

Tip: Since the author documents crash spots transparently, check the workshop page first before treating bug reports as a server-side problem.

Plan the rollout and operation

Because of the documented performance and crash risks, schedule Zengcheng as a test run first. Start each of the five maps directly, verify transitions, and play the revised fourth chapter and finale with four clients. Watch the server console and memory use at heavy spawn points. Keep an older working release only as a separate alternative and never mix its files with the remaster in the same Workshop collection.

Place the Workshop entry in a curated server collection and record whether it replaces a map, model, texture, animation, or dependency. Fully reload the server and test clients before an event, start affected maps directly, and inspect the console for missing materials, particles, or models. A smoke test covers lobby joining, map transitions, the core feature, and reconnecting with several players. Do not enable several add-ons that replace the same files; the Source engine often resolves those conflicts only through load order. Add packages one at a time and preserve the last working collection list. Check campaigns and libraries for dependencies before removal, while purely client-side textures can be disabled without save risk. This keeps server, Workshop-download, and local override failures distinguishable. Also record whether every player needs each entry or it is merely a local recommendation, so the collection and support guide set the same expectation.