As a result of our implementation of a custom point system that is able to be leveraged by group leaders, we are now able to fairly accurately determine whether a drop was received solo, or by a group of members of the same group.
This means that we can theoretically allow groups to enable split tracking logic, and then award GP value to all associated members of the drop (an equal amount for each player to the value if the item was split x ways), which would prevent a group of users from receiving an extremely valuable drop, and only one player receiving any credit on the leaderboard.
This would require a fair bit of internal work, as we currently store drops solely based on the player who received them. A new split table with relevant foreign keys to the drop table would likely be the most clean way to implement the storage mechanism; however the redis logic would also need to be investigated so that it continues to work normally for groups who do not enable split tracking logic.
Additionally, we must ensure that any and all changes made are properly aligned with iur existing logic for group leaders to modify drop submissions on discord using context menus; so that changes made to splits there are reflected properly globally.
As a result of our implementation of a custom point system that is able to be leveraged by group leaders, we are now able to fairly accurately determine whether a drop was received solo, or by a group of members of the same group.
This means that we can theoretically allow groups to enable split tracking logic, and then award GP value to all associated members of the drop (an equal amount for each player to the value if the item was split
xways), which would prevent a group of users from receiving an extremely valuable drop, and only one player receiving any credit on the leaderboard.This would require a fair bit of internal work, as we currently store drops solely based on the player who received them. A new split table with relevant foreign keys to the drop table would likely be the most clean way to implement the storage mechanism; however the redis logic would also need to be investigated so that it continues to work normally for groups who do not enable split tracking logic.
Additionally, we must ensure that any and all changes made are properly aligned with iur existing logic for group leaders to modify drop submissions on discord using context menus; so that changes made to splits there are reflected properly globally.