Basics

The only group that isn’t about an instruction. This is the language as a whole: how the processor counts time, what kinds of values there are, where link names come from.

You don’t have to read it front to back — lessons in the other groups link here themselves whenever they need something from it.

Lessons

1. Writing it in the gameWhere the program lives, what a line is made of and what the buttons around it do
2. A program is textAssembled from blocks, stored as lines — and that is worth using
3. The variables windowThe only place that tells the truth about what the program has computed
4. How the processor worksThe program runs top to bottom and starts over. Lines count from zero, speed is measured in instructions per tick
5. Number, object and textA variable holds either a number or an object — and what you can do with it follows from that
6. Emptiness: nullThere is no value — and that is a value too. The main source of silent mistakes in mlog
7. Variables and namesA variable isn't declared — it's just named. Which names are free, and which are already taken
8. Links and getlinkA link is not adjacency: a block has to be connected, and only then does it get a name
9. When it does not workmlog reports no errors. So you have to look yourself — and there is an order in which it is done