Oh..ok..but I looked in a brick .zip file and found .blb files..what are these and what do I do with them?
Well, that's your starting point. Everyone that wants to learn how to make Bricks or scripts or anything at all needs to know how to tackle a set of Problems, so you'll need to learn some Problem Solving skills
How to solve a problem0- Observe: Try to gather up info on the subject and/or study the script. There is no tutorial so all you can do is look at the script and think on it.
1- Speculation: Try to guess what the answer to something is. Use your brain and try to piece everything you know in a manner that makes logical sense.
2- Test it out: Go into the script and change something corresponding to your idea. Then go in-game and see what happens. Keep track of all your changes! And most importantly
Don't forget to make a backup of all the scripts you will be performing tests with!!You can keep track of changes within a script by making Comments. In .blbs it's a bit more iffy where you can and cannot place comments, but generally you can make comments anywhere by starting it with // and just writing things after. These Comments are ignored by the engine.
3- Compare: What changed in this script before and after the test? And what does this mean for your Idea or theory of how it works? This step can have 1 of 3 outcomes.
4a- Your Idea is wrong: You got a result that's completely different from what you were expecting. Now you need to make up a new Idea that works for this observation and further test it, so you go back to step 1
4b- Your Idea is right: Being smart or just very lucky, everything worked as you expected. Now you can move on to another subject or go further still in this current subject.
4c- Now nothing works at all: Well this will happen, and do NOT be scared of it happening. Your script simply does not work after you changed it. Fortunately you know what you changed, and furthermore you have a Backup waiting somewhere that you can compare your changed version with. Finally you have the Console chucking error reports at you. So from here you go back to step 1 but now the question is
Why did it break? Not only is it very possible to fix the problem yourself, but you are likely to learn a ton of things by fixing it!The process is repeatable and cyclic. It's very easy and works almost naturally, go try it out.
Note: If you run into a snag (like in step 4c), do NOT ask for help.
You are likely to learn 10 times more AND retain the answer by solving the problem yourself instead of asking for help.
