Updated Introduction to Editor Scripting.md (markdown)
commited
commit
a5c1fda5c4219bf4748a57370e478af6b26882ab
| ... | ... | @@ -11,7 +11,7 @@ So let's look at our first example. |
| 11 | 11 | setBlock(x, y, z, prefabIndex); |
| 12 | 12 | ``` |
| 13 | 13 | We can ignore the first line, since it begins with `//`. This makes the editor ignore any code in the current line, but it can give us some hints on what the following line does.\\ |
| 14 | The second line starts with the function `setBlock`. You can imagine this as placing a script block with the aforementioned name. A list of these functions can be found in the [examples](/wiki/fancade-web#editor-scripting). The following text represents the inputs given to this function, separated by `,` and enclosed by brackets. So to put this in [[visual scripting]] therms, we are placing a block called `setBlock` and give it the inputs `x`, `y`, `z` and `prefabIndex`. |
|
| 14 | The second line starts with the function `setBlock`. You can imagine this as placing a script block with the aforementioned name. A list of these functions can be found in the [examples](/wiki/fancade-web#editor-scripting). The following text represents the inputs given to this function, separated by `,` and enclosed by brackets. So to put this in [[visual scripting]] terms, we are placing a block called `setBlock` and give it the inputs `x`, `y`, `z` and `prefabIndex`. |
|
| 15 | 15 | |
| 16 | 16 | But those inputs were actually just placeholders, so let's replace them with some actual values! |
| 17 | 17 | ```js |