Difference between revisions of "LSL Protocol/Restrained Life Relay/gender"
Jump to navigation
Jump to search
Maike Short (talk | contribs) (more comments, some old ones a bit reworded, navigation box) |
|||
Line 16: | Line 16: | ||
: Please explain how !gender differs from the optional !vision extension. On [[LSL_Protocol/Restrained_Life_Relay/vision|!vision]] you wrote that you "agree 100%" that a relay should only be "providing gated access to viewer RLV commands". --[[User:Maike Short|Maike Short]] 16:04, 8 April 2009 (UTC) | : Please explain how !gender differs from the optional !vision extension. On [[LSL_Protocol/Restrained_Life_Relay/vision|!vision]] you wrote that you "agree 100%" that a relay should only be "providing gated access to viewer RLV commands". --[[User:Maike Short|Maike Short]] 16:04, 8 April 2009 (UTC) | ||
:: !gender is an ***information*** passed from the relay to the device using it so that the latter can adapt its behaviour to the avatar interacting with it (just like !version, excepted that !gender is an information about the avatar while !version is about the relay itself). On the other hand !vision is an ***action*** that should not be performed by the relay at all in the first place, but by a RLV blind fold. !gender makes no assumption whatsoever about the form or attachment point of the relay, unlike !vision. | |||
: Can this be done with @getdebug_avatarsex and @setdebug_avatarsex? --[[User:Maike Short|Maike Short]] 16:04, 8 April 2009 (UTC) | : Can this be done with @getdebug_avatarsex and @setdebug_avatarsex? --[[User:Maike Short|Maike Short]] 16:04, 8 April 2009 (UTC) | ||
:: No, because @getdebug_avatarsex actually does not work properly at all (and @setdebug_avatarsex is not remembered over sessions either) and is actually only related with the shape used by your avatar (and mind you, my avatar is male, but I used a female shape for it)... | |||
: If the protocol is extended to read the gender, there should be a way to set it, too. The relay can of course refuse that, but it should be specified in the protocol right from the beginning, so that we don't need a later hacky extension. --[[User:Maike Short|Maike Short]] 05:24, 8 April 2009 (UTC) | : If the protocol is extended to read the gender, there should be a way to set it, too. The relay can of course refuse that, but it should be specified in the protocol right from the beginning, so that we don't need a later hacky extension. --[[User:Maike Short|Maike Short]] 05:24, 8 April 2009 (UTC) | ||
:: No, the idea is simply for the device using the relay to get the information needed to adapt its emotes and/or sounds to the gender of the avatar interacting with it, not to force some sex change (which sould be an ***action*** and should not be performed by the relay itself). | |||
: "ko" should be mentioned as valid response. --[[User:Maike Short|Maike Short]] 16:04, 8 April 2009 (UTC) | : "ko" should be mentioned as valid response. --[[User:Maike Short|Maike Short]] 16:04, 8 April 2009 (UTC) | ||
:: "ko" is the normal reply for any meta command that is not recognized by the relay. I know that most relays are not coded properly and never send "ko" for unrecognized and/or invalid commands... Mine does. |
Revision as of 14:03, 12 April 2009
!gender
Not yet implemented
- Description
- meta command to pass a the gender of the relay wearer to the device using the relay.
- Effect
- When receiving this meta-command, the relay must send a special acknowledgment that contains the gender of the wearer (to be set via a menu, or a chat command, or a notecard). The valid genders are: "neuter", "male", "female", "hermaphrodite".
- Motivation
- There is currently no easy way to know the gender of the avatars interacting with a device, short of asking their player via a menu. It would be easier if the players could give the gender of their avatar to their relay once and for all, then have the devices automatically adapt their actions and/or emotes to it.
Henri Beauchamp 00:21, 7 April 2009 (UTC)
- Discussion
- Please explain how !gender differs from the optional !vision extension. On !vision you wrote that you "agree 100%" that a relay should only be "providing gated access to viewer RLV commands". --Maike Short 16:04, 8 April 2009 (UTC)
- !gender is an ***information*** passed from the relay to the device using it so that the latter can adapt its behaviour to the avatar interacting with it (just like !version, excepted that !gender is an information about the avatar while !version is about the relay itself). On the other hand !vision is an ***action*** that should not be performed by the relay at all in the first place, but by a RLV blind fold. !gender makes no assumption whatsoever about the form or attachment point of the relay, unlike !vision.
- Can this be done with @getdebug_avatarsex and @setdebug_avatarsex? --Maike Short 16:04, 8 April 2009 (UTC)
- No, because @getdebug_avatarsex actually does not work properly at all (and @setdebug_avatarsex is not remembered over sessions either) and is actually only related with the shape used by your avatar (and mind you, my avatar is male, but I used a female shape for it)...
- If the protocol is extended to read the gender, there should be a way to set it, too. The relay can of course refuse that, but it should be specified in the protocol right from the beginning, so that we don't need a later hacky extension. --Maike Short 05:24, 8 April 2009 (UTC)
- No, the idea is simply for the device using the relay to get the information needed to adapt its emotes and/or sounds to the gender of the avatar interacting with it, not to force some sex change (which sould be an ***action*** and should not be performed by the relay itself).
- "ko" should be mentioned as valid response. --Maike Short 16:04, 8 April 2009 (UTC)
- "ko" is the normal reply for any meta command that is not recognized by the relay. I know that most relays are not coded properly and never send "ko" for unrecognized and/or invalid commands... Mine does.