Hi Javier, thanks for sharing your project.
I had some trouble getting started. I downloaded your git repo, but your setup instructions shows me a directory listing.
python3 -m http.server
Directory listing for /
Typically for a git repo I would expect to find a package.json containing project metadata, including shortcuts to run whatever local dev scripts are needed.
I found this url in your README.md but got a browser error trying to view it in Firefox:
Loading module from “https://jason80.github.io/dragonfly/base/output.js” was blocked because of a disallowed MIME type (“text/html”).
I tried it in Safari, where it worked. It seems like your basic parsing works - I can x things, move around, that’s good.
I found some parser irregularities:
The leaves cover the ground, crunching under your feet as you walk.
> dig in leaves
> dig leaves
You don't know what you are saying.
>
You don't know what you are saying.
I got no response to “dig in leaves” and then double responses to “dig leaves”.
When I was trying to copy text to paste here for example, I found that the page is insisting on keeping focus on the text input, which prevents users from selecting text on the page. I understand why you’d want to keep focus on the input, so the user can always type, but that piece might benefit from a rethink - perhaps reset focus on keydown.
More parser irregularities. I got no response to “listen to creek” (or even “listen creek”).
To the south, you can hear the soft sound of a creek.
> listen to creek
>
I can’t examine the creek, I guess because it’s in the next room, though it is mentioned in this room.
> x creek
There is none of that.
I get no response to “enter log”.
An old hollow log lies near the creek, its bark weathered and dark.
> enter log
>
When no response is given, the parser provides a new input line out of order, and then there’s some irregularities about how the parser handles text following the next input. Here, “enter log” left me with a blank input line followed by “You don’t know what you are saying.” and then when I typed “look in log” the lockpick text followed.
You can't take the hollow log.
> enter log
> look in log
You don't know what you are saying.
Inside there is: a lockpick.
But I can’t take the lockpick.
I guess there’s a combination of things going on - some issues with the parser, some issues with the particular game file. It seems like the parser has no response to verbs it doesn’t know.
> take lockpick
There is none of that.
> hit log
> Nothing happens.
> Kick log.
>
Similarly, I can’t get into the cabin.
> enter cabin
>
You don't know what you are saying.
> go in cabin
>
> go cabin
>
>
> unlock cabin
>
It seems like a nice start, and I’m impressed that you’re working with multiple languages.