Run Migrate. Implemented a full separation between Player and Character - Players (OOC entities) can now also hold cmdsets and execute commands. This means that "disconnecting" from a Character becomes possible, putting the Player in an "OOC" state outside the game. This overall makes the game much more stable since there used to be issues if the character was destroyed. Having an OOC set also avoids the previous problem of @puppeting into an object that didn't have any cmdset of its own - you couldn't get back out! A new default OOC-Cmdset handles commands available to a player while OOC. Commands in this set are applied with a low priority, allowing "IC" mode to give precedence if desired.

This change meant several changes to the lock and permission functionality, since it becomes important if permissions are assigned on the Player or on their Character (lock functions pperm() and pid() etc check on Player rather than Character). This has the boon of allowing Admins to switch and play/test the game as a "Low access" character as they like.

Plenty of bug fixes and adjustments. Migrations should make sure to move over all data properly.

game/gamesrc/objects/baseobjects.py

@@ -44,12 +44,6 @@ class Object(BaseObject):
     
     Hooks (these are class methods, so their arguments should also start with self): 
 
-     basetype_setup() - only called once, when object is first created, before
-                       at_object_creation(). Sets up semi-engine-specific details such as 
-                       the default lock policy, what defines a Room, Exit etc. 
-                       Usually not modified unless you want to overload the default
-                       security restriction policies.
-
      at_object_creation() - only called once, when object is first created.
                             Almost all object customizations go here. 
      at_first_login() - only called once, the very first time user logs in.