Showing posts with label business. Show all posts
Showing posts with label business. Show all posts

Monday, July 27, 2015

Script: Unpacker Scripts

[Black Tulip] Script - Unpacker Scripts (Script for Designers)

(c) 2015 Auryn Beorn

Script - Unpacker Scripts in Marketplace.

Thank you for having considered this script to enhance the quality of your products. Please read the following instructions carefully, especially the ones explaining which permissions to apply to the scripts for the next owner. Failure to complete this task INVALIDATES the license governing your use of this set of scripts.

IMPORTANT!
Each script contains a check to prevent accidental give-aways. If you haven't set permissions correctly in your inventory, then the scripts will self delete when you try to use them. The best way to ensure you set permissions correctly is by doing it NOW in your inventory.

TABLE OF CONTENTS



CHANGE PERMISSIONS FOR NEXT OWNER


Check the following section on this page, knowing that each [Black Tulip] ASSET refers to the scripts contained in the package as well as the supplied mesh boxes and pose. The textures shouldn't be distributed.

IMPORTANT: If you include any no copy assets in your package box, the script will not attempt to send them, and so they will remain inside the box. The script will warn the user about this, per no-copy item that it founds. Since you're using an unpacker script, you should be always working with COPY assets for next owner.


ABOUT THE SUPPLIED MESH ITEMS, TEXTURES, AND POSE


In the event that you don't have yet any unpacking box to deliver to your customers, and/or a pose for wearable ones, you can use the included ones.

  • [Black Tulip] Holding is a priority 4 pose that you can use in conjunction with the scripts that work with animations (It's explained after this which ones are those).
  • [Black Tulip] Unpacker Box is a mesh box with a face reserved to drop your product vendor. It's textured with the UV Layout, in case you want to create your own textures for it.
  • [Black Tulip] Unpacker Box - TEXTURED is the same mesh box, with the included baked texture applied to it.
  • [Black Tulip] Unpacker Box - Add/Wear - TEXTURED is again the same mesh box, already positioned and rotated to be used with the unpacker scripts that also pose your avatar and the included [Black Tulip] Holding pose.
  • [Black Tulip] Unpacker Box - UV is a texture you can download to your computer with the guides to create your own box textures. It's color-coded so you can easily relate which parts of the mesh correspond with which parts of the UV layout texture.
  • [Black Tulip] Unpacker Box - AO is the corresponding ambient occlusion map, to add shading if you create your own box textures.
  • [Black Tulip] Unpacker Box - BAKED is a baked texture that you can use directly. The [Black Tulip] Unpacker Box - TEXTURED and [Black Tulip] Unpacker Box - Add/Wear - TEXTURED mesh items have this texture already applied.

If you've never used/textured mesh objects, you may want to check out the following documentation posts:


IMPORTANT: The space reserved for your product vendor picture is expecting an 1:1 aspect ratio texture. Product ads having a different aspect ratio may show distorted.


GIVE FOLDER ON TOUCH - BASIC


If you simply want a script that will deliver contents in a folder to the owner of the object, use the [Black Tulip] Unpacker - Give items on touch in folder BASIC script included in the package. The unpacker script itself isn't delivered in the folder.


GIVE FOLDER ON TOUCH


The [Black Tulip] Unpacker - Give items on touch in folder script gives a couple of configuration choices that the [Black Tulip] Unpacker - Give items on touch in folder BASIC script doesn't include. It allows us to add hover text indicating that the box is ready to be clicked for unpacking, and that the unpacking operation has been performed once the folder is sent.

We can decide the text by writing it in the description of the prim with the unpacker script (and the assets to be delivered in a folder) something like this:

rdy=Click to unpack#done=Unpacking complete\nEnjoy!

Notice the # character: it's separating the two fields that the script needs:

rdy=Click to unpack
done=Unpacking complete\nEnjoy!

The rdy= part is what tells the script the text you write after, will show as hover text when rezzing the box to unpack. The done= is what tells the script the text you write after, will show as hover text when the folder with items has been sent. Note that by writing \n we're introducing a carriage return in the hover text: we would use this to separate text in lines.

Try keeping your hover text concise: The description field of a prim only allows for a maximum of 127 characters.


GIVE FOLDER ON TOUCH - WEAR AND ANIMATE - BASIC


The [Black Tulip] Unpacker - Play Anim & Give items on touch BASIC script is meant for attached unpacking boxes that will play a pose/animation while attached. Neither the script nor the configured animation/pose will be sent in the folder delivered to our customer.

In order to achieve this, we need to type one command in the unpacking box description field. Before seeing what exactly, let's talk about the other feature of this script:

When setting the unpacking box to be attached, likely we've changed its rotation, so it fits with the pose. But our customers could rez the box anyway. This would leave the box rezzed in a strange rotation, like the picture shows:


If you would like that the box is rezzed with a correct rotation:


you have to supply a certain parameter also in the unpacking box description field. Let's see that now, together with how to indicate which is the animation to use as "hold" pose (Remember: This pose won't be a part of the contents of the unpacked folder.)

We can write the description of the item as follows:

anim=[Black Tulip] Holding#rot=<0,0,180>

As we can see, again the # character is separating fields, so in this case we have:

anim=[Black Tulip] Holding
rot=<0,0,180>

The first one is pretty obvious: after the anim= part, we write the name of the animation included to pose when wearing the unpacking box. Then after the rot= part, we have three numbers between < and > and separated by commas. How do we know which numbers?

We know which numbers by editing our object, and taking note of the numbers showing under the Rotation edit boxes:


We must type them in the same XYZ order they show in the Edit window, this way:

rot=<X_Value,Y_Value,Z_Value>


GIVE FOLDER ON TOUCH - WEAR AND ANIMATE


The [Black Tulip] Unpacker - Play Anim & Give items on touch script gives the same functionality than the script explained above, plus the rdy and done parameters explained for the [Black Tulip] Unpacker - Give items on touch in folder script, to show hover text. Try keeping the description brief: the description field of a prim only allows for a maximum of 127 characters.


GIVE FOLDER ON TOUCH - HUD VERSION


Creating a HUD version is not so different than creating a regular unpacking box. For starters, if you've never created a HUD and don't know how to go about it, check this tutorial about creating HUDs in SL.

There's a sample HUD supplied, no transfer, to show how you could create your own: [Black Tulip] Test HUD to Inspect - Add/Wear. Knowledge about working with linked sets and what a child prim is, is assumed here. The basic idea is, you will create different prims for the different buttons you want to include:

  • In the button that should be your product vendor picture, you include all the items to deliver plus the [Black Tulip] Unpacker - Give items on touch in folder BASIC script.
  • You may have different buttons to give a landmark to your store, a notecard with information... In all those instances of giving a single item upon touch of the button, you will drop that single item (landmark, notecard...) and the [Black Tulip] Very Simple Single-Item Giver script (with permissions correctly adjusted; green prims on the sample HUD).
  • You may also want that other buttons open a website upon touch. In that case, when editing your HUD object inworld, first, in the DESCRIPTION field of the prim, you write the web address, as-is. Again, remember that the description field of a prim only allows for a maximum of 127 characters. If you have large web addresses, you may consider services like http://tinyurl.com/ to reduce it. After this, you drop the [Black Tulip] Click for Web Address script in that prim.

    This script will write the website address in local (nearby) chat, and will also show a dialog menu offering to open the web page. If you don't want that the popup shows, simply add #no-popup in the prim's description field, after the web address you write. You find the examples to inspect on the purple prims on the sample HUD.


TROUBLESHOOTING


Q: The hover text showing isn't the one I've specified.

A: Make sure that you're using the DESCRIPTION field of the prim, not the name field.

Q: I change descriptions on the HUD, but the scripts don't read them.

A: Make sure that you're changing the description field of those prims when the HUD is rezzed inworld, not attached to your avatar.


-- Auryn Beorn
Posted by at
Labels:

Monday, November 3, 2014

Tool: Simple Teleport System

[Black Tulip] Simple Teleport System

(c) 2014 Sei Lisa, Auryn Beorn

Simple Teleport System, in Marketplace.

If you're planning on setting up a teleport system, and all of your destination locations have Teleport Routing set to Anywhere, the simplest solution might be the most effective and user friendly for your customers, and that is what this script offers to you. Set up an object that will be the teleport panel via a notecard, and you can rez copies of this object, already set up, at all places where you need your teleport board.

Please read the following instructions carefully. There's a sample object included to guide you through an example set up, so you can then set up your own teleport board. If the script isn't working as it should, please read first the Troubleshooting section of this documentation. If your problem isn't described there, then fill the following form, explaining exactly what you did and what happened, and I'll get back to you.

TABLE OF CONTENTS




FEATURES


IMPORTANT: You need Teleport Routing set to Anywhere in all of your destination locations, in order for this script to work.

  • Configure several teleport points, anywhere (each destination location requires the Teleport Routing setting specified above)
  • Each teleport point has owner only/group/everybody (all) access
  • Menu shows allowing the user to click the location and so being teleported to it
  • Location shows in private chat too (the text will not be seen by others, only by the avatar clicking)


SET UP: WHAT ELEMENTS DO I NEED FOR THIS SYSTEM?


You need three items to set up the teleport system:

  • An object that you will use as teleport board
  • The [Black Tulip] Simple Teleport System script
  • The [Black Tulip] Simple Teleport System ~CFG~ configuration notecard

Included with this package, there's a teleport board ready for up to EIGHT destinations, the [Black Tulip] Simple Teleport SAMPLE OBJECT object. You can use that one if you prefer so.

We will have to:

  • Type an identifier we choose in the DESCRIPTION field of the prims that contain teleport panels
  • Use that identifier in the configuration notecard, to define the teleport points

There can be more than one prim containing teleport panels. Make sure that each prim has a DIFFERENT description than the rest.


SETUP: EXAMINING THE SAMPLE OBJECT


Rez the [Black Tulip] Simple Teleport SAMPLE OBJECT object. Inspect it, and pay attention to the DESCRIPTION field of the prims.

The root prim has no description.
The prim with the teleport panels has the following description:

tp

This description, tp, will be relevant to the configuration notecard.

If you were working with your own teleport panel object, and you have more prims that will contain teleport destinations, this is what you have to remember: give each teleport prim an UNIQUE description.

For example, the following descriptions would be okay in different prims:

tp
tp1
tp2
tpMainArea

while the following ones would not be okay:

tp
tp1
tp1
tp2

because tp1 shows twice. Make sure your descriptions are UNIQUE in the same object.


SETUP: THE CONFIGURATION NOTECARD


The configuration notecard is named [Black Tulip] Simple Teleport System ~CFG~, and it allows us to:

  • Write comment lines, for our own clarifications. Comment lines always begin with a # character.
  • Define the teleport points: what prim, face (showing one panel) correspond to a specific location, and the access type.
  • Define a default text other than Would you like to: showing on the menu.

With the exception of comment lines, all of the other lines have the structure:

parameter = value

The accepted parameter keywords are:

TP
In here, we relate prim+face with a specific location and access type for it

txtMenu
In here, we define a text other than the default Would you like to: that shows on the menu.

Now, let's explain how the values are written and what they mean.


TP = Prim-Desc|Face-Number|Region Name|X|Y|Z|Access

We specify the definition of a teleport destination after the = sign after the TP key word. We have to write down a series of values and separate them with the | character. What do all those Prim-Desc, Face-Number, etc. mean?

Prim-Desc
The description we have written for a teleport prim

Face-Number
The face number of a prim showing a teleport panel to be clicked upon

Region Name
The region name of the destination location

X
The X coordinate of the destination location

Y
The Y coordinate of the destination location

Z
The Z coordinate of the destination location

Access
A number identifying the type of access:
  • 0: Everyone will get the teleport menu when clicking on that panel
  • 1: Only those with the group tag activated will get the teleport menu when clicking on that panel
  • 2: Only the owner of the object will get the teleport menu when clicking on that panel

We write ONE of this lines PER teleport destination. If you don't know how to obtain Region Name, X, Y and Z, check the following section, How to obtain the region data. In a moment we analyze the meaning of the lines in the included [Black Tulip] Simple Teleport System ~CFG~ configuration notecard. Before that, let's complete the notecard specification, with the other possible value.

txtMenu = Text to show on the menu

By default, the menu shows the Would you like to: text, and then the teleport link. If you would like a different text before the teleport link, write it after the = sign, and do NOT write in separate lines! All the text should be together on the same line. If you're fine with the default text, then just leave the line commented, as it is in the supplied configuration notecard.

Let's examine now the TP = lines from the supplied [Black Tulip] Simple Teleport System ~CFG~ configuration notecard:

TP = tp|0|Casablanca Estates|193|112|25|0
TP = tp|1|Casablanca Estates|215|150|35|0
TP = tp|2|Casablanca Estates|185|170|26|0
TP = tp|3|Casablanca Estates|204|90|35|0
TP = tp|4|Casablanca Estates|225|148|25|0
TP = tp|5|Casablanca Estates|199|168|36|0
TP = tp|6|Casablanca Estates|124|126|22|0
TP = tp|7|Casablanca Estates|167|172|25|0

If we count the TP = lines, we see that we have EIGHT of them. This means that the panel object will hold eight different locations.

The first line says:

TP = tp|0|Casablanca Estates|193|112|25|0

This means: When we click on the prim with description tp, the face number 0, we will be offered to teleport to Casablanca Estates region, position X = 193, Y = 112, Z = 25, and everybody will get this menu, for the access is set to 0, in the last field.

The second line says:

TP = tp|1|Casablanca Estates|215|150|35|0

This means: When we click on the prim with description tp, the face number 1, we will be offered to teleport to Casablanca Estates region, position X = 215, Y = 150, Z = 35, and everybody will get this menu, for the access is set to 0, in the last field.

and similarly, we can now understand what the other lines mean.

If we had another prim with description, for example, tp1, we could add more lines like:

TP = tp1|0|Casablanca Estates|215|140|25|1

which would mean, when we click on the prim with description tp1, the face number 0, we will be offered to teleport to Casablanca Estates region, position X = 215, Y = 140, Z = 25, and only those with their group tag on would get this menu, for the access is set to 1, in the last field.

REMEMBER: *YOU* decide what description you want to give to your prims, and then you use those descriptions in the configuration notecard.

IMPORTANT: Do not use the = character in the description of the prim, and do not leave spaces around the | characters of the notecard. Be particularly careful with possible spaces at the end of the lines, for those are easily unnoticed.

If you ever lose your configuration notecard, your documentation has an embedded copy.


SETUP: THE CONFIGURATION NOTECARD - HOW TO OBTAIN THE REGION DATA


Let's take as an example the landmark included with your purchase.

In your inventory, right click on it and select the Show on Map option. This opens the world map, showing you a red circle highlighting the location. To the right, you have some information:


Highlighted, there's the name Casablanca Estates followed by a Find button. Casablanca Estates is the region name. We would write it exactly that way. Then, under Location, we see three numbers. They correspond, respectively, to the X, Y and Z position of the destination location. So 171 would be the number to write down for X, 128, the number for Y, and finally, 25, the number for Z.


SETUP: DROPPING THE SCRIPT AND NOTECARD


Now that the configuration notecard is ready, this is how we have to proceed:

  • Right click the LINKED panel object to Edit it.
  • Do NOT tick Edit Linked. This is to ensure that script and notecard will go to the root prim.
  • Click the Content tab of the Edit window.
  • Drag from your inventory and drop on said Content tab the [Black Tulip] Simple Teleport System ~CFG~ notecard.
  • Now, drag from your inventory and drop on the Content tab the [Black Tulip] Simple Teleport System script.
  • Close the Edit window.

You will see a message show up in your local/nearby chat window telling you when the script is ready.

If you need to change/add/remove locations, you can edit the notecard inside the object, or delete it, then edit the notecard in your inventory and drag and drop it again.


TROUBLESHOOTING


Q: The script does not recognize the name I have given to the teleport prims. What happens?

A: Make sure you have written the name in the DESCRIPTION field of the prims. If you use the Name field, the script will not know those are your teleport points.


Q: I have double-checked: I've written the names in the DESCRIPTION field of the prims, but the script does not work. What's wrong?

A: Make sure that name coincides exactly with the one you write in the notecard lines. Careful with spaces at the end of the description field, for those would go unnoticed.


