Julian Laubstein

I would really like to see this project and especially the interpreter to grow and mature to a moment when it able to be embedded into other projects.

You should also be able to hide the handle if you're only using one instance.

You could switch it for a regular button though

IMHO it doesn't even have to be the domain on which coolify is installed. There should just be a setting named "Wildcard domain" or something. On setting it, the wildcard...

I would like to tackle this issue

I'm currently a little overflown with work, so I didn't really move along with this. I'm really sorry. I would like to take some time on the weekend to implement...

This could go even further: The project could crowdsource the explanations for each move and open up the database to well informed users. That way listudy could get actual explanations...

There are plans, but it is quite difficult to implement since there is no documentation about how the texturepacks are send to the client

Having a hook like `hooks/initialize.server.js` and `hooks/initialize.client.js` would be extremely useful for injecting code to run "on boot". Many ORMs like TypeORM and MicroORM depend on you being able to...

So this should be documented then, right?