[luki1412]

Description:

This plugin blocks/limits classes for bots!
It can run alongside Class Restrictions For Humans that blocks/limits classes for humans

Cvars:

PHP Code:

sm_crb_enabled 1 //(0/1, default 1) Enable/disable restricting classes for bots in TF2.

sm_crb_blu_demomen -1
sm_crb_blu_engineers -1
sm_crb_blu_heavies -1
sm_crb_blu_medics -1
sm_crb_blu_pyros -1
sm_crb_blu_scouts -1
sm_crb_blu_snipers -1
sm_crb_blu_soldiers -1
sm_crb_blu_spies -1
// Limits for Blu bot classes in TF2. (-1 for no limit, 0 is disabled, 1 or anything higher will be the limit for that class. Default -1)

sm_crb_red_demomen -1
sm_crb_red_engineers -1
sm_crb_red_heavies -1
sm_crb_red_medics -1
sm_crb_red_pyros -1
sm_crb_red_scouts -1
sm_crb_red_snipers -1
sm_crb_red_soldiers -1
sm_crb_red_spies -1
// Limits for Red bot classes in TF2. (-1 for no limit, 0 is disabled, 1 or  anything higher will be the limit for that class. Default -1) 


Important info:
Plugin limits classes when bots spawn, so if you change limits after they have been spawned then you have to wait until they die or you can slay them (for changes to take effect). REMOVE AN OLDER VERSION OF THIS PLUGIN OR OTHER PLUGINS FOR CLASS RESTRICTION BEFORE YOU INSTALL THIS PLUGIN!
Also, disable the tf2 default classlimit if enabled(the plugin disables 2 cvars itself but only once). Autobalance can also cause problems, depending on your settings.

Installation:
Autogenerates a .cfg file in cfg\sourcemod when you load it for the first time.

1. Download the plugin(or the source and compile it yourself)
2. Put the .smx file in tf\addons\sourcemod\plugins
3. Load the plugin manually/Change the map/Restart the server

Map configs:
Class_Restrictions_For_Bots.cfg is loaded first, then the map config. Using map configs is obviously optional.

1. Create folder cfg\sourcemod\Class_Restrictions_For_Bots
2. Create a <mapname>.cfg inside that folder with plugin cvars (you can also just copy Class_Restrictions_For_Bots.cfg and rename it to <mapname>.cfg). For example cp_dustbowl.cfg

Changelog:

6.11.2013 - 1.0 - Initial release
7.11.2013 - 1.1 - Fixed bots stuck without a class
- Added some checks if there are more bots than limits
- Client index 0 is invalid - error fixed
16.11.2013 - 1.15 - Removed unnecessary code
29.11.2013 - 1.16 - Fixed typo (in a check for tf2)
9.12.2013 - 1.2 - Autogenerated cfg file in tf/cfg/sourcemod folder
- cvar were renamed to sm_crb_* to be shorted
- check for max bots was modified so you can have for example 1 bot from each class(as well as limits set to 1 for each class) and plugin will not consider it as a full team, until another bot joins after that
- replaced game version check so you dont need sm 1.5.0+
- cvars tf_bot_keep_class_after_death and tf_bot_force_class will be disabled when you enable this plugin to prevent crashes( or who knows what...)
10.12.2013 - 1.21 - Removed unnecessary code
- Optimized code a bit
- Fixed check for bot force/keep class cvars
26.1.2014 - 1.22 - Removed tf_bot_keep_class_after_death cvar code (looks like not needed anymore)
- Logging errors when there are more bots than cvars allow
21.4.2016 - 1.23 - Added url to this thread
- Removed the print to all error messages
14.06.2016 - 2.00 - Reworked a big part of this plugin
- Config file is now called Class_Restrictions_For_Bots
- Added flag FCVAR_DONTRECORD for the version cvar so it doesnt appear in the config file
- Removed flag FCVAR_PLUGIN - deprecated
- Cvar tf_classlimit is now being set to 0 so it doesnt break the plugin
- Reworked the functions that check whether there is space for a bot
- Code optimizations
03.07.2016 - 2.10 - Transitional Syntax
- Removed convar change hook for tf_bot_force_class
- Changing m_lifeState when changing classes/teams
- Better code readability
- Modified version cvar flags
21.07.2016 - 2.11 - Changed handle type for convar handles to ConVar
05.04.2017 - 3.00 - Rewritten the third time
- Fixed a bug where bots could change to a class that wasnt allowed
- The plugin now properly checks the number of players playing that class
- Code optimization and performance improvements
02.11.2017 - 3.01 - Replaced the game engine check
- Plugin now disables cvar tf_bot_reevaluate_class_in_spawnroom to stop bots from killing themselves to change class
23.09.2022 - 3.03 - Fixed the compilation warning on sourcemod 1.11
- Added late load code
26.12.2022 - 3.04 - Removed redundant connection check
- Added per map config support

