The user should see these fields:

• Drop down for Spell - Hard code strings till we have a spell class
• input for Level - determines strength of potion
• update post method for new fields

Inside A GMC 4201
The trailer of the GMC 4201 is huge, it has the capacity to carry atleast 3
standard cars inside of it with room to spare. In a pinch you could probably
fit about 50 seats in here, safety would be a prime concern however. 
A Male Human (Unicorn) (dual) is sitting here.
A Male Human (Unicorn) (dual) is sitting here.
A huge RV has been parked here. (Yours)

• Review current Readme.en for gaps

• Include mudjs instructions

• Briefly describe VSCode setup

Our sandbox is composed of entities, items, characters, and locations.
Each of these classes needs a flexible, describe() method.

For reference, we have agreed upon the following convention:

class Foo:
    _name               # private variable holding the name

    def __repr__(self): # returns a proper, pythonic representation

    def __str__(self):  # returns the name

Needs a commands command (maybe just redirect to help commands?). Can add a short description to command registration and generate a list of commands available and their short descriptions to the user based on the user's permission level. Option on registration to hide commands from commands output.

The purge commands, as well as a possible break user command, should explain what will happen upon running, and ask the user to run the command a second time to confirm.

Currently NPCs only remove trees that block construction, but they should also remove the trees that will end up inside a structure's walls. This should be done before construction.

See #90 and #99.