Hey, no need to apologise. I'm just wearing my tester's hat and trying to help you improve your game so that other players (and judges) will enjoy it more .
Re CREDITS, I meant that you could write something a little more user friendly and specific to your game. Don't just rely on the system credits. See mine (ABOUT, CREDITS or INFO) as an example. I used stagger to account for mobile, as this is the only command that provides a long response. (A long response for credits is allowed in the jam rules.)
Re quotes, the natural response is for your eyes to move down to the next line immediately after entering a command. I found it a bit jarring when there was nothing there, but your peripheral vision indicates there's something to the right, so your eyes move to the right. (This is a human factors engineering thing. You might not have noticed it yourself, as you knew what to expect. The staggered display on text messaging is quite different, as the two conversations overlap quite a lot and the eyes don't have to travel as far on the small screen of a mobile phone.) If you want the quoted text to look different, you could use a different colour. Anyway, this was just an observation of something I found quite annoying. It's entirely up to you whether you change it or not.
Re leaves, you're right. That was fixed in 0.1.0. Either I was mistaken or I'd noted it in an earlier version.
Re disambiguation menu, if you have two objects with object IDs of red_key and blue_key and both objects are in scope at the same time and you try to (say) EXAMINE KEY or GET KEY, then Adventuron will automatically provide the disambiguation menu for you. You don't have to do anything special other than ensure that the object IDs include the appropriate adjective. Better disambiguation techniques are now available I believe, but I haven't used them yet. You can avoid the disambiguation menu with two-word input by allowing the player to refer to the adjective, e.g. EXAMINE RED, GET BLUE. You just need to account for this in your tests, especially match statements. The code can get a bit messy, so test thoroughly.
Re the Okapi issue, I think it's the ask_string that's causing the problem. I noticed this in a couple of games. What happens is if you use ask_string, it asks you a question and you are expected to answer that question. If you don't realise you have to answer the question and just play on, it can get in a real mess. I thought it was a rhetorical question and pressed the up arrow to repeat the previous command. (I had got into the habbit of doing this a lot in your game to see whether responses were consistent or random.) When you press the up arrow when Adventuron is expecting an answer to an ask_string question, it does NOT repeat the previous command. A similar thing happens if you don't answer with a number after a disambiguation menu. Adam Sommerfield just demonstrated this quite unknowingly in his review of 'Opposite Edge of Slumber' on YouTube. He had to terminate the playing session because he thought he'd crashed the game.
Thanks for doing all the updates. I'm sure it will be a lot better now. Will I be able to find that last treasure now?