For the key use the hanger, but before that you will have to get rid of the guard Dennis (if you still have the flask). For the bikini, you will find the answer in the bedroom, but you need the key. For the coins given to the Ratherdashing guard, I had never tried it before, and maybe it's another bug.
It's a pity, it could have been a nice little game.
The barrel was the key. I had tried everything I could think of to clean the mold off the barrel and all I had to do was USE soap. I wish authors wouldn't use USE. It's a real cop-out. This game uses it a lot.
Anyway, once I had the big jerky, the rest of the game was a doddle. I've finished now.
P.S. Don't use the flask on Dennis, as you need it somewhere else.
There are default command handlers for GET, DROP, WEAR, REMOVE (these all support ALL), INVENTORY,SAVE, LOAD, WAIT and possibly a few others that I can't remember just at the moment. You can also use IT after any verb that expects a noun and it will use the noun from the previous command. For example, EXAMINE AXE, GET IT.
Adventuron may have a list of these somewhere, but I don't think they're properly documented.
You normally don't have to do anything. What happens behind the scenes is that if you use GET ALL, Adventuron identifies all the objects that are in scope (using is_beside) and attempts to get each of those objects. The action handler for each object is exactly the same as if you had typed them individually. I'd strongly recommend against overriding the default behaviour with :match "TAKE ALL", as this prevents you getting objects that you've dropped that don't have to be bought. If you're having trouble with GET ALL, there may be something wrong with the action handlers for the individual objects. You should check this first.
As an example of how this works in practice, go to the stationery store in 'Igor's Quest' and try GET ALL. You'll get separate messages for each of the objects that needs to be bought. The only downside is that if there is an object that can be taken, I think you get the auto_redescribe and the screen refreshes before you can read all the messages.
The only downside is that if there is an object that can be taken, I think you get the auto_redescribe and the screen refreshes before you can read all the messages.
This should not happen. If it doesh happen then I'd love to see a sample source code that demonstrates this.
The auto redescribe should only happen once per batch. A get all initiates a batch.
There are several solutions to puzzles that can get you into an unwinnable situation, but they all have alternative solutions. I think most (if not all) of these involve the flask. Strictly speaking, this is contrary to the jam rules, but, as a player, I'm prepared to turn a blind eye, as it has some nice puzzles. I just wish it didn't use USE to solve so many puzzles and had anticipated more actions.
