You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
While testing an experience based scripted teleporter system I noticed two issues:
Requesting exp perms of agents that didn't yet have the exp allowed that were over parcels that also didn't have the exp allowed, failed.
Attempting to teleport an agent who had the experience allowed, but was on a parcel that didn't, failed.
The above scenarios happened with the agent over land owned by the same owner as the parcel the teleporter was over, just not set to allow the same experience.
These are expected behaviours, but if we had a means of checking if the experience is allowed/blocked at a given parcel we could prevent such scenario's and let the user know they need to move to the same parcel or offer a location url of a designated parcel where the experience is allowed.
Proposed functions and syntax:
integer ExperienceAllowedAt(vector pos) - returns TRUE if the parcel at pos allows the same experience as associated with this script AND the exp is not blocked at the region level, returns FALSE if the exp is blocked or not allowed on the parcel at pos or if exp is blocked at the region level.
integer ExperienceBlockedAt(vector pos) - returns TRUE if the same experience as associated with this script is blocked on the parcel at pos or if it is blocked at the region level, returns FALSE if the exp is not blocked both on the parcel at pos and at the region level.
Both functions return -1 if no experience is associated with the script.
Aside from aiding in checks during operation, these functions can aid in setup of teleport devices at high altitude where parcel boundaries are not easily visible or if a land owner or moderator has forgotten to allow the experience on a parcel.
Thanks in advance for any consideration.
Additional Information
The general XP_ERROR_NOT_PERMITTED error is returned with far too many scenarios, including the issues mentioned above as well as the user denying or blocking the request or the experience not being allowed on the same parcel.
Alternatively, if this error can be broken down more efficiently it may do the job just as well.
{
'Business Unit': ['Platform'],
'Date of First Response': '2014-08-06T13:59:20.475-0500',
'How would you like the feature to work?': "While testing an experience based scripted teleporter system I noticed two issues:\r\n\r\n- Requesting exp perms of agents that didn't yet have the exp allowed that were over parcels that also didn't have the exp allowed, failed.\r\n- Attempting to teleport an agent who had the experience allowed, but was on a parcel that didn't, failed.\r\n\r\nThese are expected behaviours, but if we had a means of checking if the experience is allowed/blocked at a given parcel we could prevent such scenario's and let the user know they need to move to the same parcel or offer a location url of a designated parcel where the experience is allowed.\r\n\r\nProposed functions and syntax:\r\ninteger ExperienceAllowedAt(vector pos) - returns TRUE if the parcel at pos allows the same experience as associated with this script AND the exp is not blocked at the region level, returns FALSE if the exp is blocked or not allowed on the parcel at pos or if exp is blocked at the region level.\r\ninteger ExperienceBlockedAt(vector pos) - returns TRUE if the same experience as associated with this script is blocked on the parcel at pos or if it is blocked at the region level, returns FALSE if the exp is not blocked both on the parcel at pos and at the region level.\r\n\r\nAside from aiding in checks during operation, these functions can aid in setup of teleport devices at high altitude where parcel boundaries are not easily visible or if a land owner or moderator has forgetten to allow the experience on a parcel.\r\n\r\nThanks in advance for any consideration.",
'Target Viewer Version': 'viewer-development',
'What just happened?': 'Moved it to a private DB',
'What were you doing when it happened?': 'In outer space somewhere',
'What were you expecting to happen instead?': "Didn't think about the need to have this public until after the initial move",
'Why is this feature important to you? How would it benefit the community?': '?',
}
The text was updated successfully, but these errors were encountered:
Information
While testing an experience based scripted teleporter system I noticed two issues:
Requesting exp perms of agents that didn't yet have the exp allowed that were over parcels that also didn't have the exp allowed, failed.
Attempting to teleport an agent who had the experience allowed, but was on a parcel that didn't, failed.
The above scenarios happened with the agent over land owned by the same owner as the parcel the teleporter was over, just not set to allow the same experience.
These are expected behaviours, but if we had a means of checking if the experience is allowed/blocked at a given parcel we could prevent such scenario's and let the user know they need to move to the same parcel or offer a location url of a designated parcel where the experience is allowed.
Proposed functions and syntax:
integer ExperienceAllowedAt(vector pos) - returns TRUE if the parcel at pos allows the same experience as associated with this script AND the exp is not blocked at the region level, returns FALSE if the exp is blocked or not allowed on the parcel at pos or if exp is blocked at the region level.
integer ExperienceBlockedAt(vector pos) - returns TRUE if the same experience as associated with this script is blocked on the parcel at pos or if it is blocked at the region level, returns FALSE if the exp is not blocked both on the parcel at pos and at the region level.
Both functions return -1 if no experience is associated with the script.
Aside from aiding in checks during operation, these functions can aid in setup of teleport devices at high altitude where parcel boundaries are not easily visible or if a land owner or moderator has forgotten to allow the experience on a parcel.
Thanks in advance for any consideration.
Additional Information
The general XP_ERROR_NOT_PERMITTED error is returned with far too many scenarios, including the issues mentioned above as well as the user denying or blocking the request or the experience not being allowed on the same parcel.
Alternatively, if this error can be broken down more efficiently it may do the job just as well.
Original Jira Fields
The text was updated successfully, but these errors were encountered: