No worries, your feedback is appreciated! (although it’s definitely nice to know you like it too 
)
Yes, a return statement could make sense. Right now you only have the natural indented block structure to control where the flow is going inside a beat indeed. It should not be difficult to add and would add more flexibility.
I’m interested to know any other pain points you are having relative to Ink, even if that’s not a blocker. These can really help shape the next round of updates to the language!
Right now there is not a full per-target API documentation. I’d like to have that, but first I need to figure out a smart enough way to maintain it properly given the many targets Loreline supports, so for the time being there are only the integration guides and the example projects that come with it.
Regarding reading and writing states, you can use interpreter.getStateField() and interpreter.setStateField() (or the snake_case equivalent on languages that use snake case like python).
If there is a specific thing you’d like to do but don’t know how to do it with Loreline, you can also ping me. There are things that are not properly documented but I can point to the right direction!