====== Utilise message classes to provide consistency ======

===== Overview =====

**Launchpad URL:** [[https://blueprints.launchpad.net/sapidlib/+spec/message-classes|https://blueprints.launchpad.net/sapidlib/+spec/message-classes]]

**Description:** 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. 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). Furthermore, we could use message classes to allow users to set custom colours for tells, says, etc.

**Components affected:** Objects that that write output to the screen, the mobile object

**Contributors:** CodySomerville

===== Release Notes =====

//Describe what should be in the release notes when this is implemented//

===== Rationale =====

//Describe the rationale of this specification//

===== Use Cases =====

//Describe two or more use cases//

===== Design =====

//Describe the design of this specification//

===== Implementation =====

//Describe how this specification will be implemented//

===== Discussion =====

//Discussion and comments would go here.//