yuki

Nursy

Nursy started as a moderation and fun bot and became a moderation-only bot, with no joke commands. It has ban, kick, timeout, warnings that turn into a timeout every three, message cleanup, slowmode, channel lockdown and n!purify, which recreates a channel from scratch. Every punishment goes to the log channel and the person gets a DM. Automod blocks invites to other servers, spam, too much CAPS and banned words, and everything is tuned with n!config. The bot replies in English.

Area
Server-side
Stack
Node.js · discord.js v14 · JavaScript (ES Modules) · dotenv · Git
Year
2026
Status
archived

Support tickets

  • n!config ticket wipes the chosen channel, leaves only the open-a-ticket box and locks the channel so only the support team can write there.
  • Whoever clicks open ticket fills in a form with their name and reason, and the bot creates a private channel only they and the staff can see.
  • Each person can only have one open ticket at a time.
  • On close, the channel is deleted and the whole conversation goes to the log channel as a text file.

Under the hood

  • Commands are written with SlashCommandBuilder but used through a prefix. The builder only describes the name, options and permissions; a layer I wrote reads the message, converts mentions, IDs, numbers, channels and roles, and shows how to use the command when something is wrong. If I ever switch to real slash commands, the commands stay the same.
  • Before punishing anyone, the bot checks the role hierarchy between the moderator, the target and itself, requires the right permission and asks for confirmation on destructive things like n!purify.
  • Commands and events load straight from their folders. A new command is just a new file.
  • Each server's config, warnings and tickets live in a JSON file, saved with atomic writes so it doesn't get corrupted if the process dies halfway.
  • The token lives in .env, which git ignores. Only an empty .env.example goes in the repo.