Title should be self explanatory, if it's not. Here is a gist:

Basically, if you ban, you'll get 2 case logs instead of one, we should filter the logs if the banned user is that user and is from the moderator

Is your feature request related to a problem? Please describe.
Commands should be the easiest part of the coding process, but due to the settings and translation API, the code is badly formatted and unreadable.

It's even worse than that, not having any formal way to code commands makes the code harder to test, which makes us only test manually. This may be good if the API is consistent, but as we can see from recent events, that it's not the case and caused many bugs.

Describe the solution you'd like
The solution consists of several steps:

• Test API - for testing commands and events, making it easier by abstracting the environment and making it easy to simulate events and users.
• Command API - for uniting all commands around one tested API. Making it much harder to have bugs in the command.

This solution will need some kind of draft, to not make them another inconsistent APIs like the Translation API.

Describe alternatives you've considered
Another alternative solution is to make commands simpler to understand, without an API, but that will lose the uniformity of the testability of each command.

What is a "guild policy?" - A guild policy is a way to include a subset of rules Nino can act on when a certain event has been emitted.

How would it work?

Guild policies will be placed in the guild_policies database table as the following structure:

{
  "guild_id": "...",
  "events": ["GUILD_MEMBER_ADD"],
  "do": {
     "type": "message_send",
     "data": {
         "channel_id": "...",
         "content": "..."
      }
  }
}

Use this as another shortlink database to generate from.

Also, add a GitHub action to refresh the shortlinks.json module whenever the database is updated (cron job probably in ~15 minutes / ~1 hour?)

• Add the database to scripts/shortlinks.js
• Add a GitHub action under .actions/ to periodically update the db if it has changed or not

Is your feature request related to a problem? Please describe.
Sometimes in servers, people like to customise the bot to suit the prefix that is easiest to them.

Describe the solution you'd like
A custom command system that uses a command to change prefix, e.g nino <prefix>

@dondish, remove TSLint and upgrade to ESLint when TSLint gets deprecated in early 2020

Is your feature request related to a problem? Please describe.

It is hard to know what things can be configured inside of Nino, because currently the help wiki page does not document everything

Describe the solution you'd like

Detailed docs for each value that can be set in x!settings

Workarounds

running x!settings set help shows you all configurable settings in the form of an error message, however, does not describe what they do

Other notes

• Would be happy to have a shot @ it on the wiki for now
• More issues coming soon before I try to address them in PR's

Describe the bug
When you use the mute command the bot logs again for a role add.

To Reproduce
Steps to reproduce the behavior:

1. Set a mod-log channel
2. Mute someone by adding the role.
3. Unmute and mute someone using a command
4. Look in mod-log

Expected behavior
It should not log twice.

Great Google technology

https://perspectiveapi.com/

Some messages use punctuation and others don't.
In general, I am against exclamation marks and heavy punctuation in short responses, as they make the message kind of shouty and agressive.

For example:

I ban a user using Discord. The bot should listen for this and create a case in the mod-log, then allowing the moderator to set a reason.

This could apply to mute/unmute, ban and kick.

Describe the bug
Don't delete messages by one

This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• Update dependency dev.kord:kord-core to v0.8.0-M14
• Update dependency io.sentry:sentry-logback to v5.7.4
• Update dependency org.jetbrains.kotlinx:kotlinx-coroutines-bom to v1.6.3
• Update dependency com.charleskorn.kaml:kaml to v0.46.0
• Update dependency com.squareup.okhttp3:okhttp to v4.10.0
• Update dependency io.prometheus:simpleclient to v0.16.0
• Update dependency io.prometheus:simpleclient_common to v0.16.0
• Update dependency io.prometheus:simpleclient_hotspot to v0.16.0
• Update dependency net.logstash.logback:logstash-logback-encoder to v7.2
• Update dependency org.jetbrains.kotlinx:atomicfu-gradle-plugin to v0.18.0
• Update dependency io.sentry:sentry to v6
• Update dependency io.sentry:sentry-kotlin-extensions to v6
• Update dependency io.sentry:sentry-logback to v6

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency com.auth0:java-jwt to v3.19.2
• Update dependency io.ktor:ktor-bom to v2.0.2
• Update dependency io.sentry:sentry to v5.7.4
• Update dependency io.sentry:sentry-kotlin-extensions to v5.7.4
• Update dependency org.jetbrains.kotlinx:kotlinx-datetime to v0.3.3
• Update dependency org.jetbrains.kotlinx:kotlinx-serialization-bom to v1.3.3
• Update dependency com.diffplug.spotless:spotless-plugin-gradle to v6.7.2
• Update dependency io.insert-koin:koin-core to v3.2.0
• Update dependency io.kotest:kotest-bom to v5.3.1
• Update dependency org.postgresql:postgresql to v42.4.0
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Title is self explaintory

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

