[Ilusion9]

Description: Disable specified bombsites if there are fewer CTs than their accepted limit.

Commands:

sm_bombsites - will show up a menu where you can set a limit of CTs to all bombsites.

GitHub: https://github.com/Ilusion9/bombsite-limiter-sm

[ThatOneGuy]

Looks good.

Consider using EntIndexToEntRef for storing the entities, then EntRefToEntIndex to switch back. I'm not sure if this applies to bombsite ents, but ents can change from round to round, so using ent refs will address that possibility.

Consider changing the key-value key "site" to be "enabledsite". It is otherwise unclear (until I read the code) if the server manager is supposed to put the sites they want to keep or disable.

Side note for possible future expansion

Currently, if a setup is found, this plugin disables all sites except the one noted (until the CT limit is exceeded, that is). What about maps with more than two bomb sites? You could expand the functionality of the plugin to allow for multiple sites to be enabled (e.g. "sites" "ab"), or even better, you could loop all setups each map start and check all cfgs that match the map name, then you could have, e.g., "A" always open (set # CT's = 0), "B" open after X CTs, and "C" never open (perhaps it was a problematic site?). Just a thought for supporting larger maps by having multiple tiers of [#CTs vs sites open] and allowing server operators to disable problematic bomb sites when there are more than 2.

[Ilusion9]

The bombsites are loaded when the map starts, and they remain after round ends.

I've changed the plugin. Now, in the configuration file, you must name the bombsite that will be disabled and the limit to disable it.

Example:

PHP Code:

    "de_dust2_unlimited_go"
    {
        "B"        "5"
        "C"        "10"
    } 


[ThatOneGuy]

Originally Posted by Ilusion9 The bombsites are loaded when the map starts, and they remain after round ends.[/PHP]

I wondered if static map stuff like that keeps the same index. Glad you know.

Originally Posted by Ilusion9 I've changed the plugin. Now, in the configuration file, you must name the bombsite that will be disabled and the limit to disable it. Example: PHP Code:     "de_dust2_unlimited_go"     {         "B"        "5"         "C"        "10"     }

Pretty slick.

[laibach]

hello
this plugin only works on standard maps do not work on de_dust2_winter maps

[Ilusion9]

Originally Posted by laibach hello this plugin only works on standard maps do not work on de_dust2_winter maps

Add a configuration in configs/bombsites.cfg

[laibach]

Originally Posted by Ilusion9 Add a configuration in configs/bombsites.cfg

me bombsites.cfg
"BombSites"
{
/** Site disabled - CT limit
* If there are fewer CT's than the specified limit, then the specified site will be disabled.
* Example (for de_dust2): if there are fewer CT's than 5, bombsite B will be disabled.
*/

"de_dust2"
{
"B" "5"
}

"de_dust2_winter"
{
"B" "5"
}

"de_dust2_night"
{
"B" "5"

}
}

Although he writes that the bombsite is block, but the bomb can be put

[Ilusion9]

Yeah, cause the author created Site B before Site A. I tested the map, and site A will be locked if I set site B to be locked.

In de_dust2_winter, site B has 428 entity index and site A 431 which is wrong.

From valvesoftware wiki page:

The bombsites are assigned as A and B in the order the func_bomb_target entities were created.

https://developer.valvesoftware.com/...mb_Defusal_Map

All maps should respect the standards in order to work correctly.

[Ilusion9]

Code improved. Now the plugin will detect which site is A and which site is B.
If you lock bombsite C, all bombsites after C (site D, site E etc.) will be locked.

[aykocity]

Is it possible to change in certain rounds?

example;

1.round - A
3.round - B
5.round - A

etc..