Using .cfg files to change bot setup Options

[DNA.styx]

Anyone try to do this on a dedicated server?

I would like to have the option to kick all bots, return the bots, make all bots snipers etc without having to restart the server, or even the map.

Default setup
my config.ini file includes

CODE

rcbot_addbottime 5
rcbot_bot_quota_interval 5
rcbotd config min_bots -1
rcbotd config max_bots 10

All the bot profiles have team = -1 but have their class set.

I've got a plugin that restarts the map when all real players leave in the hope that it will reset everything back to default when the next player joins - as I'm planning to have these .cfg files available to be voted for my non-admins.

I've created a vote_rcbot_kick_all.cfg that contains

CODE

rcbotd config min_bots -1
rcbotd config max_bots -1
rcbot_bot_quota_interval 0
sm_kick @bots

and a vote_rcbot_return_all.cfg that contains

CODE

rcbotd config min_bots -1
rcbotd config max_bots 10
rcbot_bot_quota_interval 5
sm_kick @bots

All the above seems to work well. So far so good.

The next option I wanted to create was a sniper only server. I was hoping a .cfg file like the below would work.

CODE

sm_kick @bots
rcbotd addbot 3 2
rcbotd addbot 3 3
rcbotd addbot 3 2
rcbotd addbot 3 3
rcbotd addbot 3 2
rcbotd addbot 3 3
rcbotd addbot 3 2
rcbotd addbot 3 3
rcbotd addbot 3 2
rcbotd addbot 3 3

But some non-sniper bots mange to sneak in before the rcbotd addbot command(s) do
Here's the console log when I run the above .cfg
https://pastebin.com/CRwqKHxP

I also note that restarting the map doesn't return the bots to thier 'default' profiles.

Anyone tried this before? Any obvious bugs in my setup/logic?

[DNA.styx]

Thanks for the info INsane. Has given me loads to work through and get my head around. Leave it with me.

This is the admin menu/vote plugin (1) I'm testing. Appears to work well. (image below)



(1) https://forums.alliedmods.net/showthread.php?p=2097623

[INsane_dod]

Thanks for the info INsane. Has given me loads to work through and get my head around. Leave it with me.

Here is another angle on class - RCBot2 - fun modes. Just in case you wanted another headache

Another way to control RCBot2 class "on the fly" or per map is to change weapons, not the class.
The RCBot2 class issues workarounds I explored had 2 noticeable actions, bots don't mind being kicked and bots don't mind having weapons stripped at spawn.

So we alter weapons of each class...not the class itself.

Two weapon plugin's work fine on dod:s.

1. [DoD:S] Gun Menu https://forums.alliedmods.net/showthread.php?p=1781776

That one is fine and fun but shouldn't be used with the next one. It has some small issues with RCBot2 but works fine.

2. DoDs Equipment (various versions) ... https://forums.alliedmods.net/showthread.php?p=654354

Now that is version 0.0.6 in the link, version 0.0.7 is in a further link, both had issues.
I reworked a couple of items and made a version 0.8 for testing. It just needed a small compatibility edit.

It's here as a download...
https://www.dodbits.com/dods/index.php/down...quipment-plugin

It was part of my download for a dedicated server on a home LAN. I see no reason why it wouldn't work in a online server.

This is explained here....
https://www.dodbits.com/dods/index.php/dods...ot2#dodeqipment

So, again integrating this on a RCBot2 server, the dod equipment plugin can deliver a standard set up (at server start) that all players can get the old "dod 1.3" weapons load out, like the various dod pistols plugin but... you have near total control of weapons and ammo in every class.

You can also "change on the fly", make every class a sniper load out.
Then you can also call the file in a map config file.

So... it is a bit of a Swiss army knife when you look at what it can control.

Its more work (my examples reduce that workload) in config files but unlike the [DoD:S] Gun Menu this can do a lot more.

The main work is making the config's and getting them working without conflicts.

I know [DoD:S] Gun Menu is very popular but DoDs Equipment if set up opens up a whole range of possible fun modes for a mixed RCBot2 and Human fun server.