AltAway Help

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
 ====== Bunny Dayz Two ======

If installed, this plugin allows for on-the-fly changes of object attributes, based on existing attributes.  This is purely a display override - no changes to the database are made, and thus the effect is non-permenant.

This plugin is in active development; if you cannot achieve what you want, ask, and it may be extended.

Create a trigger object of type <204 Bus Stop> (temporary id; this may change.)

Set properties on this in the form\\
<from|to>(<parent>)<fieldname> of value <value(|value..)>\\
e.g.\\
fromclassNumber  24\\
fromparentimageURL  a.AthleticFem.img\\
toimageURL "h.bunnyR.img"\\

This would make any object with a classNumber of 24, i.e., a head, with a parent object with the AthleticFem image, i.e. that particular body type, and it would change the head to a bunny.  Or in short, anybody with a AthleticFem body will appear with bunny heads.

'from' rules are additive - all must match in order for the 'to' rules to take effect.
Value in 'from's can be in the form aaa|bbb|ccc where any of the supplied values aaa, bbb or ccc will be matched against the object.
Value in 'to' is singular, and will replace the field value in the object.

To create additional effects, or "or" cases, just create another trigger object and add alternate properties to that too.

An additional property of name "invisibletoself" is also available. Setting this to 1 will, for any change affecting an avatar or its immediate child objects (e.g, the head,) not show the change to that particular avatar's owner - only everybody else in the region will see the change.  This is what the original Bunny Dayz plugin did, and was a cuase of much confusion and merriment.

Each trigger object is processed in turn.  Thus a change made in one might be tested against by another, and changes may overwrite previous changes.  Usually triggers are processed in database-object-id order, but this is not guaranteed and is mostly invisible to the end user.   It is therefore advisable not to construct triggers that might conflict.

To see what properties are already set on your trigger object, say **/proplist <noid>**