
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is original of duplicate:
|
|
SVC-1744
Returning functionality to phased.
|
|
|
|
|
Relates
|
|
This issue Relates to:
|
|
SVC-125
llSitTarget allows evasion of being detected by llSensor
|
|
|
|
|
SVC-1475
Restore the ability to choose when you can be scanned by llSensor
|
|
|
|
|
|
This issue is related to by:
|
|
SVC-1744
Returning functionality to phased.
|
|
|
|
|
|
SVC-456 Meta-Issue: Improved Anti-Griefer Tools
|
|
|
|
|
|
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar appear offline to scripts and allows you to appear truly offline to anyone that is not right beside you in world. This will allow you to avoid malicious sensors, and prevent people from interacting with your avatar when you don't want to be interacted with (for example you're busy).
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
- Causes you to ignore attempts to get permissions from you (e.g to animate you), unless you are the object owner, or on the owner's land, or sitting on the object (in which case permissions are automatically given as normal).
- Causes you to ignore dialogues from objects, unless you are the object owner, or on the owner's land, or sitting on the object (in which case permissions are automatically given as normal).
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
In addition to this, the option will enable more robust IM/chat ignoring functions in combination with "Busy" mode. i.e. - if you set yourself to privacy mode, then any IMs you receive will be replied to with the "User offline" message, unless the user in question is on your friends list and always allowed to see you. You will receive chat as normal.
If you are in privacy mode AND busy, then your viewer will queue any IMs you receive and reply with the user offline message to people, or in the case of friends who are always able to see you, they will receive your busy message. All messages will be queued somewhere for you to see when you remove busy status.
As for combat/gaming/roleplay sims where this could be harmful to some functionality, there would be an estate-level function to allow land-owners to prevent privacy mode on their land. Easiest way would probably be to block "private" avatars as with non-paying or non-verified avatars, but to prompt the user with a message telling them they must disable privacy mode to enter the parcel. Otherwise the more difficult (but better) way is to add two flags to an avatar, one indicating if they have set themselves to privacy mode, and another to indicate whether they actually ARE in privacy mode. This way when you pass into a parcel that disables privacy mode, then the setting is turned off, but when you leave it is turned back on if you want it on.
|
|
Description
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar appear offline to scripts and allows you to appear truly offline to anyone that is not right beside you in world. This will allow you to avoid malicious sensors, and prevent people from interacting with your avatar when you don't want to be interacted with (for example you're busy).
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
- Causes you to ignore attempts to get permissions from you (e.g to animate you), unless you are the object owner, or on the owner's land, or sitting on the object (in which case permissions are automatically given as normal).
- Causes you to ignore dialogues from objects, unless you are the object owner, or on the owner's land, or sitting on the object (in which case permissions are automatically given as normal).
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
In addition to this, the option will enable more robust IM/chat ignoring functions in combination with "Busy" mode. i.e. - if you set yourself to privacy mode, then any IMs you receive will be replied to with the "User offline" message, unless the user in question is on your friends list and always allowed to see you. You will receive chat as normal.
If you are in privacy mode AND busy, then your viewer will queue any IMs you receive and reply with the user offline message to people, or in the case of friends who are always able to see you, they will receive your busy message. All messages will be queued somewhere for you to see when you remove busy status.
As for combat/gaming/roleplay sims where this could be harmful to some functionality, there would be an estate-level function to allow land-owners to prevent privacy mode on their land. Easiest way would probably be to block "private" avatars as with non-paying or non-verified avatars, but to prompt the user with a message telling them they must disable privacy mode to enter the parcel. Otherwise the more difficult (but better) way is to add two flags to an avatar, one indicating if they have set themselves to privacy mode, and another to indicate whether they actually ARE in privacy mode. This way when you pass into a parcel that disables privacy mode, then the setting is turned off, but when you leave it is turned back on if you want it on. |
Show » |
made changes - 08/Feb/08 04:32 AM
| Field |
Original Value |
New Value |
|
Link
|
|
This issue Relates to SVC-125
[ SVC-125
]
|
made changes - 08/Feb/08 04:33 AM
|
Link
|
|
This issue Relates to SVC-1475
[ SVC-1475
]
|
made changes - 08/Feb/08 05:38 AM
|
Description
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar completely invisible to EVERYTHING and is possibly a requirement to correctly implement an "Invisible" status. What it does is make it impossible for you to be detected, queried or ANYTHING by a person or script, though you will still be visible in world to people who can see you (but your name-tag will indicate your "busy" status).
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
- Causes you to ignore all IMs from people other than your friends, excluding friends who do not have permission to "see" you (all ignored messages are queued on your viewer somewhere for you to look at later). Ignored IMs will reply with a "User is offline" message.
- Gives your name-tag the "Busy" status for people near you to see.
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar completely invisible to EVERYTHING and is possibly a requirement to correctly implement an "Invisible" status. What it does is make it impossible for you to be detected, queried or ANYTHING by a person or script, though you will still be visible in world to people who can see you.
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
In addition to this, the option will enable more robust IM/chat ignoring functions in combination with "Busy" mode. i.e. - if you set yourself to invisible, then any IMs you receive will be replied to with the "User offline" message, unless the user in question is on your friends list and always allowed to see you. You will receive chat as normal.
If you are invisible AND busy, then your viewer will queue any IMs you receive and reply with the user offline message to people, or in the case of friends who are always able to see you, they will receive your busy message. All messages will be queued somewhere for you to see when you remove busy status.
As for combat/gaming/roleplay sims where this could be harmful to some functionality, there would be an estate-level function to allow land-owners to prevent invisible status on their land. Easiest way would probably be to block invisible avatars as with non-paying or non-verified avatars, but to prompt the user with a message telling them they must be "visible" to enter the parcel.
|
made changes - 08/Feb/08 04:44 PM
|
Link
|
|
This issue is related to by SVC-456
[ SVC-456
]
|
made changes - 09/Feb/08 03:03 AM
|
Summary
|
Invisible Mode
|
Invisible/Privacy Mode
|
made changes - 29/Feb/08 04:18 PM
|
Description
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar completely invisible to EVERYTHING and is possibly a requirement to correctly implement an "Invisible" status. What it does is make it impossible for you to be detected, queried or ANYTHING by a person or script, though you will still be visible in world to people who can see you.
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
In addition to this, the option will enable more robust IM/chat ignoring functions in combination with "Busy" mode. i.e. - if you set yourself to invisible, then any IMs you receive will be replied to with the "User offline" message, unless the user in question is on your friends list and always allowed to see you. You will receive chat as normal.
If you are invisible AND busy, then your viewer will queue any IMs you receive and reply with the user offline message to people, or in the case of friends who are always able to see you, they will receive your busy message. All messages will be queued somewhere for you to see when you remove busy status.
As for combat/gaming/roleplay sims where this could be harmful to some functionality, there would be an estate-level function to allow land-owners to prevent invisible status on their land. Easiest way would probably be to block invisible avatars as with non-paying or non-verified avatars, but to prompt the user with a message telling them they must be "visible" to enter the parcel.
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar completely invisible to EVERYTHING and is possibly a requirement to correctly implement an "Invisible" status. What it does is make it impossible for you to be detected, queried or ANYTHING by a person or script, though you will still be visible in world to people who can see you.
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
In addition to this, the option will enable more robust IM/chat ignoring functions in combination with "Busy" mode. i.e. - if you set yourself to invisible, then any IMs you receive will be replied to with the "User offline" message, unless the user in question is on your friends list and always allowed to see you. You will receive chat as normal.
If you are invisible AND busy, then your viewer will queue any IMs you receive and reply with the user offline message to people, or in the case of friends who are always able to see you, they will receive your busy message. All messages will be queued somewhere for you to see when you remove busy status.
As for combat/gaming/roleplay sims where this could be harmful to some functionality, there would be an estate-level function to allow land-owners to prevent invisible status on their land. Easiest way would probably be to block invisible avatars as with non-paying or non-verified avatars, but to prompt the user with a message telling them they must be "visible" to enter the parcel. Otherwise the more difficult (but better) way is to add two flags to an avatar, one indicating if they have set themselves to invisible, and another to indicate whether they actually ARE invisible. This way when you pass into a parcel that disables "invisibility", then the setting is turned off, but when you leave it is turned back on if you have set yourself to invisible.
|
made changes - 03/Mar/08 03:40 PM
|
Link
|
|
This issue is related to by SVC-1744
[ SVC-1744
]
|
made changes - 04/Mar/08 05:24 AM
|
Link
|
|
This issue is duplicated by SVC-1744
[ SVC-1744
]
|
made changes - 04/Mar/08 09:25 AM
|
Summary
|
Invisible/Privacy Mode
|
Privacy Mode (Make yourself invisible to scripts)
|
|
Description
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar completely invisible to EVERYTHING and is possibly a requirement to correctly implement an "Invisible" status. What it does is make it impossible for you to be detected, queried or ANYTHING by a person or script, though you will still be visible in world to people who can see you.
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
In addition to this, the option will enable more robust IM/chat ignoring functions in combination with "Busy" mode. i.e. - if you set yourself to invisible, then any IMs you receive will be replied to with the "User offline" message, unless the user in question is on your friends list and always allowed to see you. You will receive chat as normal.
If you are invisible AND busy, then your viewer will queue any IMs you receive and reply with the user offline message to people, or in the case of friends who are always able to see you, they will receive your busy message. All messages will be queued somewhere for you to see when you remove busy status.
As for combat/gaming/roleplay sims where this could be harmful to some functionality, there would be an estate-level function to allow land-owners to prevent invisible status on their land. Easiest way would probably be to block invisible avatars as with non-paying or non-verified avatars, but to prompt the user with a message telling them they must be "visible" to enter the parcel. Otherwise the more difficult (but better) way is to add two flags to an avatar, one indicating if they have set themselves to invisible, and another to indicate whether they actually ARE invisible. This way when you pass into a parcel that disables "invisibility", then the setting is turned off, but when you leave it is turned back on if you have set yourself to invisible.
|
This is an option I've come up with in response to the complaining in SVC-125 about griefers using cage-guns etc.
Essentially it makes your avatar appear offline to scripts and allows you to appear truly offline to anyone that is not right beside you in world. This will allow you to avoid malicious sensors, and prevent people from interacting with your avatar when you don't want to be interacted with (for example you're busy).
It will do the following:
- Make you invisible to sensors, unless you are the owner, or on the owner's land (so security scripts can still see you).
- Make you always return an offline status to llGetAgentData() calls, unless you are the owner, or on the owner's land (though why it'd matter is beyond me).
- Make you always return null values to llGetObjectDetails() calls using your avatar key, unless you're on the owner's land.
- Make you always return false, or an error to calls to llGetAgentInfo() unless the script is owned by you, or you are on the owner's land.
- Causes you to ignore attempts to get permissions from you (e.g to animate you), unless you are the object owner, or on the owner's land, or sitting on the object (in which case permissions are automatically given as normal).
- Causes you to ignore dialogues from objects, unless you are the object owner, or on the owner's land, or sitting on the object (in which case permissions are automatically given as normal).
There may be some specific scripting functions I missed, but you get the idea, basically the scripting virtual machine will be aware of your invisible status for ALL functions that can process an avatar's key.
It essentially makes it impossible for follower scripts and similar annoyances to follow or target you in any way.
In addition to this, the option will enable more robust IM/chat ignoring functions in combination with "Busy" mode. i.e. - if you set yourself to privacy mode, then any IMs you receive will be replied to with the "User offline" message, unless the user in question is on your friends list and always allowed to see you. You will receive chat as normal.
If you are in privacy mode AND busy, then your viewer will queue any IMs you receive and reply with the user offline message to people, or in the case of friends who are always able to see you, they will receive your busy message. All messages will be queued somewhere for you to see when you remove busy status.
As for combat/gaming/roleplay sims where this could be harmful to some functionality, there would be an estate-level function to allow land-owners to prevent privacy mode on their land. Easiest way would probably be to block "private" avatars as with non-paying or non-verified avatars, but to prompt the user with a message telling them they must disable privacy mode to enter the parcel. Otherwise the more difficult (but better) way is to add two flags to an avatar, one indicating if they have set themselves to privacy mode, and another to indicate whether they actually ARE in privacy mode. This way when you pass into a parcel that disables privacy mode, then the setting is turned off, but when you leave it is turned back on if you want it on.
|
made changes - 20/Apr/08 12:34 PM
|
Status
|
Open
[ 1
]
|
Closed
[ 6
]
|
|
Resolution
|
|
Duplicate
[ 3
]
|
made changes - 20/Apr/08 12:38 PM
|
Resolution
|
Duplicate
[ 3
]
|
|
|
Status
|
Closed
[ 6
]
|
Reopened
[ 4
]
|
made changes - 27/May/08 09:09 PM
|
Priority
|
Major
[ 3
]
|
Normal
[ 4
]
|
made changes - 13/Nov/08 12:07 PM
|
Workflow
|
jira-2007-12-22a
[ 51992
]
|
jira-2008-11-14
[ 81651
]
|
made changes - 13/Nov/08 04:35 PM
|
Workflow
|
jira-2008-11-14
[ 81651
]
|
jira-2008-11-14a
[ 88690
]
|
made changes - 29/Jul/09 01:56 PM
|
Comment
|
[ Comment retracted
]
|
|
made changes - 30/Sep/09 01:32 PM
|
Affects Version/s
|
|
1.30 Server
[ 10510
]
|
|
Affects Version/s
|
|
1.27 Server
[ 10460
]
|
|
Affects Version/s
|
|
1.26 Server
[ 10420
]
|
|
Affects Version/s
|
|
1.25 Server
[ 10380
]
|
|
Affects Version/s
|
|
1.24 Server
[ 10351
]
|
|
Affects Version/s
|
|
1.23.4 Server
[ 10343
]
|
|
Affects Version/s
|
|
1.22.4 Server
[ 10340
]
|
|
Affects Version/s
|
|
1.22.3 Server
[ 10331
]
|
|
Affects Version/s
|
|
1.22.2 Server
[ 10330
]
|
|
Affects Version/s
|
|
1.22.1 Server
[ 10320
]
|
|
Affects Version/s
|
|
1.21.0 Server
[ 10310
]
|
|