I went through this problem on my versus servers and found it was caused by a combination of cvars and a plugin:
Quote:
The spawn issue I posted about back then was resolved, but not due to the factors he listed, nor was it caused by FMC. The issue was caused by the cvars allowing an all bot survivor team in versus, which allows a single player to play infected, interacting with a plugin using the same cvars:
cvars previously in server.cfg
sm_cvar sb_allbot_game 1
sm_cvar allow_all_bot_survivor_team 1
sv_hibernate_when_empty 1
combined with:
[L4D2] Survivor AI Trigger fix
This plugin also applies the bot cvars when a single player is in a versus server. Hence, the redundant use of the bot cvars in the server.cfg (always on) and in the Survivor AI Trigger Fix plugin caused the spawn bug.
Removing the bot and hibernation cvars from the server.cfg resolved the issue on all three versus servers and it has never returned. My versus servers get a good amount of traffic, so players would have reported a spawn problem if it still existed.
|
However, after the most recent game update the spawn distance bug suddenly returned. Removing the
[L4D2] Survivor AI Trigger fix plugin entirely stopped the problem and it has not occurred since.
Regarding sm_cvar z_spawn_safety_range 250 // (default 500):
I too used this cvar in the server.cfg as a workaround for the spawn distance issue. However, be aware that this affects the minimum spawn distance for Bot Special Infected too, allowing them to practically spawn right on top of survivors. It is most noticeable when the infected team only has 1-2 people and the rest are bots.
Best regards,
PatriotGames