llSetPayPrice

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

SetPayPrice

llSetPayPrice

Summary

1/2 Bugs

Function: llSetPayPrice( integer price, list quick_pay_buttons );

0.0	Forced Delay
10.0	Energy

Suggest default amounts for the pay text field and pay buttons of the appearing dialog when someone chooses to pay this object.

• integer	price	–	PAY_* constant or positive value (including zero)
• list	quick_pay_buttons	–	Four PAY_* constants and/or positive integer values (zero is not shown)

Constant Alt Description PAY_HIDE -1 0 Hides this quick pay button. PAY_DEFAULT -2 Use the default value for this quick pay button.

Button Order 1 2 3 4

Defaults $1 $5 $10 $20

Caveats

• This function should not be trusted to limit the values of money payable to the object; always verify the amount paid is the amount expected.
• Use only one call to this function in all the scripts on an object to prevent confusion about which values are used. You still need to check in the money event that the amount is as expected.
• This function only works when called from the root prim of an object. Its effect applies to all the prims in the object. Calling it from a child prim has no effect.
• Payment to a prim can be blocked by the llSetPayPrice() setting in the prim, which persists even if the script with llSetPayPrice() is removed.
• Note that the pay option will only be shown in prims having a running script with a money event (or in all the prims of the object if the root has a running script with a money event).
• The effect seems to persist even if the script is recompiled with out the llSetPayPrice function, even if the script is replaced with another one which includes a money event, but not llSetPayPrice.
• Money cannot be paid to an attachment; "Pay" will go directly to the wearer instead.
• If quick_pay_buttons contains a negative value or zero, the button will not be shown at all.
  • However, zero is allowed for price, which is used to set the custom text field's value within the Pay window.

Examples

This will give the user a dialog box without the price field and only one button with a value of 150.

llSetPayPrice(PAY_HIDE, [150,PAY_HIDE,PAY_HIDE,PAY_HIDE])

integer price = 10;

default
{
    state_entry()
    {
        llSetPayPrice(PAY_HIDE, [PAY_HIDE ,PAY_HIDE, PAY_HIDE, PAY_HIDE]);
        llRequestPermissions(llGetOwner(), PERMISSION_DEBIT);
    }
    run_time_permissions(integer perm)
    {
        if(perm & PERMISSION_DEBIT)
            state cash;
    }
}

state cash
{
    state_entry()
    {
        llSetPayPrice(price, [price ,PAY_HIDE, PAY_HIDE, PAY_HIDE]);
    }
    money(key id, integer amount)
    {
        if(amount != price)
        {
            llGiveMoney(id, amount);
            llInstantMessage(id, "You paid "+(string)amount+", which is the wrong price, the price is: "+(string)price);
        }
        else
        {
            //insert your give code here.
            llInstantMessage(id, "You paid the right price");
        }
    }
}

See Also

Events

•

money

Functions

•

llGiveMoney

Deep Notes

Tests

•

llSetPayPrice Test

Signature
function void llSetPayPrice( integer price, list quick_pay_buttons );