jagrosh / jagrosh/Vortex

In kick, ban and tempmute logs the old name system is still in use

Open
#165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
600
Forks
338
PR merge metrics
No merged PRs in 30d

Description

In some log actions, e.g.:
- kick
- ban
- tempmute
- (possibly more)

... the old naming system of discord is still in use.

Example - first and third message is a kick and tempmute log, which still uses the old naming system (`ExampleUser#1234`). The second log message is a edit of a message, which uses already the current naming system (`ExampleUser`).
![Screenshot_20240325_150346_Discord](https://github.com/jagrosh/Vortex/assets/96007573/68e58736-3688-4299-a70a-5b6527d7c60f)
![Screenshot_20240325_150423_Discord](https://github.com/jagrosh/Vortex/assets/96007573/970c6412-eecb-49fa-9012-b427585dfc2a)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the log generation for kick, ban, and tempmute actions, then compare their name formatting with the message-edit log shown in the issue. The work is done when these affected moderation logs use the current Discord naming system without the discriminator suffix, and any additional affected log actions are covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.