Communication System #24
Description
Currently, the only available forms of communication for user code are to use the Senses API or to create a CommandResult within the flow of a command. This is all well and good, but it does not allow user code to send arbitrary messages to an arbitrary user from an arbitrary place in the code. Support should be added for this.
Example implementation: Create a "Message" class. The default constructor uses the magic power of AspectJ to determine the current connection's Communicator based on the flow of control. But the other constructor takes a Communicator directly. We will then need to provide some kind of system to allow retrieval of arbitrary Communicators. The simplest solution is to attach a Communicator instance to the Player object, but I am not sure if I like that.