Fixed bug with how PlayerDB import was handled
This commit is contained in:
parent
e7de2de63b
commit
38090e686f
1 changed files with 2 additions and 2 deletions
|
|
@ -21,7 +21,6 @@ from django.conf import settings
|
||||||
from src.typeclasses.models import (TypedObject, TagHandler, NickHandler,
|
from src.typeclasses.models import (TypedObject, TagHandler, NickHandler,
|
||||||
AliasHandler, AttributeHandler)
|
AliasHandler, AttributeHandler)
|
||||||
from src.objects.manager import ObjectManager
|
from src.objects.manager import ObjectManager
|
||||||
from ev import managers
|
|
||||||
from src.players.models import PlayerDB
|
from src.players.models import PlayerDB
|
||||||
from src.commands.cmdsethandler import CmdSetHandler
|
from src.commands.cmdsethandler import CmdSetHandler
|
||||||
from src.commands import cmdhandler
|
from src.commands import cmdhandler
|
||||||
|
|
@ -724,7 +723,8 @@ class ObjectDB(TypedObject):
|
||||||
pid = int(pid[:pid.find(")")])
|
pid = int(pid[:pid.find(")")])
|
||||||
except ValueError:
|
except ValueError:
|
||||||
return False
|
return False
|
||||||
player = managers.players.get_id(pid)
|
players = PlayerDB.objects
|
||||||
|
player = players.get_id(pid)
|
||||||
player.db._playable_characters.remove(self)
|
player.db._playable_characters.remove(self)
|
||||||
|
|
||||||
# See if we need to kick the player off.
|
# See if we need to kick the player off.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue