• Implement the layered, optimized client/server design
• Implement a proper item collection hierarchy (you know, stacks of items, fluids, etc).  I've already designed this and will publish my design.  The implementation will be quite easy.
• Clean up the orb.actions classes
• Fix up the garbage collection (long term project...)
• Add edit functionality in the property viewers, so you can change the property values you are viewing
• Add client-side functionality for starting and stopping activities.
• Implement the Anatomy classes
• Generalize resource management into ResourcePool class, so all icons are indexed instead of referenced by name.  This will hopefully speed up the client-server communication.  This needs to be done before starting a server on the net.
• Add admin functionality for keeping track of who is logged on, adding/removing/modifying Accounts, sending messages to currently logged on clients, and other admin stuff.
• Implement the event propagation constraints, so that you can't hear events that are out of your hearing range, etc.

Done:

• Implement the skill system
• Implement item.addFireActionListener(FireActionListener lis), and the related classes.  This is used when you want to know what an object does, and when it's properties change, but don't care about which external events reach it.  Very important...