Utilise message classes to provide consistency
Registered by
Cody A.W. Somerville
The mudlib should make use of message classes (see message efun manpage) to provide consistency. For example, all success messages could set their class to success and instead of the developer adding "%^BOLD%
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- Accepted for trunk
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
(?)