Différences

Ci-dessous, les différences entre deux révisions de la page.

--- nexus_teleporter [2022/12/07 21:06] – admin
+++ nexus_teleporter [2025/01/06 18:56] (Version actuelle) – admin
@@ Ligne 1: / Ligne 1: @@
+====== Nexus Teleporter ======
+[[https://marketplace.secondlife.com/p/Nexus-Teleporter/19786826|Marketplace]]
+version 3.0
 Do you hate blue menus? Nexus Teleporter is the elegant solution for you
 TP destination are grid wide. A simpler to install version for intra-sim TP is called [[Windrose Teleporter]]
-Nexus use [[the Elite experience]]. Owner and Region or land must have allowed this experience
+Nexus use [[Blaise experience]]. Owner and Region or land must have allowed this experience
 Nexus must be able to rez object. that means For land you own Nexus and land have same owner
 or for group owned land the group must be allowed to rez objects in land options
@@ Ligne 22: / Ligne 26: @@
     - optionally you can add after the z @angle° to set where avatar will be facing on landing @0 = East, @90 = North etc
 Add the destination to your Nexus :
-- Add the renamed texture in the Nexus contents. This was the way in Nexus up to version 1.5 and still works
+- Add the renamed texture in the Nexus contents.
-for basic operation you don't need to read more
+If you need to resize the disk reset the scripts after resizing or it will come back to original size
+**for basic operation you don't need to read more**
 ------------------------------------------------------------
-Advanced operation
+**Advanced operation**
 Another way to add a (hidden) destination without putting the snapshot in the teleporter inventory
 allows to restrict that destination to group or individuals:
-- Add a line in the ~destinations notecard  with UUID_of_this_texture|name_of_texture|access_code where access_code is A for all, O for Owner, G for Group, L for List or an avatar key List is a list of avatars usernames in the ~accesslist notecard
+  * Add a line in the ~destinations notecard  with **UUID|name|access**
-Destinations added this way are not visible to others by editing the teleporter. Destination in inventory are accessible to all
+  * UUID_of_a_texture
+  * name_of_texture as you would have named it in inventory simname/x/y/z@dir
+  * access_code where access_code is
+    * A for all
+    * O for Owner
+    * G for Group
+    * L for List  (a list of avatars usernames in the ~accesslist notecard)
+    * an avatar UUID
+Destinations added this way are not visible to others by editing the teleporter. Destination in inventory are accessible to all.
 So you can mix the two ways but only destinations in the notecard can be access limited
 The first person stepping on the teleporter will define what destinations will be offered. Others standing with them will have same choice
-To limit usage of your Nexus to group or only yourself, enter 'group' or 'owner' or 'list' in the object description field.
+To **limit usage** of your Nexus to group or only yourself, enter 'group' or 'owner' or 'list' in the object description field.
   * list means access only to avatars usernames listed in the ~accesslist notecard. one per line, never with .resident
-The sound that is played to tell destinations are prepared can be changed in inventory or just deleted if you don't want any.
+The **sound** that is played to tell destinations are prepared can be changed in inventory or just deleted if you don't want any.
@@ Ligne 51: / Ligne 67: @@
   * **multiply**: when TRUE, add copies of destinations to make sure there are at least 3 displayed
   * **lag**: a tech delay that might need to be increased on laggy places if sometime not all destinations appear. normally 0.2 sec
+**your own effect**
+There is a template script called "effect script example" you can modify.
+This script does nothing but you can set it to do whatever you want when teleport occurs