altf4/RealTimeTactics — Issue #33: Reorganize message types to have sub-types
Author: altf4
Created: 2012-03-07 04:14:55+00:00
State: open

Currently, there is only one "type" variable for messages, and it's owned by the parent Message class. As the number of types increases, this field is getting crowded. It's time to make more.

Each message Class should have its own sub-type. And then the existing Message's "type" field should be made to just hold an enum of what class the message should be. (IE: An aide in casting the Message to the correct child class) Each child class will have their own enum that describes what exact message is being sent.