Difference between revisions of "User:Toy Wylie/RLV Documentation/recvim sec"
Jump to navigation
Jump to search
(usage fix, clarification, source code fix) |
m (typo) |
||
| Line 2: | Line 2: | ||
|command=@recvim_sec|type=Restriction | |command=@recvim_sec|type=Restriction | ||
|usage=@recvim_sec=<y/n> | |usage=@recvim_sec=<y/n> | ||
|purpose=When prevented, every incoming IM will be discarded and the sender will be notified that the user cannot read them. This particular command allows exceptions issued from the same object only, opposed to the non-secure way that allows exceptions from any object. Example 1 is where all | |purpose=When prevented, every incoming IM will be discarded and the sender will be notified that the user cannot read them. This particular command allows exceptions issued from the same object only, opposed to the non-secure way that allows exceptions from any object. Example 1 is where all IMs are blocked, Example 2 is with an exception for one UUID that will be able to IM anyways. | ||
'''Note:''' To add an exception you still use @recvim:<UUID>=<add/rem> '''not''' @recvim_sec:<UUID>=<add/rem>. | '''Note:''' To add an exception you still use @recvim:<UUID>=<add/rem> '''not''' @recvim_sec:<UUID>=<add/rem>. | ||
| Line 20: | Line 20: | ||
{ | { | ||
llOwnerSay("@recvim_sec=n"); | llOwnerSay("@recvim_sec=n"); | ||
llSay(0, " | llSay(0, "IMs are now restricted."); | ||
} | } | ||
else | else | ||
| Line 43: | Line 43: | ||
{ | { | ||
llOwnerSay("@recvim_sec=n,recvim:fcf9eafc-a6b4-4de9-bda7-c44ddb649895=add"); | llOwnerSay("@recvim_sec=n,recvim:fcf9eafc-a6b4-4de9-bda7-c44ddb649895=add"); | ||
llSay(0, " | llSay(0, "IMs are now restricted, but with an exception."); | ||
} | } | ||
else | else | ||
Latest revision as of 12:56, 7 July 2010
@recvim sec
Type
Restriction
Implemented
Implemented since RLV version 1.21
Usage
@recvim_sec=<y/n>
Purpose
When prevented, every incoming IM will be discarded and the sender will be notified that the user cannot read them. This particular command allows exceptions issued from the same object only, opposed to the non-secure way that allows exceptions from any object. Example 1 is where all IMs are blocked, Example 2 is with an exception for one UUID that will be able to IM anyways.
Note: To add an exception you still use @recvim:<UUID>=<add/rem> not @recvim_sec:<UUID>=<add/rem>.
See Also
Example 1
<lsl>integer restricted = FALSE;
default {
touch_start(integer total_number)
{
if (llDetectedKey(0) != llGetOwner()) return;
restricted = 1-restricted;
if(restricted)
{
llOwnerSay("@recvim_sec=n");
llSay(0, "IMs are now restricted.");
}
else
{
llOwnerSay("@recvim_sec=y");
llSay(0, "IM restriction lifted.");
}
}
}
</lsl>Example 2
<lsl>integer restricted = FALSE;
default {
touch_start(integer total_number)
{
if (llDetectedKey(0) != llGetOwner()) return;
restricted = 1-restricted;
if(restricted)
{
llOwnerSay("@recvim_sec=n,recvim:fcf9eafc-a6b4-4de9-bda7-c44ddb649895=add");
llSay(0, "IMs are now restricted, but with an exception.");
}
else
{
llOwnerSay("@recvim_sec=y,recvim:fcf9eafc-a6b4-4de9-bda7-c44ddb649895=rem");
llSay(0, "IM restriction lifted.");
}
}
}
</lsl>