Clan Ops

What the client wanted

Clan Ops is the bot I kept ending up rebuilding from scratch for every clan or community I worked with. Roster tracking, rank promotions, operation scheduling with RSVPs, and a clean recruitment pipeline — every clan needs the same primitives, and most stitch them together out of three or four mismatched bots.

Goal: one bot that handles the core operations side of a clan or unit-style Discord, without the bloated feature creep that turns most 'community bots' into a UI nightmare.

What got built

Roster & ranks: members are tracked as rows with rank, join date, and attendance. Officers can promote, demote, or mark inactive via slash commands; the audit trail is logged to a private channel so nothing gets lost.

Op scheduling: officers post an operation with date, time, role slots, and notes. Members RSVP with reactions or a slash command; the bot pings the day-of and tracks who actually showed up vs. who flaked.

Recruitment: applicants run a /apply flow that posts a structured embed into a recruitment channel. Officers vote, add notes, and the bot moves accepted applicants into the right roles and channels automatically.

What happened next

Soft-launched with a handful of clans I personally know. Iteration is fast — I ship updates the same week a real officer surfaces a real complaint.

Built specifically against the workflows of unit-style and milsim-adjacent clans, but the primitives transfer cleanly to any community that runs scheduled activities.

Public release is gated on feedback from the soft-launch cohort. If you run a clan and want early access, drop into the Discord.