PACKAGES & NICK-NAMES
-------------------------------------------------------------------------------
* :fs
	- :facilservil
	- The library used by :lambdamush to create the actual TCP server
* :lm
	- :lambdamush itself
* :lm-b
	- :lambdamush-base
	- A default "extension" to Lambdamush
	- Provides all of the basic user-commands ("help", "say", and more)
	- Provides the chat-system
	- Provides the movement/object/room system

Basically…
	:fs provides the low-level server bits
	:lm provides handy abstractions to allow MUSHes to be created
	:lm-b provides the actual MUSH, but can be pretty easily replaced



USER/CONNECTION/SOCKET HIERARCHY
-------------------------------------------------------------------------------
In the world of Lambdamush, there are three different ways to interact with and
represent a single connection:

* Socket
	- The actual socket of their connection, as provided by :usockets
	- As low-level as you can get; useless for our purposes
	- usocket:SOCKET data-type

* Client
	- The abstraction of this created by :facilservil
	- Middle-level; rarely useful
	- An integer randomly assigned to a connection by :facilservil
	- Can be used to store data related to a connection
		+ dialogue-data, temp-username & temppassword (etc for
		  registering or logging in) are stored to client-data
		+ Stored with `fs:client-data-set`
		+ Fetched with `fs:client-data-get`
		+ *All* data stored "to" a client with these functions is put
		  directly into memory.
	- Can be used to write text to, with `facilservil:client-write`

* User
	- The abstraction of this created by :lambdamush
	- Highest-level; the most useful for our purposes
	- A string (username) assigned to a client upon them registering or
	  logging in through the default dialogue (lm-b:*d-welcome*)
	- Can be used to store data related to a conenction
		+ Stored with `lm:user-data-set`
		+ Fetched with `lm:user-data-get`
		+ Data is fetched from the user-file or memory (depending on if
		  it's already been accessed)
		+ Data is set to memory until written to file after
		  `lm:user-data-write` has been executed

Basically…
	The hierarchy is SOCKET --> CLIENT --> USER.

	When hacking on :LM itself, use USER as much as posible, sometimes
	CLIENT, but *never* SOCKET.

	When hacking on an :LM extension (like :LM-B), try to always use USER,
	and never CLIENT or SOCKET.