For example:

• Check if it's banned on ksoft.si
• Check the account age
• Check if the account has a profile picture
• Check if multiple people are joining with the same profile picture?

Describe the bug
When doing lockdown it doesn't select the right channels

To Reproduce
Steps to reproduce the behavior:

1. Lockdown a specific channel.
2. Watch as another channel gets locked

Expected behavior
Lockdown should only lock down the specified channels

Screenshots

yes

Describe the bug
Hierarchy is misspelled everywhere as heirarchy.

To Reproduce
Steps to reproduce the behavior:

1. Run any moderation command on someone above your role

Expected behavior
Hierarchy should be spelled correctly

Shortened URLs are super dodgy.

Once implemented, I can provide a list of URLs to block if you need me to.

Is your feature request related to a problem? Please describe.

You can have up to 15 punishments (in total)!

From the docs (https://github.com/NinoDiscord/Nino/wiki/Managing-Guild-Settings)

Describe the solution you'd like

U N L I M I T E D T I E R S

Additional context

I see no technical reason for this arbitrary limit

I cant seem to find the config.yml file does anyone know where it is?

Describe the bug
Spams the "mod log" channel with a bunch of cases because of calculating bigints over numbers

To Reproduce
Steps to reproduce the behavior:

1. Mute a user for over a week
2. Wait that duration
3. Nino spams mod-log

Expected behavior
It shouldn't spam the mod-log channel

Screenshots
View above

Discord (please complete the following information):
Not applicable in this situation

Additional context
None at the moment

im currently using redis with password since my servers redis is serving multi purpose bots/websites so having non password is out of option.

application.yml does not support redis password and suggest it does

Introduce a new concept from discord/discord-api-docs#1396 that is called the Everyone Mention Automod, which essentially checks for @everyone/@here/user or role mentions and proceeds automod actions for the user.

If you send a message and then edit your message with an invite, you can bypass the automod. As seen here https://quak.ovh/2bf3Dz5.gif

Proposal

Use wumpfetch v0.3.0's profile feature

Assigned to auguwu (dont do this dondish, i can do it u fake weaboo)

Describe the bug
Some commands echo the content raw, allows mentioning commands.

To Reproduce
Steps to reproduce the behavior:

1. Start the bot
2. use x!help @ROLE
3. Role is pinged

Expected behavior
The response should be sanitized.

Roadmap

• Add slash command variants
• Refractor database models
• Implement MikaBot/cluster-operator
• #789
• #704
• Add message highlighting when discord.com/channels/.../messages/... appears
• Rework argument system to be very safe for development and the end user Ended up being too complex, maybe later.
• #275
• Add thread commands into moderation (i.e, no-threads and threads)
• Add tags into Nino with some new features.
  • Scriping Language for complex tags
  • Minimal API for less complex tags
  • Tag Recovery and Export/Import
• Implement ravy API for banning unwanted users in the guild (if wanted)
• #831

Is your feature request related to a problem? Please describe.
By request, people always have said the settings command is very difficult to use, which we understand since it was coded when the bot was first fully introduced in mid-2019.

Describe the solution you'd like
I feel like we need other people's solutions so we can make it easier to make it more user friendly. So, if you have any suggestions, leave them here.

To make it easier to come from other bots. This is a list of aliases I have thought of

• prune: purge
• ban --soft: softban
• warn: point
• warnings: points, checkpoints checkwarnings

Fixes many translation issues and adds the ability to remove channels from being ignored (Logging) and swears (Swearing Automod)

See the title. It'd be useful for when people change their avatar to NSFW and we can ban them for it.

see title

When i try to run it it says this:

Is your feature request related to a problem? Please describe.

For newcomers, it may be hard to understand how to work your bot. Slash commands provide easy descriptions, easy marking of the expected field type, and optional parameters. Plus, selecting TAB to enter an argument is much faster than --, as well as argument completion being a huge speedup as well

Describe the solution you'd like

Commands to be mirrored using the / command api

Describe alternatives you've considered

A second bot to take /commands and then pipe it to Nino

Additional context

Slash commands are beta, and subject to change, but I believe the tradeoff is worth it for the ease of use