Manage your DCS World servers via Discord with lots of extensions and possibilities
To use the new player number alarms, configure your mission.yaml like so:
DEFAULT:
# ...
usage_alarm:
min_threshold: 30 # send a message, if less than 30 people fly on your server
max_threshold: 10 # send a message, if more than 10 people fly on your server
role: DCS Admin # the role that should be pinged
channel: 1122334455 # the channel to send the ping in (default: admin channel)
:warning: Attention! You need to decide for EITHER min_threshold OR max_threshold. You can NOT use both together. There will be only ONE alarm per mission for now, until someone tells me how you guys want it to be different.
This release has some nice additions for you SRS and LotAtc users:
run.cmd -s to reveal them./node shell added/node shell added/mission rollback did not write serverSettings.lua correctly/dcs install and /dcs uninstall always asked if servers should be shut down, even if none were up/node add_instance did not work reliably on servers without any instanceDEFAULT:
message_no_srs: You need to enable SRS to use any slot on this server!
enforce_srs: true # block slots until SRS is activated
move_to_spec: true # move people back to spectators, if they leave SRS (only if enforce is true)
:warning: The move to spec might move people to spectator that only lost connection. Handle it with care.
You have new commands:
/srs list => show active people on SRS with their radios
/gci list => show active GCIs on LotAtc
/gci info => shows information about a specific GCI
The GCI commands are available in the in-game chat also.
MyFancyServer:
force_voice: true # people will be forced in this voice channel, if they are active in any other voice channel. The server access will be blocked until they move themselves in any voice channel!
channels:
status: 112233
chat: 334455
admin: 556677
voice: 998877 # I am new!
/link, /unlink and /linkme handling/scheduler maintenance + /scheduler clear smart auto-completion added/linkme
/unlink
/info verify and unlink did not affect squadronsYou need to have the LotAtc extension activated for your server and then add "lotatc" to your opt_plugins like so:
opt_plugins:
- lotatc
You can define the new autoroles in your bot.yaml or servers.yaml. I changed the structure a bit, the bot will migrate you over if you had used autorole in the past, but you still might want to look into it, as the new options are much more flexible: a) bot.yaml
autorole: # Automatically give roles to people, depending on conditions (see below). The roles need to be set up in your Discord server.
on_join: Member # Give anyone the "Member" role, if they join your Discord.
linked: DCS # Give people that get linked the DCS role.
online: Online # Give people that are online on any of your servers the "Online" role.
b) servers.yaml
My Fancy Server: # Your server name
autorole: Fancy Players # Optional: give people this role, if they are online on this server (overwrites autorole[online] in bot.yaml!).
For "online", you can use either the bot.yaml variant or the servers.yaml variant, or even both, where the servers.yaml entry will overwrite the bot.yamls one for this specific server (so in the above example, an online player would get the role "Online" on any of your servers but "My Fancy Server", where they would get the "Fancy Players" role.
I hope you enjoy the new version!
/squadron add, /squadron edit, /squadron list added/squadron join can be disabled now (see documentation)/squadron create will auto-add people that have the respective squadron role to the squadron/node online, /node offline
You get the audit messages back on DCS updates with this version. Sorry for that mishap. And you might try out the new /help command that gives you mentionable links to all commands. Same for any command that prints something like "Please run /aaa bbb"
If you want to disable the /squadron join command, you can do that by adding these lines to your userstats.yaml:
DEFAULT:
squadrons:
self_join: false # enable self-join for squadrons (default: true, otherwise you need to get the associated role)
This does only make sense, if you have a role associated with the respective squadron. People will then join / leave a squadron automatically, when they get the role (or the role is being removed).
A "squadron" can be created with a short description and a possible auto-role with /squadron create. People that are linked can then join the squadron with /squadron join. If you have set an auto-role, they will get it on join and it will be revoked on leave. There are no locking mechanisms atm, so people can join any squadron they want.
You can then use squadron:<name> as a period filter option in your /highscore or /serverstats displays. Atm you can not stack periods, meaning, you can only get the total highscore for a squadron, but not the daily or weekly one. That might need some additional tweaking if needed.
Happy Easter, dear DCSServerBotUsers, or whatever you might celebrate these days!
A new version 3.0.3.4 has just dropped, bringing you besides some smaller add-ons and some bug fixes a long awaited feature "timeleft", which displays the remaining time until the next mission restart in the server status embed, a new command /server timeleft and a new in-game command -timeleft.
/server timeleft and in-game -timeleft added/prune can now prune (old) server data from the database also-restart did not check the time value/info raised error with unlinked Discord accounts/help could not print "mission" plugin, as there were too many commands in/dcs update I hope you enjoy this little update and the bot in general!
/player exempt added to put players on the AFK-exemption list/dcs update can now get a branch to update to the release version of DCS./info, /find moved from userstats to mission/player info alias added for /info
/player find alias added for /find
/mission info display so that the embed does not use that many elements./dcs ban: ucids were not checked before ban/node statistics to show the pool usages on your nodes.Small bugfix update. I made some small mistakes in the last version, which for instance did not bring up your greenieboards properly anymore. And as I was working on the next version already, you get some of the new stuff also.
For Multi-Node changes and CreditSystem enhancements, please see below.
/dcs unwatch now has auto-completion/info, /credits list and /penalty show relative discord timestamps now/node upgrade
/server config can change the server port now also/server config works on non-initialized servers/server config (interaction already responded)/link
/node add_instance [template] should have been optional/doc generated double // on slash commands/doc did not generate the correct lists for the DCS role/modulestats did not work with new campaign filter/serverstats weird graphics due to missing ORDER BYThe bot now has a detection if the same nodes runs on the same machine. Unfortunately, if you run multiple bots for multiple communities on one machine, it does not take that into consideration.
The easiest one is to create different node names (which would be preferable anyway).
I for instance run 3 nodes on my server:
run -n MERC
run -n JDS_DE01
run -n CB
You only need to change the node names in your nodes.yaml and scheduler.yaml (or in any config you have them, should only be those two) and you only need to do that in the above mentioned case.
To give a bit more insight what you can do now with the CreditSystem, you can reward people now for proper landings. It works in combination with the former "use_reservation", which was renamed to "payback" with this release, as it is more self-explaining, what it does (I hope so at least). The system is as follows:
a) Payback If you enable payback (payback: true) in your slotblocking.yaml, you can give people their money back that they paid for a plane. The money will be taken on takeoff and will be refunded on landing. This is more or less how it worked before but it is taken on takeoff and not on birth now. Keep that in mind, if you have airstarts!
b) Multiplier With the new system, you can create a multiplier in your creditsystem.yaml. The default is 0 => no multiplier. The multiplier determines, how many points someone will get in addition on a proper landing. So with a multiplier of 1, people get the same amount of points (aka credits) awarded that they got already during that sortie, if only they bring back their plane. 2 means double award, means 3x the points on one sortie.
Enjoy the new system and credits to Enigma for the idea!