Q: My customers say that they get the menu and click on the teleport link, but they're not teleported to the exact location. What's happening?

A: Make sure that the Teleport Routing setting of the land properties for that destination is set to ANYWHERE.


Q: I have a customer telling me that no link shows on the menu. What's wrong here?

A: It could be that your customer is using a way outdated viewer. They should update their viewer, but in any case, they also receive in local chat a link that they can click to teleport to the destination. Let them know about this.


For any other problem not described here, please give a complete description of your issue in the customer service online form. I'll get back to you after I have read your report and replicated your issue inworld, according to your description of it. Please, be detailed.

-- Auryn Beorn
Posted by at
Labels: , ,

Saturday, November 1, 2014

Tool: Messenger/Sender Tool

[Black Tulip] Messenger/Sender Tool

(c) 2012 Auryn Beorn

Messenger/Sender Tool in Marketplace.

TABLE OF CONTENTS



FEATURES

The [Black Tulip] Messenger/Sender Tool (Messenger) is a HUD (Heads Up Display) that allows you to perform the following functions for all the avatars listed in the configuration notecard:

  • Send all the notecards contained in the HUD, plus a message
  • Send all the landmarks contained in the HUD, plus a message
  • Send all the objects contained in the HUD, plus a message
  • Send all the items (no matter the asset type) contained in the HUD, plus a message
  • Send only a message
  • Get a list of the UUIDs and avatar names of all the avatars on the sim to copy/paste in your configuration notecard

NOTE: The script itself and the configuration notecard will NOT be sent to the avatars listed in your notecard.



INSTALLATION AND USE OF YOUR MESSENGER TOOL


Wear the object [Black Tulip] Messenger/Sender Tool (wear/center). It will attach to the center attachment point of your avatar. It consists of a panel (touch area) showing all the options. Clicking the various areas of the HUD will activate the indicated function.

To use the HUD, simply Edit it, and drag the notecards/landmarks/objects/etc that you want to send into the Contents of the HUD. There are no restrictions over the number of items you can send. Check the IMPORTANT NOTES ABOUT THE ASSETS YOU WISH TO SEND section of this document for in depth notes.

Edit the configuration notecard [Black Tulip] Messenger/Sender Tool - CONFIG according to the rules of the THE CONFIGURATION NOTECARD section below.

Your HUD is ready to use.

This first version of the tool has the following options, in order from top to bottom, left to right:

Send notecard/s and message
This will ask you to type a message in a certain channel. This channel is set in the configuration notecard. You have five minutes to complete writing your message.

After writing the message and pressing ENTER, the Messenger will send all the notecards contained in the Contents of the HUD (with the exception of the configuration notecard [Black Tulip] Messenger/Sender Tool - CONFIG) together with the message, to all the avatars you have listed in the configuration notecard.

Send landmarks/s and message
This will ask you to type a message in a certain channel. This channel is set in the configuration notecard. You have five minutes to complete writing your message.

After writing the message and pressing ENTER, the Messenger will send all the landmarks contained in the Contents of the HUD together with the message, to all the avatars you have listed in the configuration notecard.

Send object/s and message
This will ask you to type a message in a certain channel. This channel is set in the configuration notecard. You have five minutes to complete writing your message.

After writing the message and pressing ENTER, the Messenger will send all the objects contained in the Contents of the HUD together with the message, to all the avatars in your list in the configuration notecard to all the avatars you have listed in the configuration notecard.

Send all and message
This will ask you to type a message in a certain channel. This channel is set in the configuration notecard. You have five minutes to complete writing your message.

After writing the message and pressing ENTER, it will send all the assets contained in the Contents of the HUD (with the exception of the configuration notecard [Black Tulip] Messenger/Sender Tool - CONFIG and the main script [Black Tulip] Messenger/Sender Tool) together with the message, to all the avatars you have listed in the configuration notecard.

Get avatars' data as list
This will output in local chat, in an owner-say message (that is, only you can see it) a list of all the UUIDs and avatar names from the avatars in the sim where you are, in a suitable format to directly copy/paste them in your configuration notecard.

Scripts can't write notecards, so this option will help you in adding UUIDs and names to your list.

