Skip to content

[Bug]: Warn Reason Too Long > Causes Issues #61

@Joshua8600

Description

@Joshua8600

Checked Existing

  • I have checked the repository for duplicate issues.

What happened?

When a warn reason is too long, strange things happen.

  1. Bandwidth says unable to process or something (I can't remember the exact wording and I do not have an alt to test on) with also saying "255" in it, presumably a character limit
  2. However, the warn still gets logg, still untrusts, and sends a DM to the user
  3. But the warn itself is not shown in /manage-warn view, meaning it did not fully process

What did you expect to happen?

Either:

  1. To process like normal
  2. To not do any of the above, including the DM and untrusting

Steps to reproduce?

  1. Warn a user with a very long warn reason.

Other relevant information. (OPTIONAL)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    approvedThe topic is approved by a developerbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions