Back To School (Chapter 1)

Back To School (Chapter 1) – the opening of a seven-part campaign

Close to 962,000 players have subscribed to this first of seven parts in the "Back To School" series. Chapter 1 – Forest – takes survivors from a forest camp past a barricaded gorge and a military checkpoint into an abandoned mine. The six maps support campaign and versus, adding ten panic events, a non-linear finale, extra models and textures, and three custom-voiced NPCs.

Important for server operators: this is only part one of seven — the author requires subscribing to all seven via the Workshop collection, or later chapters won't load. The full campaign must sit on both your L4D2 server and every client.

Tip: Link the full "Back To School" collection in your server description instead of this chapter alone, or players get stuck between chapters.

Plan the rollout and operation

Back To School Chapter 1 is a connected campaign part and should be distributed as a complete package rather than map by map. Check all six maps, panic events, the nonlinear section, and the transition into the mine with a full lobby. Make clear that this is only the first part of the series. When later chapters are installed, keep their Workshop entries separate but together in one curated collection so no files are missing.

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.