Send message
This will ask you to type a message in a certain channel. This channel is set in the configuration notecard. You have five minutes to complete writing your message.

After writing the message and pressing ENTER, it will send this message to all the avatars you have listed in the configuration notecard.


THE CONFIGURATION NOTECARD


The configuration notecard must be placed in the Contents of the HUD together with the [Black Tulip] Messenger/Sender Tool script, and it has to be named [Black Tulip] Messenger/Sender Tool – CONFIG.

As we can see in the sample notecard, its format is very simple:

# [Black Tulip] Messenger/Sender Tool - CONFIG
# Lines beginning by # are ignored

channel = 5

766f3817-2f2a-469d-acfa-9789080ecc85|Auryn Beorn
c1502900-1696-45e8-904f-c58a1995c33d|Auryn (Resident)

It supports a single parameter, which must be named channel, assigned a number, as in the sample:

channel = 5

This means that the HUD will ask you to input your messages in channel #5. If you wish to use a different chat channel, simply edit the notecard in the object and change 5 to the channel number of your preference.

Then, following the channel parameter, you simply type a list indicating the avatars to whom you want to send notecards, landmarks, etc. Use one line per avatar, having this format:

UUID|Avatar Name

The | is a separator character (often called a "pipe"). You can specify whatever avatar name you prefer. This is simply informative for you; the HUD will always inform you of the progress of the task it is performing, by saying to which avatar it has sent the information, and this will be the name the HUD will use.

Check the HOW DO WE GET THE AVATAR KEY? section to learn about retrieving the UUID of an avatar.


IMPORTANT NOTES ABOUT THE ASSETS YOU WISH TO SEND


Because of a Second Life scripting limitation, the items have to be sent one at a time, per avatar. Each item sent adds a delay of 2 seconds, so if you have a long collection of items to be sent to a long list of avatars, expect the script to take some time. It will inform you of its progress, but it will require the time.

Unless stated otherwise, the references to permissions explained now are permissions for the owner of the object. That is, you.

To make sure that there won't be issues in using this tool, your assets should have one of the following permissions for you:
    Copy - Modify - Transfer (that is, FULL PERMS)
    Copy - No Modify - Transfer

If the items you want to send are not full permissions, but copy/no modify/transfer, you will have to rez the HUD, drag the desired items into its Contents, and then take the HUD back into your inventory before attaching it.

If you attempt to send a no copy asset (for you), or a no transfer asset (for you), the HUD will output an error message.

You may set permissions for NEXT OWNER as you deem necessary! It's permissions for you that need to be copy and transfer. If you're unclear about the difference between permissions for owner, and permissions for next owner, check this tutorial about the basics on permissions in SL.


HOW DO WE GET THE AVATAR KEY?


Some viewers, like Firestorm, show you the avatar key as you open a profile, over the name. But in case you don't have a viewer that allows you to obtain the key of an avatar from the avatar name, this box also contains an object that will allow you to get the key of an avatar.

Rez the object [Black Tulip] Request UUID avatar. You'll see appear a black sphere with white text over it: Click here to request an avatar UUID.

When you click the sphere, it will turn to green and the text over it will change to: Type in chat /1 FirstName LastName (New avatars, LastName = Resident)

For example, to find the key for the avatar Auryn Beorn, we have to do the following:

  • Click the sphere.
  • Type in chat:
    /1 Auryn Beorn

Then the sphere will return us text like the following:

[22:34:44]  [Black Tulip] Request UUID avatar: 0 => 4454> Auryn Beorn: Name2Key.Lookup
[22:34:45]  [Black Tulip] Request UUID avatar: 0 => 4454> Found: 766f3817-2f2a-469d-acfa-9789080ecc85

and will go back to black.

