In general, there is loads of channels and forums around where people are happy to help if you have at least tried to look at the LSL Wiki and searched on the forum here for a solution to your problem. Here is some good tricks I use for looking stuff up and debugging.
- Use the Search tools here - they also come in advanced flavor which can be powerful.
- On the LSL Wiki there is also a search function but they also have various ways of quick linking to the things you want. Try exploring that for bit to get a feel of how things are grouped and you will noticed almost everything is accessible by 2 clicks.
- The LSL Wiki has a index file if searching doesn't get what you wanted - its in the upper left bar.
- The LSL Wiki is slow - at least for Europeans like me its on the edge of awful and it gets even worse if your on a public wireless area like work or campus. I've downloaded the major parts of it to a offline version I can also use while on the move. I Use "HTTrack Website Copier" and used the index file as the source. BUT - be aware the the hole idea of wikies is that they are updated and with stuff like LSL you offend find some function is working again or [more often] stops working with the newest SL client.
- The SL Client before compiling your LSL doesn't debug near as well as the offline LSL scripting, debug and run tools like "LSLEditor". I can't name how many times I tried some really advanced code that didn't function even thought looking up potential trouble makers on the LSL Wiki to see if anyone had experienced problems or limitations. Only to copy it into LSLEditor and find out there is like 20 errors be course I wrote the code when I was sleepy and assigned integers with "==" and what not SL Client will not complain about.
- Practice listing down features and menu structures of advanced code beforehand. Also writing codeish terms on everything you want to do and looking up if the wheel is already invented so to speak - LSL has some really powerful predefined functions.
- Using a offline editor also has other features besides better debugging. Like real programming project solutions they have auto finishing so you don't have to write up the entire lllisten function each time. Also the description features can help you a long way to get rid of using the Wiki. This speeds up my coding a lot.
- Use staged development of code. Don't start with functions or what not you don't know work for sure if you haven't tested the genetic code. Instead use beta versions of the code that you save at different stages that are tested. Also develop a pure working version of the critical features before running off with neat solutions that might be a bit better but take ages to develop and test.
- When you see a neat feature or get a good idea for something - remember they might be useful later too. Make a habit of starting a library of functions and name them so you can quickly via copy-paste stick together code. Also make it genetic script that have included key features that you always can use in your scripts - like security lldie code or your name and license features for open source code.
More later when I remember them.