Use L4D2 Tools to find installed maps, choose a default map and mode, or change levels during a session. New custom maps must be installed separately before they appear in the list; the tool does not download Steam Workshop content.
Read the current map and mode
The page shows the current default map and mode. Choose from co-op, realism, versus, survival, and scavenge. Match the mode to the map; survival maps usually need survival mode.
Use Detect Maps to view available maps, then select the one you want. The map filter and Addon maps only checkbox can help narrow the list. If you enter a map manually, use its BSP name without the .bsp extension.
Set a default map safely
Before changing the default, note the current map and mode so you can restore them if needed. Select the map and matching mode, then choose Save Default. Confirm the expected level loads when the server starts. Change one setting at a time so you can identify the cause if something goes wrong.
Use Save Default when you want a map to load on a future server start. Choose Change Level Now when you want to move an active session to another map. The immediate change interrupts play, so tell everyone first and confirm they are ready to rejoin.
If the group is about to play a scheduled session, test first with a small number of players. Confirm that the map loads, the mode is appropriate, and players can connect. Keep the previous working map and mode recorded so you can restore them quickly if needed.
Change the level now
Change Level Now requests an immediate level change. Use it only after confirming the map is installed and the mode matches. Warn current players before changing levels because it interrupts the session. After the request, inspect the result panel and console output; if the server reports a failure, return to the last known working selection and investigate before retrying.
Diagnose a missing or failing map
If a map is not listed, run detection again and check the filters. If it still does not appear, it may not be installed in a location the server can detect. Install the map on the server before trying to select it; subscribing from your game client does not add it to the server.
Use Addon maps only to narrow the detected list. Select the installed map and verify the mode separately. If you enter a name manually, omit the .bsp suffix and use the BSP identifier rather than its display title.
If a detected map fails to load, verify its name and mode, review console output, and test a known working map. If that map loads, check whether the custom content supports your server version and selected mode before changing RAM.
When a Change Level request returns an error, do not immediately repeat it with another guessed identifier. Copy the console message, restore the known working default, and confirm the server is stable. Then test one detected candidate at a time. This keeps the current session recoverable and provides useful evidence if the content itself is incompatible.
Use player and message controls
The L4D2 Tools screen also has Refresh Players and a message field with a Say action. Use refresh to retrieve the current player list before taking an administrative action. Messaging is useful for announcing a planned level change or maintenance. Keep messages brief and do not expose private server credentials in them.
The broader manager provides console, Properties, resources, logs, and account controls. Use permissions deliberately; shared users may not have the same rights as the owner. Review the L4D2 management documentation for the current navigation.
Plan around supported content
To prepare a custom session, detect an installed map, choose its matching mode, save the default or test a level change, then check the console and join the server. For current server options and resource estimates, see Left 4 Dead 2 hosting.