If we want to find the key of an avatar without surname, we have to add Resident, as follows (don't confuse the name with the display name!):

  • Click the sphere.
  • Type in chat:
    /1 Auryn Resident

The sphere, again, will return us text like the following:

[22:12:24]  [Black Tulip] Request UUID avatar: 0 => 214> Auryn Resident: Name2Key.Lookup
[22:12:25]  [Black Tulip] Request UUID avatar: 0 => 214> Found: c1502900-1696-45e8-904f-c58a1995c33d

and will go back to black.

To minimize lag, the sphere will wait for our request a maximum of 2 minutes. If no request has been done during two minutes, the sphere will go back to black and we'll have to click it again if we want to get an avatar key from a name.


If you have any problem with this script, please give a complete description of your issue in the following online form.

I'll get back to you after I have read your report and replicated your issue inworld, according to your description of it. Please, be detailed.

-- Auryn Beorn
Posted by at
Labels: , ,

Tool: Information Point

[Black Tulip] Information Point

(c) 2012 Auryn Beorn

Information Point in Marketplace.

TABLE OF CONTENTS



PURPOSE AND FEATURES


The purpose of the [Black Tulip] Information Point tool is to allow you to:

  • Offer to your customers a folder with one or more items providing information about your products (one per product)
  • Show a link in chat to click and join your group
  • Show a link in chat to your store blog, marketplace page or marketplace page for a specific product
  • Register if your customer has selected to get the informative folder, the group link or the web links, and when
  • IM you when a customer has chosen the informative folder, providing a link in chat so you can open their profile
  • List who/when/what in chat (only you see this chat), according to the data recorded
  • Send an e-mail at any moment to the e-mail address you choose with this who/when/what list
  • Stores up to 100 "clicks", sending you an e-mail automatically and a message in chat when this limit is reached, cleaning then all the data to begin recording again


SETTING UP YOUR "INFORMATION POINT"


In order to correctly set your information point, you have to:

  • Decide which primitive will hold all the information (notecards, pictures, etc), configuration notecard and script/s. If you use a single prim for this, you have to worry not. The above is important when your information point object consists of more than one primitive.
  • Change the DESCRIPTION of the primitive you want being your clickable information point to Information Point. Check the provided [Black Tulip] Multi Door Tool INFO (Sample 1 Prim) sample object to compare if your information point is made of one prim, or [Black Tulip] Multi Door Tool INFO (Sample >1 Prim) if more than one.
  • Drop the [Black Tulip] Information Point ~config~ notecard in the Content tab of this primitive and edit it, filling in all the required information for your item. The details are covered in next section, THE CONFIGURATION NOTECARD.
  • Drop also the items you want to be delivered as information: notecard/s, landmark/s, picture/s, demo object/s...
    Check the provided [Black Tulip] Multi Door Tool INFO (Sample 1 Prim) sample object to compare if your information point is made of one prim, or [Black Tulip] Multi Door Tool INFO (Sample >1 Prim) if more than one.
  • If you have added an e-mail address in your notecard to receive the reports there, then add the [Black Tulip] Information Point e-mail submodule script.
  • Finally, add the [Black Tulip] Information Point script.

When all this is completed successfully, you'll see messages like the following in chat (only you will see them):

[04:40]  [Black Tulip] Staff Pager INFO: Reading notecard, please wait...
[04:40]  [Black Tulip] Staff Pager INFO: Information Point READY. 3 informations in folder to be delivered for item '[Black Tulip] Staff Pager'
[04:40]  [Black Tulip] Staff Pager INFO: Free memory: 34060 bytes.

The first message informs us of the script reading the configuration notecard. If it finds any error, it will notify you and will show text hover your information point primitive.

The second message informs us of how many items will be delivered if the user clicks the Item Info option.

Then finally, the third line shows the free memory for the script: once this happens, the script is READY to register all your users clicks.


THE CONFIGURATION NOTECARD


Do a copy of the [Black Tulip] Information Point ~config~ notecard to always keep a clean copy of this.

This notecard simply consists of several parameters that the [Black Tulip] Information Point script will use in order to give information to our customers, as well as parameters to set specifics for informing us when an user clicks an option.

Let's see all the parameters in one example:

# [Black Tulip] Information Point ~config~
# Lines beginning by # are ignored

customMsg = This is a custom message.\nIt can contain carriage returns and even\n\t\ttabulators\n(Check the doc for this)\nIt's a good idea if you add a link to your profile:\n\tsecondlife:///app/agent/766f3817-2f2a-469d-acfa-9789080ecc85/about
itemName = [Black Tulip] Multi-Door/Drawer/Curtain Tools
groupUUID = d076391d-eb7c-74d7-699c-3e2ddaa0f7d4
hoverText = 0
hoverTextColor = <1.0, 0.5, 0.0>
sendIM = 1
storeBlog = http://blacktulip-store.blogspot.com/
storeMP = https://marketplace.secondlife.com/stores/42594
storeMP_Item = https://marketplace.secondlife.com/p/Black-Tulip-Multi-DoorDrawerCurtain-Tools/2891315
merchantName = Auryn Beorn
storeName = Black Tulip
emailMerchant = auryn.beorn@gmail.com

customMsg
Here we type the message to show to our customers after they've chosen to receive an informative folder. If we leave it empty, the default message will be as follows:

[04:41]  [Black Tulip] Presenter INFO: Thank you for your interest in my products. For more information on them, don't hesitate contacting me (Auryn Beorn):
secondlife:///app/agent/766f3817-2f2a-469d-acfa-9789080ecc85/about

Of course, instead of Auryn Beorn and my UUID, it will appear what you've written for merchantName and your own UUID

SPECIAL CHARACTERS:
If we type \n as in the example notecard: A carriage return will be inserted instead
If we type \t as in the example notecard: A tabulator will be inserted instead

itemName
The name of our product. This will appear in the menu and other informative messages.

groupUUID
The UUID of our group. We can find this in the properties when opening the group window. When the user selects Group join", a message like the following shows:

[04:42]  [Black Tulip] Multi Door Tool INFO:
Click the following link to open the Group window and then click 'Join'.
    secondlife:///app/group/d076391d-eb7c-74d7-699c-3e2ddaa0f7d4/about
Thanks! Auryn Beorn.

Of course, instead of Auryn Beorn, it shows what you've written for merchanName.

hoverText
Do you want hover text displaying over your information point primitive? Set this to 1. You don't want hover text displaying over your information point once is set up? Then set this to 0.

hoverTextColor
If hoverText is set to 1, then this is the color for the hover text. This package includes the "[Black Tulip] Color HUD" tool for you easily writing a color correctly in this part. Click here for the documentation of the Color HUD tool.

sendIM
Set this to 0 if you don't want to receive any IM when an user clicks an information point to receive an informative folder.

If you wish to receive an IM like the following if an user decides to receive information:

[04:41]  [Black Tulip] Multi Door Tool INFO: [Information Point] '[Black Tulip] Multi Door Tool INFO'
The avatar 'Auryn Beorn' has clicked for information about '[Black Tulip] Multi-Door/Drawer/Curtain Tools' on 2012-02-11, 12:41:51. UTC
Click here for profile: secondlife:///app/agent/766f3817-2f2a-469d-acfa-9789080ecc85/about

then set this to 1. The link written in chat is clickable and will open the profile of our customer.

storeBlog
In here, we should write the link of our store website, if we have one.

storeMP
In here, we should write the link of our marketplace store, if we have one.

storeMP_Item
In here, we should write the link of the marketplace page of the product, if we have this item in Marketplace.

If we fill the three of them, when our customer clicks "Webpage", the information they'll obtain will be as follows:

[04:43]  [Black Tulip] Staff Pager INFO: 
You can check the following link to get this item in Marketplace (or to send it as a gift):
    https://marketplace.secondlife.com/p/Black-Tulip-Multiavatar-Staff-Pager/2075861
Please leave a review if you've liked it!
Click the following link to open the store web. Follow it and leave your comments if you're so inclined:
    http://blacktulip-store.blogspot.com/
Don't forget checking the Marketplace listing for more products like this one!
    https://marketplace.secondlife.com/stores/42594
Thanks! Auryn Beorn.

merchantName
Here we'll write our name as we wish it to appear in all the messages for the user.

storeName
Here we'll specify the name of our store.

emailMerchant
If we want the clicks report to be sent to a specific e-mail address, we will write it here. ONLY if we type in something for this parameter, we should include the [Black Tulip] Information Point e-mail submodule script.


If you have any problem with this script, please give a complete description of your issue in the following online form.

I'll get back to you after I have read your report and replicated your issue inworld, according to your description of it. Please, be detailed.

-- Auryn Beorn
Posted by at
Labels:
Subscribe to: Posts (Atom)