The bot that runs the department

Do it anywhere, see it everywhere

The site and the bot share one database, so neither has to tell the other anything. Something done on the website shows up in Discord. Something done in Discord shows up on the website. There is no delay and no syncing step, because there is nothing to sync between.

1. You fill in the formHost, date, everyone who came, marks and comments.
2. It is saved hereBefore anything is sent anywhere else.
3. Posted to the forumWritten out as BBCode and posted for you.
4. Logged in DiscordOne entry with a link straight to the post.
5. Counted on profilesEveryone listed has it added to their record.

1. You run the commandAnd give your CIT account name.
2. The link is savedYour Discord account is tied to your member record.
3. Your profile updatesThe site now knows the two are the same person.
4. Your face appearsYour Discord picture shows on the roster and profile.

It works the same way for the rest of it.

Using it without leaving the game

Game chat is mirrored into Discord already. The bot reads that mirror, and when a line turns out to be a command it runs it and sends the answer back the same way. You never alt tab.

1. You type in game!backup, or !play, or anything else.
2. The line is mirroredGame chat appears in Discord as it is typed.
3. The bot spots a commandIt reads your name and what you asked for.
4. It runs as normalThe same code that runs it in Discord.
5. You get the answerBack in game chat, in plain text.

Music is the one that needed thinking about. An in game name does not tell the bot which Discord account you are, so it cannot look at which voice channel you are in. Instead it stays in the channel it is already in, and if it is not in one it joins the busiest channel with people in it.

The log lines moderators paste

Every group action taken in game gets announced in chat: promotions, demotions, kicks, warnings, rewards, joins and leaves. All of it then has to be written onto the forum log by hand, worded the right way, with the right date.

The bot does that writing. It reads each announcement, tidies the names by stripping rank prefixes, group tags and unit numbers, and posts it to the moderator channel as a clean entry with the mod role pinged.

1. Something happens in gameSomeone is promoted, warned, kicked or rewarded.
2. It is announced in chatAs a plain line of text, names and tags and all.
3. The bot reads itPulls out who, what, why, and by whom.
4. Moderators get itA tidy entry, with the forum line already written out.

The last part is the useful part. Every one of those entries ends with a ready made line for the forum log, already worded and already dated. It gets copied across as it is.

Nobody pastes BBCode any more

Training reports, patrol reports, vacations, promotions, tests, badges and unit numbers all end up as a post on the CIT forum. You fill in a form and the bot writes the post.

1. Your form is savedFirst, before anything is sent out. It cannot be lost after this point.
2. The post is writtenNames become links to profiles here, the report number links back to the full report.
3. It goes to the forumPosted under the department account, in the right topic.
4. You get the linkStraight to your post, not to page forty of a thread.

If the forum is down, you are told so plainly and given a Retry button, and only then does the BBCode appear so you can paste it yourself. When it worked there is nothing to copy, so you just get the link.

Recruitment

Joining works the same whether you start on the website or in Discord. It used to be a second bot with its own database, which meant two records of the same application that slowly stopped agreeing. Now there is one.

1. Three short formsOne at a time, so there is no wall of questions to lose.
2. It reaches the channelWith Approve and Deny for the members who hold forum rights.
3. A decision with a reasonWhich is stored, and sent to you.
4. Nothing is overwrittenThe record keeps every step it went through, not just the ending.

What it does without being asked