Epic: EventHandler Deprecation and Removal #192
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference: aethyr/Aethyr#192
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background and Context
The
EventHandlerprocesses events using reflection:Module.const_get(event.type).send(event.action, ...). It is retained only for combat delayed events (punch_result, slash_result, kick_result) and NPC Reacts action sequences. The spec has a 4-phase deprecation plan: freeze, extract CombatService, migrate Reacts, remove.Demonstrable Outcome
EventHandlerclass deleted. Combat usesCombatService. Reacts usesPriorityQueue.Acceptance Criteria
@event_handlerremoved from Manager