Utilise message classes to provide consistency

Registered by Cody A.W. Somerville on 2007-11-29

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%^GREEN%^Success [<object>]:%^RESET%^" to all their success messages, we could handle that (although we'll have to stip all the current ones out). This would ensure all success messages look the same and we (or the mud admins) can easily update it (making the change system wide immediately) later (neat use case would be translation).

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

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.