Summary
The DKP (Dragon Kill Points) system should be extracted from bbGuild core into a separate plugin, developed at https://github.com/avandenberghe/bbDKP.
What to move
Log types (from constants.php + log.php)
DKPSYS_ADDED/UPDATED/DELETED (1-3)
EVENT_ADDED/UPDATED/DELETED (4-6)
HISTORY_TRANSFER (7)
INDIVADJ_ADDED/UPDATED/DELETED (8-10)
ITEM_ADDED/UPDATED/DELETED (11-13)
RAID_ADDED/UPDATED/DELETED (23-25)
RT_CONFIG_UPDATED (27)
DECAYSYNC/DECAYOFF/ZSYNC/DKPSYNC (28-31)
DEFAULT_DKP_CHANGED (32)
PLAYERDKP_UPDATED/DELETED (34-35)
Language keys
- All
ACTION_DKPSYS_*, ACTION_EVENT_*, ACTION_INDIVADJ_*, ACTION_ITEM_*, ACTION_RAID_*, ACTION_RT_*, ACTION_DECAY*, ACTION_*SYNC, ACTION_PLAYERDKP_* and their VLOG_ counterparts
- DKP keys already archived in
contrib/archive/language/*/dkp_common.php
Controllers / models
- Raid management, loot tracking, point adjustments, DKP pools
- Reference implementation in old
ext/avathar/bbdkp/
Design
- DKP plugin repo: https://github.com/avandenberghe/bbDKP
- Plugin registers its own log types via a tagged service or event listener
- bbGuild core log system accepts plugin-registered types (extend
valid_action_types)
- Plugin provides its own migrations, ACP modules, language files
Phase
Phase 3 — after core feature completion.
Summary
The DKP (Dragon Kill Points) system should be extracted from bbGuild core into a separate plugin, developed at https://github.com/avandenberghe/bbDKP.
What to move
Log types (from
constants.php+log.php)DKPSYS_ADDED/UPDATED/DELETED(1-3)EVENT_ADDED/UPDATED/DELETED(4-6)HISTORY_TRANSFER(7)INDIVADJ_ADDED/UPDATED/DELETED(8-10)ITEM_ADDED/UPDATED/DELETED(11-13)RAID_ADDED/UPDATED/DELETED(23-25)RT_CONFIG_UPDATED(27)DECAYSYNC/DECAYOFF/ZSYNC/DKPSYNC(28-31)DEFAULT_DKP_CHANGED(32)PLAYERDKP_UPDATED/DELETED(34-35)Language keys
ACTION_DKPSYS_*,ACTION_EVENT_*,ACTION_INDIVADJ_*,ACTION_ITEM_*,ACTION_RAID_*,ACTION_RT_*,ACTION_DECAY*,ACTION_*SYNC,ACTION_PLAYERDKP_*and theirVLOG_counterpartscontrib/archive/language/*/dkp_common.phpControllers / models
ext/avathar/bbdkp/Design
valid_action_types)Phase
Phase 3 — after core feature completion.