Surprising lack of scripters!

Not everybody wants to work on their car. They might be perfectly capable of learning the procedures and understanding the concepts, but they just aren't interested. Other folks love understanding what makes them work, and the satisfaction of doing it themselves. Likewise, not everybody wants to be bothered being a programmer, and not every SLer is going to show an interest in scripting.

So, is there actually a problem here, or just an observation?

That said, and not spending much time in-world recently, is there a need for more Q&A and tutorial sessions on scripting?

I've been trying to learn LSL for over 2 years now, and its only been a hassle to me.

The reason why is such a hassle: How do I know when I can push the limits and put together a rather complex system? How do I know if something isn't working right, is it a bug? or is it a flaw in LSL or is it something I'm not doing right?

The fact of the matter is, I find a lot of visual learners (like myself) want to know, what each function does visually so you can tell the result. Not having a reference point, and having to do everything by scratch not knowing that the hell you're doing, is quite frustrating and many people don't have the time or energy to get involved in learning it.

If I had a set of functions, and visually shown what each does, (invisable or visable), for those wanting to learn it (like me) would have a better time and picking up LSL.

But right now, alls it reminds me of is a blank notepad that you put togther like basic html can be done on a notepad.

Yes! The "picture is worth 1000 words" saying is true for me.
As I (probably) mentioned earlier in this thread, I often have to draw a picture or chart to determine how something works (or will work).

For visual learners, the only real answer is to attend a class or get an experienced scripter (like me) to help you one-on-one. It's really easier to show you the bounds of certain functions that way.

As for "How do I know if LSL screwed up or I did," roughly 99 times out of 100, it's you that screwed up. While LSL has plenty of bugs and annoyances to fix, most of these fall into the realm of obvious once you have a good debugging rhythm going.


The easiest ways to find bugs are:

1) Comment out code and try again
2) Turn on llOwnerSay for a certain variable at points in the code
3) Check the function's page on the Wiki


Simple enough, yes?