18 June 2016
|Type||Corrade progressive command|
|Last Changes||Release 9.92 - added.|
Be aware that by sending a
secret you are revealing your account credentials to the machine that is running Corrade. On the other hand, Corrade only uses HTTPs encrypted requests such that once the data gets to Corrade it will be safely used to interact with the Second Life website. Nevertheless, be weary about using this command in case you are not the sole person with access to the Corrade machine and if you care about your account possibly being compromised.
addevent command can be used to schedule an event in Second Life - it will only work in Second Life.
|Command||Required Parameters||Required Corrade Permissions||Example|
| || || ||
llInstantMessage(CORRADE, wasKeyValueEncode( [ // Schedule a new event in Second Life // by providing all the necessary parameters. "command", "addevent", "group", wasURLEscape(GROUP), "password", wasURLEscape(PASSWORD), // The account firstname. "firstname", "Moka", // The account lastname. "lastname", "Dumbledore", // The account password. "secret", "dumb3r", // The event name. "name", "Corrade LSL Test Modified", // The event description. "description", "Corrade LSL Test Modified - delete me!", // The time of the event (from geteventformdata command). "time", "22:00:00", // The duration of the event (from geteventformdata command). "duration", "10", // The category of the event (from geteventformdata command). "category", "18", // A date - in any standard Gregorian date notation. "date", "06/19/2016", // The location of the event (from geteventformdata command). "location", "1020,995,0,0,0,d436261b-7186-42a6-dcd3-b80c1bcafaa4", // Send the event identifier to the following URL "callback", wasURLEscape(URL) ] ) );
| ||A string.|| The password of the account that Corrade is currently connected on or the password of the account specified by
| ||A string.||The name of the event.|
| ||A string.||The description of the event.|
| ||A valid Gregorian calendar formatted time (date is ignored).||The time when the event will take place.|
| ||An integer representing a valid value returned by the geteventformdata command.||The duration of the event.|
| ||An integer representing a valid value returned by the geteventformdata command.||The category of the event.|
| ||A valid Gregorian calendar formatted date (time is ignored).||The date when the event will take place.|
| ||A valid location returned by the geteventformdata command.||The location where the event will take place.|
|Optional Parameter||Possible Value||Meaning|
| ||The first name of an account.||By sending a first name and a last name Corrade will instead query the account transaction data for that account instead of the current account that Corrade is connecting on.|
| ||The last name of an account.|
addevent takes as parameter a bunch of parameters that are all required in order to submit an event to Second Life. The parameters:
are all up to the calling script. However, the parameters:
are in the Linden Lab format and can be retrieved with the geteventformdata command.
In other words, if you wanted to schedule an event, you would first use
geteventformdata in order to query the possible values for the
location parameters necessary to the
addevent command. You do not have to use the
geteventformdata command every time you need to schedule an event though since these parameters represent the built-in values for drop-down boxes on the Second Life event submission page which do not change often.
addevent command, if successful, will return via the callback a
data key with the value set to the numerical event identifier - which can then be used together with the deleteevent command or the modifyevent command in order to delete, respectively modify the event. In case you may like to delete or modify an event before it takes place, it is imperative that you store this numerical identifier - otherwise, you will not be able to modify the event anymore.