Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework Warn System #1373

Merged
merged 2 commits into from
Nov 7, 2024
Merged

Rework Warn System #1373

merged 2 commits into from
Nov 7, 2024

Conversation

FrozenChen
Copy link
Member

  • Now there is 2 types of warns, ephemeral and pinned
    • ephemeral warns are the default type of warn and expire after 180 days
    • pinned warns are applied with the .pinwarn command (works the same as .warn), pinned warns do not expire and are only deleted by staff.
    • Expired or deleted warns are still kept in the DB and can be seen with the modsense slash command.
  • All old warns will be converted to ephemeral warns meaning a lot of warns will be deleted once its implemented.
    • It's straight up impossible to check warns one by one to see which one should be a pinned warn, currently the DB has 6143 warns logged
  • Added new slash command, multiwarn which can apply multiple warns at once, works the same as softwarn but you can also select if you want all the warns to be ephemeral or pinned (meaning you dont need to spam softwarn or pinwarn)

@FrozenChen FrozenChen merged commit 0dbbf1a into main Nov 7, 2024
1 check passed
@FrozenChen FrozenChen deleted the rework_warns branch November 7, 2024 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant