Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Wiki print out ??

Jonathan Morris
Registered User
Join date: 5 Jan 2006
Posts: 66
06-08-2006 11:31
I am starting scripting, as a dyslexic I need a list of commands to hand to check spelling, and notes on syntax...
I would like to print out the commands as a list, and a manual giving the use of all the commands.

Has anyone got an easy way to get a print out of the WIKI ?

Regards Jonathan
Artemis Cain
Take it or Leave it
Join date: 11 Apr 2005
Posts: 116
06-08-2006 11:43
If you go in to your Second Life folder on your computer... assuming default installation, it would be C:\Program Files\Second Life.

there is a copy of the LSL scripting guide right there.
Osgeld Barmy
Registered User
Join date: 22 Mar 2005
Posts: 3,336
06-08-2006 19:02
the scripting guide is about as useless as a visual output for the blind

in the past there was someone that had a HTML copy of the wiki so you could DL it, altho ive never heard anything about it since, so i would imagine its out of date

altho this "feat" can be done using internet explorer and the synchronize tool, infact i just did it last night, you still end up with a large wad of random, non oginized HTML pages, not cool if you intend to print it

I synced with it becuse ive been toying around with php, and thought a little in world pocket wiki doo-hicky would be handy(then it started getting late, im gonna fiddle with it tonight some) , but one thing that has and still is looming over my head ...

most of us are aware of the dropdown box, which contains all the functions, events,ect altho a pain in the butt becuase you have to scroll tru a 3 mile long list of stuff, its better than nothing (IMO it could use the same thing that the Sim selector now uses on the map)

another thing is the LSL editor window, if you imput the wrong stuff, functions wont turn red ect, and with the worst case you will have to debug your script, which you will probally have to do anyway heh

and the last "questionable conflict" with my project is the mouseover, if you put your mouse over any hard set functions in LSL it will bring up text, which is usually the same first cupple lines on the wiki about the said function

so theres a few options for all of us to check syntax, without killing a tree (heh like i care, thats why we have tree farms) constant alt-tabbing, working in a tiny window or whatever else :)
SuezanneC Blackflag
Registered User
Join date: 8 Jun 2006
Posts: 14
06-08-2006 20:19
There lsl_guide.html file mentioned above is adequate for use as a memory aid and reference guide for function and event names, constants, etc. It is not intended as a complete tutorial on scripting. It is a linear piece of text that can easily be printed, though you might want to edit it to suit you before printing it.

The entries in that for functions look like:

From: someone

A.44. llEdgeOfWorld

integer llEdgeOfWorld(vector pos, vector dir);

Returns TRUE if the line along dir from pos hits the edge of the world in the current simulator and returns FALSE if that edge crosses into another simulator.


There is another file, in C:\Program Files\SecondLife\app_settings, called keywords.ini that could, with a little editing, be a useful extremely concise "cheat sheet" for some things.

To use this file you would want to copy it it and use the copy. This is the file with the popup help for the LSL script editor, so you don't want to mess with the original.

It has event names, with parameter lists, etc. in a format like:

From: someone

state_entry state_entry():Triggered on any state transition and startup
state_exit state_exit():Triggered on any state transition
touch_start touch_start(integer num_detected):Triggered by the start of agent clicking on task
touch touch(integer num_detected):Triggered while agent is clicking on task
touch_end touch_end(integer num_detected):Triggered when agent stops clicking on task


A little editing - maybe bolding the keywords, double spacing after each description - and you'd have a fairly condensed, readable though incomplete LSL summary.