-
Notifications
You must be signed in to change notification settings - Fork 44
Open
0 / 60 of 6 issues completedLabels
improvementIdeas for streamlining existing featuresIdeas for streamlining existing features
Milestone
Description
Version 2.0 may not be coming out for a while, but we can use this issue to track database updates and other breaking changes that may need to wait until then.
- Make our own schema management table; keep using
libertybans_revisionif possible - Use a single active punishments table, rather than an active table per type, removing the unique type/victim constraint for active punishments (Restructure data: Remove the restriction on unique active punishment per type/victim #316)
- Add ghost mute and potentially custom punishment types ([Feature Request]: Add a ghost mute #238, Change database and API to allow unlimited custom punishment types #308)
- Add notes on existing punishments and/or users, which are not the same as a standalone punishment type ([Feature Request]: Annotate/Note feature #266)
- May need to store player language in the database, in case it's not available during login ([Feature Request]: Multi-language support #312)
- Create a notifications table to handle warning messages ([Feature Request]: Warning notifications for offline players #303) and ban notices for players who never logged in ([Feature Request]: Send ban notice to player on first join after their ban expires. #232)
- Store scope configuration in the database, and allow multiple scopes per punishment type (Adding scope-related dynamism for the punishment interface #326)
Sub-issues
Metadata
Metadata
Assignees
Labels
improvementIdeas for streamlining existing featuresIdeas for streamlining existing features