alathon / awesomemud Goto Github PK

http://cryosphere.net/mud-protocol.html

See http://tintin.sourceforge.net/msdp/ and the msdp branch which has an MSDP.Scala file.

We may reconsider whether MSDP is in fact the correct protocol, depending on what the client ends up being.

Currently, movement displays the objects in string form (via toString()) when entering and leaving rooms and such.

Add a new DescType for name, and change the calls to use describeTo with DescType.Name instead. By default, should use GameEntity.name

Currently, the command parser has some wonky type polymorphism going on. Scala has very advanced support for a variety of different paradigms. The following changes are probably desirable:

1. Allowing commands to specify what type their source should be, as long as it is a child of GameEntity (so ex. 'Command[Mob]' leading to a source argument in go() that is a Mob)
2. Preventing CommandComponent's type information from being erased.

However, its not strictly necessary right now. But it leads to ugly code such as:

def go(source: GameEntity, args: Seq[Any]) {
source match {
case m: Mob =>
m.attemptMove("north", Some("the north"))
case _ =>
}
}

Currently, search returns a list of game entities depending on the location specified.

Extend Search.getEntitiesInLocation to require a filter function as well, and provide a Ref constructor through object Ref that supports a filter function. If no filter function is given, pass an anonymous function that simply accepts everything.

Currently, text is trimmed if not sent to an input grabber - Should it be getting trimmed before being sent to input grabbers as well??

Singleton object for stuff such as:

• List of clients online
• Current version
• Message of the day
• Any other 'global' state we'd like to be able to handily grab about the world.

Currently, commands' 'components' List has to be built manually. It would be... ideal, if it allowed a componentsText string as well, which would parse the text into a components list. For example:

componentsText = "'say'|'''; anything?" would be equivalent to
components = List(Or(Word("say"), Word("'")), Anything(optional = true))

There needs to be a way to query for multiple things in a row. In an ideal world, I would be able to define a story, f.ex:

• First, ask user for name (Constrained by specific bounds on length etc)
• Then, ask user for a gender (Constrained to male/female choice)
• Then, ask user for an e-mail (Constrained by e-mail regex)
• Then, ask user for a password (Constrained by pw constraints)
• Then, log the player in.

During all of this, the user should be able to move back to previous steps, and should be able to receive a summary at the end. Work on this is started but wholly unfinished in com.awesomeware.core.io.InputRequest.scala as a 'Story', where one story f.ex. is character creation.

It would be ideal to separate the input validation from the concept of going back/forth through a list of items the user needs to complete, and to allow common, easily-accessible ways to dispay and query for things, common validation constraints, etc. while still allowing custom on-the-fly constraints etc.