> Verse uses logic as the type for Boolean values, which means logic only has two possible values: true and false.
(<a href="https://dev.epicgames.com/documentation/en-us/uefn/logic-in-verse" rel="nofollow">https://dev.epicgames.com/documentation/en-us/uefn/logic-in-...</a>)<p>why in the world would you do that? even going out of your way to _call it boolean_ in the description, and then :fu: in the actual language<p>> indented comment: Anything that appears on new lines after <#> and is indented four spaces over is part of the code comment. The first line that isn’t indented four spaces over is not part of the code comment and ends the code comment.<p>Interesting. I see later on that code blocks also tolerate Python-ish syntax <a href="https://dev.epicgames.com/documentation/en-us/uefn/code-blocks-in-verse#spacedformat" rel="nofollow">https://dev.epicgames.com/documentation/en-us/uefn/code-bloc...</a> but _also_ brace syntax
Wow they were really serious about trying to make this approachable for beginners, cat sketches and all. And what better way to test that method than to release it to fortnite fans and seeing where/if they hit a wall.
That's funny: while there was clearly some work done on the website, it is very bad: on my phone there's no simple way to go from one section to the next!
I didn’t mind blueprints for things like animations or shaders but when building actual logic my programmer bias still preferred to write code. I’d be interested to see how this develops and if it supplants blueprints.
it seems <a href="https://news.ycombinator.com/item?id=35270720" rel="nofollow">https://news.ycombinator.com/item?id=35270720</a> has won out and I don't have the energy to email hn@ about merging the threads