Epic: Sunset Legacy out_event() Pattern #178
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.
Blocks
Depends on
Reference: aethyr/Aethyr#178
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
Container#out_event(lines 59-77 ofcontainer.rb) distributes event hashes to all occupants of a room by iterating inventory and calling.out_event()on each object. It is called from 23 locations across movement, inventory, equipment, communication, and combat commands. Each call site constructs an event hash with message variants (to_player,to_target,to_other, etc.).This pattern predates Wisper and must be replaced with domain event broadcasting. Once all 23 call sites are converted, the
Container#out_eventmethod is deleted.Demonstrable Outcome
Zero
out_event()calls remain in the codebase.Container#out_eventis deleted. Room notifications use Wisper domain events.Acceptance Criteria
out_event()call sites replaced with Wisper broadcastsContainer#out_eventmethod deleted