Sadly that is exactly my case where it stopped responding. I thought it was your design goal! And I don't want to walk through the adventure again, especially after I jumped off the platforms twice.
Well I fixed it for the next person at least. It is still a bit laggier than it should be but it will no longer crash your browser. Thanks for playing!
^ this made some odd looking number folders. No idea which folder was in which folder, but, ok...
for(var i=0;i<2;i++) for(var j=0;j<2;j++) for (var k=0;k<2;k++) for (var l=0;l<2;l++) ls ${i}/${j}/${k}/${l}
This did nothing, so I'm not sure if you fixed it or just placed a cap on how much js you are executing... (should have at least shown 16 frames)
for(var i=0;i<8;i++) for(var j=0;j<8;j++) for (var k=0;k<8;k++) for (var l=0;l<8;l++) open ${i}/${j}/${k}/${l}
Is/was producing a nice log of things not opened...of course my browser tab is busy logging 6 GB+ of history (does your terminal have a scrollback limit?)
Cute game, maybe I'll try to open the box later after I get some sleep. Not sure what I would use the terminal for, though - is basically what you're trying to do an interactive scratchpad with history?
If that's the case, I would look into Jupyter e.g., I'm not sure I get the point otherwise.
I made it so that it short circuits the frame creation of if there aren't going to be any files to show in that directory.
I'm honestly not sure if the web sandbox I made has enough realism to solve that puzzle though programming. There is a feature of snail that I was using to get past it.
for(let i=0; i<=8; i++) for(let j=0; j<=8; j++) for(let k=0; k<=8; k++) for(let l=0; l<=8; l++) ls ${i}/${j}/${k}/${l}