[DGD] reassigning objects of an ex admin

[Schmidt, Stephen]

I don't know about what DGD or the Klib do or don't permit for reassigning
ownership of objects. However, I do know that for other reasons (legal ones)
it is vital that anything that is in the game world be clearly marked as the
property of the game. Legal ownership and ownership as defined by DGD
and Klib are obviously different things, but it is best in my experience to
keep them parallel. Anything that is an important (or even a not-so-important)
part of the game world should clearly be identified with the system and not
with any particular admin.
 
This might mean, in a persistent setup, that you'd have to delete all the
objects used in testing, change the ownership, then recreate them all.
Not sure as I haven't done much work in persistent environments....
 
Steve

________________________________

From: dgd-bounces at dworkin.nl on behalf of Shentino
Sent: Mon 10/15/2007 9:25 PM
To: All about Dworkin's Game Driver
Subject: [DGD] reassigning objects of an ex admin



Just reading phantasmal's docs and thought of something...

...If one of my admin's accounts goes away, what do I do with his objects?

If they're already linked into the mudlib, I can't very well just wipe
them, and IIRC the Klib forbids change of ownership.

What do I do?

About the only solution I could think of is making sure that
non-"Game" objects never get linked into the mud in the first
place...sorta like:

if (query_owner() != added_object->query_owner()
    error("Requested environment does not have the same owner as the
inserted object"

This would seem to preclude the combination of allowing admins to own
their objects whilst simultaneously allowing said objects to integrate
into the game world.

One would think that System would at least be able to reassign an object.
___________________________________________
https://mail.dworkin.nl/mailman/listinfo/dgd