Map Configuration

Each map has its own config file. The plugin won't work without this file.

These files are stored in configs/bwrr/map/'map name'.cfg.

You can add a _server suffix to config file to prevent your custom config being replaced on an update.

Hint: The command sm_bwrr_editor allows to easily add new spy and engineer teleport points.

Available Settings

SpawnPoints

• normal - List of info_player_teamspawn to use for normal robots.
• giant - List of info_player_teamspawn to use for giant robots.
• sniper - List of info_player_teamspawn to use for sniper robots.
• spy - List of info_player_teamspawn to use for spy robots.

You can get the name for spawnpoints by decompiling the map or using an entity lump editor. I also recommend looking on the map population scripts to get an idea of where bots are spawning.

HatchTrigger

As of 4a4f2c5 this entry is deprecated.

Gatebot

• stun_duration - How long in seconds robots are stunned when a gate is captured.

RobotScaling

• limited_size - Limit the maximum size a robot can be?

Giants robots might get stuck on some maps, specially converted maps ( like mvm_2fort ). Setting 'limited_size' to 1 will limit the robot size to prevent them from getting stuck.

SpyTeleport

List of coordinates to teleport spy robots.

EngineerTeleport

List of coordinates to teleport engineer robots.

Example

"MapConfig"
{
	"SpawnPoints"
	{
		"normal" "spawnbot"
		"giant" "spawnbot_giant"
		"sniper" "spawnbot_mission_sniper"
		"spy" "spawnbot_mission_spy"
	}
	"HatchTrigger"
	{
		"tank_relay" "boss_deploy_relay"
		"cap_relay" "cap_destroy_relay"
	}
	"Gatebot"
	{
		"stun_duration" "22.0"
	}
	"RobotScaling"
	{
		"limited_size" "0"
	}
	"SpyTeleport"
	{
		"1"
		{
			"origin" "-571 -2203 490"
		}
		"1"
		{
			"origin" "365 -2222 490"
		}
	}
	"EngineerTeleport"
	{
		"1"
		{
			"origin" "422 1882 380"
		}
		"1"
		{
			"origin" "779 1397 682"
		}
	}
}