
|
If you were logged in you would be able to see more operations.
|
|
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or something
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automatically accepting a scripted teleport a toggleable options on the world menu or something. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it could be used as part of game mechanics, someone might want p2p teleport commanded by chat etc would all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
TigroSpottystripes Katsu - 03/Sep/08 08:00 PM - edited
hm...I'm starting to see the point against completely automated tps...
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automatically be pressed after N seconds (30 is too much?) to allow it to work completely without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (kinda like a "loading" screen, to contribute to some extent with the suspension of disbelief, something like a screen shot of the teleporting effect or something. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself
|
|
Description
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or something
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automatically accepting a scripted teleport a toggleable options on the world menu or something. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it could be used as part of game mechanics, someone might want p2p teleport commanded by chat etc would all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
TigroSpottystripes Katsu - 03/Sep/08 08:00 PM - edited
hm...I'm starting to see the point against completely automated tps...
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automatically be pressed after N seconds (30 is too much?) to allow it to work completely without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (kinda like a "loading" screen, to contribute to some extent with the suspension of disbelief, something like a screen shot of the teleporting effect or something. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself |
Show » |
made changes - 14/Sep/08 06:41 PM
| Field |
Original Value |
New Value |
|
Description
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or somthing
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automaticly accepting a scripted teleport a toggleable options on the world menu or somthing. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it coudl be used as part of game mechanics, someone might want p2p teleport commanded by chat etc woudl all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
hm...I'm starting to see the point against completly automated tps;;;
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automaticly be pressed after N seconds (30 is too much?) to allow it to work completly without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (knda like a "loading" screen, to contribute to some extent with the suspension of disbelief, somthing like a screen shot of the teleporting effect or somthing. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or somthing
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automaticly accepting a scripted teleport a toggleable options on the world menu or somthing. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it coudl be used as part of game mechanics, someone might want p2p teleport commanded by chat etc woudl all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
TigroSpottystripes Katsu - 03/Sep/08 08:00 PM - edited
hm...I'm starting to see the point against completly automated tps;;;
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automaticly be pressed after N seconds (30 is too much?) to allow it to work completly without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (knda like a "loading" screen, to contribute to some extent with the suspension of disbelief, somthing like a screen shot of the teleporting effect or somthing. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself
|
made changes - 14/Sep/08 06:42 PM
|
Link
|
|
This issue Relates to SVC-212
[ SVC-212
]
|
made changes - 14/Sep/08 06:53 PM
|
Summary
|
a couple of sugegstions regarding llTelepórtAgent
|
a couple of suggestions regarding llTeleportAgent
|
made changes - 14/Sep/08 06:59 PM
|
Description
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or somthing
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automaticly accepting a scripted teleport a toggleable options on the world menu or somthing. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it coudl be used as part of game mechanics, someone might want p2p teleport commanded by chat etc woudl all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
TigroSpottystripes Katsu - 03/Sep/08 08:00 PM - edited
hm...I'm starting to see the point against completly automated tps;;;
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automaticly be pressed after N seconds (30 is too much?) to allow it to work completly without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (knda like a "loading" screen, to contribute to some extent with the suspension of disbelief, somthing like a screen shot of the teleporting effect or somthing. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or something
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automatically accepting a scripted teleport a toggleable options on the world menu or something. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it could be used as part of game mechanics, someone might want p2p teleport commanded by chat etc would all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
TigroSpottystripes Katsu - 03/Sep/08 08:00 PM - edited
hm...I'm starting to see the point against completely automated tps;;;
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automatically be pressed after N seconds (30 is too much?) to allow it to work completely without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (kinda like a "loading" screen, to contribute to some extent with the suspension of disbelief, something like a screen shot of the teleporting effect or something. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself
|
made changes - 14/Sep/08 07:07 PM
|
Description
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or something
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automatically accepting a scripted teleport a toggleable options on the world menu or something. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it could be used as part of game mechanics, someone might want p2p teleport commanded by chat etc would all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
TigroSpottystripes Katsu - 03/Sep/08 08:00 PM - edited
hm...I'm starting to see the point against completely automated tps;;;
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automatically be pressed after N seconds (30 is too much?) to allow it to work completely without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (kinda like a "loading" screen, to contribute to some extent with the suspension of disbelief, something like a screen shot of the teleporting effect or something. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself
|
gonna post here some of the suggestions I made for the proposed llTeleportAgent function (please feel free to reorganize the text if you think it would be an improvement as long as you don't distort my ideas)
-------------------
TigroSpottystripes Katsu - 02/Sep/08 10:20 PM
I believe a similar level of grief can be done with rezzing a phys cage that bounces people away or something
having parcel owners choose if only the owners or if everyone can do it, and perhaps also limiting the destinations (only in this parcel, only to this coordinates etc), adding the instant teleports to the bumps and pushes log, and perhaps also including the ability to teleport among the abilities that get disabled when an object/avatar is muted and a few other things probably would allow this to be used to it's full potential without opening all that many griefing possibilities. Perhaps also make automatically accepting a scripted teleport a toggleable options on the world menu or something. (displaying the regular teleport dialog if it is disabled, and showing one of those first time messages instructing newbies (and people unaware of the changes) about it)
(of course, in the beginning all of those options would be set to the most restrictive by default, so no one would be affected by the change without being aware of it)
TigroSpottystripes Katsu - 03/Sep/08 05:44 AM
it could be used as part of game mechanics, someone might want p2p teleport commanded by chat etc would all require non-landowners to be able to run the command
I was thinking it could receive restrictions similar to llPushObject (except stuff like the strength crippling that came with H4, that sucks)
TigroSpottystripes Katsu - 03/Sep/08 08:00 PM - edited
hm...I'm starting to see the point against completely automated tps...
how about sending the avatar to some sort of "limbo" in the origin sim so the avatar looks like it is already not there anymore (perhaps a negative, or way above 4096 altitude), and instead of showing the avatar to the user, show a screen with a dialog with a time-out for the ok, the screen would give information about the destination (perhaps similar to that window that opens when tping form a landmark), and besides the the ok button (would automatically be pressed after N seconds (30 is too much?) to allow it to work completely without user interaction, and also a "time-in" system to keep it disabled for a small bit to help both with avoiding people clicking on the thing without being sure they want to, and to throttle the rate of auto-tps, or perhaps a checkbox that would be unchecked when the thing shows that only when checked the OK button would become enabled, perhaps have a debug_setting to define the timer for more advanced users), there would also be a button like "always accept auto-tps from this user" (and perhaps also "always accept auto-tps from this object"), as well as a mute button for the user (to mute everything by the user) and a mute for that object only (like for when a script goes borky and the owner can't fix at the moment, but you don't want to mute the owner, just get rid of the auto-tps), and of course a button to cancel the tp just this time (pressing this would send the av back to where it was when it was teleported
behind that window the screen would be filled with a texture specified by the script (kinda like a "loading" screen, to contribute to some extent with the suspension of disbelief, something like a screen shot of the teleporting effect or something. Also perhaps allow the command to choose between a simple window with just the name and coordinates of the destination in a corner of the screen and a regular full-featured window with the about land info and pics and stuff centered
having an object, or avatar muted like this would prevent the auto-tp process from even being started, the user wouldn't notice anything if a muted object tried to auto-tp them
edit:and perhaps under special conditions (like the parcel owner teleporting someone to another parcel owned by them in the same sim, and scripts tping their owner), provide the option of not requiring user interaction at all nor throttling timers, this would help with things like games that rely on auto-tps and gadgets to tp yourself
|
made changes - 13/Nov/08 11:06 AM
|
Workflow
|
jira-2007-12-22a
[ 59165
]
|
jira-2008-11-14
[ 64214
]
|
made changes - 13/Nov/08 11:27 AM
|
Workflow
|
jira-2007-12-22a
[ 64214
]
|
jira-2008-11-14
[ 71657
]
|
made changes - 13/Nov/08 04:54 PM
|
Workflow
|
jira-2008-11-14
[ 71657
]
|
jira-2008-11-14a
[ 95132
]
|
made changes - 13/Nov/08 05:10 PM
|
Workflow
|
jira-2008-11-14
[ 95132
]
|
jira-2008-11-14a
[ 100888
]
|
made changes - 13/Nov/08 05:18 PM
|
Workflow
|
jira-2008-11-14
[ 100888
]
|
jira-2008-11-14a
[ 104004
]
|
made changes - 13/Nov/08 05:30 PM
|
Workflow
|
jira-2008-11-14
[ 104004
]
|
jira-2008-11-14a
[ 108966
]
|
made changes - 13/Nov/08 05:59 PM
|
Workflow
|
jira-2008-11-14
[ 108966
]
|
jira-2008-11-14a
[ 118821
]
|
made changes - 13/Nov/08 06:24 PM
|
Workflow
|
jira-2008-11-14
[ 118821
]
|
jira-2008-11-14a
[ 127893
]
|
made changes - 13/Nov/08 06:43 PM
|
Workflow
|
jira-2008-11-14
[ 127893
]
|
jira-2008-11-14a
[ 135124
]
|
|