Refactored and fixed a lot of bugs. Creates the database but still does not properly load the settings file.

This commit is contained in:
Griatch 2015-01-08 01:25:32 +01:00
parent c96c5a1fc7
commit 0c9bf08c5a
15 changed files with 150 additions and 80 deletions

View file

@ -5,7 +5,7 @@ Player that are controlled by the server.
"""
from django.conf import settings
from evennia.players.player import DefaultPlayer
from evennia.players.players import DefaultPlayer
from evennia.scripts.scripts import Script
from evennia.commands.command import Command
from evennia.commands.cmdset import CmdSet

View file

@ -663,7 +663,7 @@ class DefaultPlayer(PlayerDB):
pass
class Guest(DefaultPlayer):
class DefaultGuest(DefaultPlayer):
"""
This class is used for guest logins. Unlike Players, Guests and their
characters are deleted after disconnection.
@ -681,7 +681,7 @@ class Guest(DefaultPlayer):
A Guest's characters aren't meant to linger on the server. When a
Guest disconnects, we remove its character.
"""
super(Guest, self).at_disconnect()
super(DefaultGuest, self).at_disconnect()
characters = self.db._playable_characters
for character in filter(None, characters):
character.delete()
@ -690,7 +690,7 @@ class Guest(DefaultPlayer):
"""
We repeat at_disconnect() here just to be on the safe side.
"""
super(Guest, self).at_server_shutdown()
super(DefaultGuest, self).at_server_shutdown()
characters = self.db._playable_characters
for character in filter(None, characters):
character.delete()
@ -700,5 +700,5 @@ class Guest(DefaultPlayer):
Guests aren't meant to linger on the server, either. We need to wait
until after the Guest disconnects to delete it, though.
"""
super(Guest, self).at_post_disconnect()
super(DefaultGuest, self).at_post_disconnect()
self.delete()