Credits:
DJ Tsunami for his team restricting plugin

Github:link

[SPYderman]

FINALLY. I have been waiting for this, thank you. Now I don't have to use the bot_roster entity and create custom maps.

[luki1412]

Originally Posted by SPYderman FINALLY. I have been waiting for this, thank you. Now I don't have to use the bot_roster entity and create custom maps.

So I'm not the only one, who needs such plugin.

[Custo]

Oh excellent! I've had some problems, on some maps, where only red engineer bots stayed in spawn. This will eleminate this problem. Thank you oh so much!

[SPYderman]

Originally Posted by Custo Oh excellent! I've had some problems, on some maps, where only red engineer bots stayed in spawn. This will eleminate this problem. Thank you oh so much!

Koth_harvest, right? If you downloaded a custom .nav file from where I think you did, red engineers will stay in spawn. Just got to generate your own.

[Custo]

Originally Posted by SPYderman Koth_harvest, right? If you downloaded a custom .nav file from where I think you did, red engineers will stay in spawn. Just got to generate your own.

Well, it's a nav I made because the generated one was pretty bad. And it seems every map I make a nav for (not generating), red engi bots break. It's weird.

But this plugin does help on harvest, yes.

[luki1412]

Yes engineers do not work properly on more maps. Usually because they wont leave spawn area.
There are classes that do not care about objectives, but you still need .nav for them. I have tested bots on maps like plr_hightower.

Snipers, spies, engineers and medics do not care about objectives so they are going to work on almost any map. There are some problems with them though.

Medics need a target to heal or they wont leave spawn. They only heal objective based classes and also follow them everywhere. Sometimes having a problem leaving the spawn area.

Snipers need sniping spots created in .nav file so they can camp there and snipe. They do not move much.

Spies sometimes do not do anything or they are too obvious when there is no target around. Sometimes have a problem leaving the spawn area as well. In the end, spy bots are the best working class for bots when there are no objectives. They move around the map and do not care about objectives.

Engineers usually place teleporters or their entire base right in front of the spawn area or doors. They don't know how to move buildings and their building locations need to be added in nav files (if I remember correctly). They also don't stop hitting their buildings with a wrench even though they are already fully upgraded. They only move from their built base when they need metal or there is an enemy around.

[SPYderman]

Originally Posted by luki1412 Yes engineers do not work properly on more maps. Usually because they wont leave spawn area. There are classes that do not care about objectives but you still need .nav for them. I have tested bots on maps like plr_hightower. Snipers,spies,engineers and medics do not care about objectives so they work on almost any map. There are some problems with them though. Medics need a target to heal or they wont leave spawn and they only heal objective based classes and also follow them everywhere. Sometimes have a problem leaving the spawn area. Snipers need sniping spots created in .nav file so they can camp there and snipe. They do not move much. Spies sometimes do not do anything or they are too obvious when there is no target around. Sometimes have a problem leaving the spawn area as well. In the end, spy bots are the best working class for bots when there are no objectives. They move around the map and do not care about objectives. Engineers usually place teleporters or their entire base right in front of the spawn area or doors. They dont know how to move buildings and their building locations need to be added in nav files (if I remeber correctly). They also dont stop hitting their buildings with a wrench even though its fully upgraded. They only move from their built base when they need metal or there is a enemy around.

There was an apparent update that allowed engineers to automatically generate sentry spots, however PLR is not a valid gametype they have logic for so they have no where to build them except spawn. Being myself, though, I've only found ways to make all class bots play MVM. I'm still working on getting them to play other gametypes. However in order to do this I have to re-compile it into a different map.

[luki1412]

Originally Posted by SPYderman There was an apparent update that allowed engineers to automatically generate sentry spots, however PLR is not a valid gametype they have logic for so they have no where to build them except spawn. Being myself, though, I've only found ways to make all class bots play MVM. I'm still working on getting them to play other gametypes. However in order to do this I have to re-compile it into a different map.

I thought that Valve is going to make some more plr maps and add bot support because pl maps have bot support.

[SPYderman]

Originally Posted by luki1412 I thought that Valve is going to make some more plr maps and add bot support because pl maps have bot support.

Then again, since when has VALVe ever made a 'major' update for their bots other than MVM.