Weird bug, maybe after adding Automap

In my WIP, I notice that I longer get the ‘I don’t understand that verb’ error if I type nonsense. Instead I get error 18 (“the noun did not make sense in that context”).

I think the change comes from adding Automap, because even though I’ve changed a lot of other stuff at the same time – I’m now using many of Dannii’s revised versions extensions, Glulx Alternative Startup rules, etc. – I can include all of those in a vanilla project and not have the problem. It seems to happen when I then add the blob of Automap, Glimmr Automap, Glimmr Automap tileset. And these are all things I’ve further tweaked, because the only one that had really been updated for 6L02, even, was Mark Tilford’s Automap.

Before I think any further, I thought I’d paste a trace here and see if anyone can identify the culprit area.

The output of trace 3 of a nonsense command in a normal project looks like this:

Summary

gh

[ “gh” ? ]
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
That’s not a verb I recognise

Here’s what I’m seeing in my WIP:

Summary

[ “gh” ? ]
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
Parse_name called
Pass 1: 0 Pass 2: 0 Pass 3: 0
[Parsing for the verb ‘no.verb’ (1 lines)]
[line 0 * scope=Routine(1104038) → A181_dumping_imap]
[line 0 token 1 word 1 : scope=Routine(1104038)]
[Scope routine called at stage 1]
[Scope routine returned multiple-flag of 0]
[Object list from word 1]
[Calling NounDomain on location and actor]
[Scope routine called at stage 2]
[token resulted in failure with error type 18]
[“Rule for printing a parser error when the latest parser error is the noun did not make sense in that context error” applies.] …

Then it prints my custom error message.

I tried finding terms like ‘no.verb’ or ‘a181… imap’ in extensions or the I6 Designer manual, but could not.

Thanks

-Wade

The “no.verb” thing is a hack employed by I7 to make the parser understand sentences that don’t begin with a verb (such as when you write Understand "[something]" as examining).

A181_dumping_imap is the I6-level name the I7 compiler assigned to an action called “dumping imap”. This action seems to be defined in the extension “Glimmr Canvas-Based Drawing”, specifically here. The behaviour should go back to normal if you remove the or "[any image-map]" part of that understand instruction.

1 Like

Brilliant, thanks!

-Wade