You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For easier use, a less time-consuming solution for punishing should be established. This consists of a list of templates that define the duration and reason that caused this punishment. Such templates will be identified by either numbers or a string identifier or both. Reason are going to be stored (in db/i18n files?) internationalized. For simpler usability, reasons will be formatted as MiniMessage components.
Additionally, templates can be assigned in a specific order to stages. With each new punishment in the same template, the stage of the actual punishment will get increased and thus its severity. This requires #8 to work and store template ids per punishment. If there is the need to reset/decrease the stage (for e.g. wrongful punishment), this is denoted in the punishment history.
The text was updated successfully, but these errors were encountered:
For easier use, a less time-consuming solution for punishing should be established. This consists of a list of templates that define the duration and reason that caused this punishment. Such templates will be identified by either numbers or a string identifier or both. Reason are going to be stored (in db/i18n files?) internationalized. For simpler usability, reasons will be formatted as MiniMessage components.
Additionally, templates can be assigned in a specific order to stages. With each new punishment in the same template, the stage of the actual punishment will get increased and thus its severity. This requires #8 to work and store template ids per punishment. If there is the need to reset/decrease the stage (for e.g. wrongful punishment), this is denoted in the punishment history.
The text was updated successfully, but these errors were encountered: