Rework unregistered players

[kharidiron]

The current permissions system doesn't make sense at the lowest two levels (unregistered/guest vs registered players). What needs to be done to correct this:

• Guest players should not be stored in the player.db at all. They are guests... they go no special treatment.
  • I believe this will also require adding a guest template to catch all their permission requests... I'll need to think about this more...
• Once guests are registered, provide name-locking. Right now, this is default for anyone who logs in, guest or otherwise.
• Unregistered players cannot place or remove blocks/items/etc on protected planets. This will be a rather involved fix, since it requires us collecting all the packets from the packet stream, and making sure ones we don't like don't happen.

I'm going to leave it at this for now... there will probably be more that will need to be included later.

[kharidiron]

There may be an issue regarding the /who and /whois information used on guest accounts. If we remove them completely from the player.db, we loose that information... so instead, we might need to create a guest.db instead.

If we must keep everything in one table, we might need to rework the 'this name is already taken' response to account for account level. This might actually be the easier solution.