What does this suggestion change/add/remove:
This suggestion adds a scrollbar to the Internal Affairs Arrest NPC. When you open up the menu of this NPC, you are greeted with an arrest and release button aswell as a list of previously arrested individuals. One major drawback of this list is that as of current writing it will only show the 12 most recent arrests. No more. This change aims to solve this issue by adding a scrollbar vgui element to the current interface and parrent the arrestee element onto this scrollbar element.
Has something similar been suggested before? If so, why is your suggestion different?:
No.
Possible Positives of the suggestion (At least 2):
Possible Negatives of the suggestion:
Based on the Positives & Negatives, why should this suggestion be accepted:
Although the above negative seems like an issue. It can be solved through a plethora of means such as a server-side JSON file tracking arrests or using mysql or sqlite depending on the current database architecture. It is important to note that culling this list of arrests will be needed as a large database/JSON file has the potential of becoming corrupt. This culling could happen right before or after a server restart as I see no need for these arrest logs to be kept longer than a day, longer ofcourse, if it is possible. This solution would also mostly solve the clientside performance issues raised.
This suggestion adds a scrollbar to the Internal Affairs Arrest NPC. When you open up the menu of this NPC, you are greeted with an arrest and release button aswell as a list of previously arrested individuals. One major drawback of this list is that as of current writing it will only show the 12 most recent arrests. No more. This change aims to solve this issue by adding a scrollbar vgui element to the current interface and parrent the arrestee element onto this scrollbar element.
Has something similar been suggested before? If so, why is your suggestion different?:
No.
Possible Positives of the suggestion (At least 2):
- Easier time tracking arrests within departments allowing for these individuals to be prosecuted either internally or externally based on their previous arrests.
- Prevents misunderstandings when it comes to the question of whether or not somebody has been arrested before.
Possible Negatives of the suggestion:
- It is likely the current system does not track more than 12 arrests as there is no reason to in the current scope.
- Clientside Performance issues could be a thing when opening the menu, if there is a large amount of arrests being tracked.
Based on the Positives & Negatives, why should this suggestion be accepted:
Although the above negative seems like an issue. It can be solved through a plethora of means such as a server-side JSON file tracking arrests or using mysql or sqlite depending on the current database architecture. It is important to note that culling this list of arrests will be needed as a large database/JSON file has the potential of becoming corrupt. This culling could happen right before or after a server restart as I see no need for these arrest logs to be kept longer than a day, longer ofcourse, if it is possible. This solution would also mostly solve the clientside performance issues raised.