ThreadBoard ArchivesSite FeaturesActiveworlds SupportHistoric Archives |
Changing the Owner (Sdk)
Changing the Owner // SdkcanopusOct 16, 1998, 4:57pm
Can a Bot change the Owner by using aw_object_change? I get a reason 211
for not allowing it. Can a Bot confer ownership by using aw_object_add with a specific value for AW_OBJECT_OWNER? When I try it, this specific value is ignored and the Bot's Owner is listed as the owner in the new object. When would one use the aw_int_set(AW_OBJECT_OWNER)? (It would be nice to build someone a surprise gift building.) roland vilettOct 16, 1998, 5:10pm
Yeah changing object ownership is a bit of a mess. Because of the way an
object change is handled in the world server, if there is a registry in effect in that world, the object winds up encroaching with itself and the change is rejected. So it cannot be done in worlds with a registry. If there is no registry however, you should be able to change the owner of the object, but only if the the bot instance has Eminent Domain in the world. It's theoretically possible to fix the registry problem but the solution would complicate the object_change operation significantly so it hasn't been addressed yet... AW_OBJECT_OWNER is not used by aw_object_add(). Sorry if the docs are not clear on this (I'm still working on updating and extending them.) All objects are automatically added under the ownership of the citizen doing the adding. In short, most of the time it is simply not possible to build as another person unless you know their privilege password. And I think that most of the time, this is arguably a good thing :) -Roland [View Quote] pc wizardOct 16, 1998, 5:15pm
I think the bot has to have Eminent Domain in the world in order for
that to work.. the AW_OBJECT_OWNER is the second to bottom box when you right click an object... It shows who built/"ownes" the object and if you have eminent domain you can change that. Atleast I think that's what the AW_OBJECT_OWNER is :) someone correct me if I'm wrong :) PC Wizard (ICQ-537376) wizardry at home.com http://pcwizard.ml.org [View Quote] canopusOct 17, 1998, 12:11am
Then a good example of an application that needs two bots would be a citizen
that wants to deed over a valuable and complicated set of buildings to another citizen. Till now all the first citizen can do is erase the buildings and then rebuild them again holding a privilege password on behalf of the other citizen. With bots, bot1 can survey, record, and then destroy each object in the set of buildings, and bot2 can receive the description of each object from bot1, and rebuild it exactly as before, except with the new ownership. Or is it possible for two bots in one application to have different owners? [View Quote] > Yeah changing object ownership is a bit of a mess. Because of the way an > object change is handled in the world server, if there is a registry in > effect in that world, the object winds up encroaching with itself and the > change is rejected. So it cannot be done in worlds with a registry. If > there is no registry however, you should be able to change the owner of the > object, but only if the the bot instance has Eminent Domain in the world. > > It's theoretically possible to fix the registry problem but the solution > would complicate the object_change operation significantly so it hasn't been > addressed yet... > > AW_OBJECT_OWNER is not used by aw_object_add(). Sorry if the docs are not > clear on this (I'm still working on updating and extending them.) All > objects are automatically added under the ownership of the citizen doing the > adding. > > In short, most of the time it is simply not possible to build as another > person unless you know their privilege password. And I think that most of > the time, this is arguably a good thing :) > > -Roland > [View Quote] roland vilettOct 17, 1998, 4:03am
Yes two different bots running in the same application can have completely
different owners. It's all in the attributes you set before calling aw_login() for each instance. -Roland [View Quote] |