reproducible Zork crash - Run-time error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Beginning of game, enter house, enter living room, move rug, open trap door
2. Type "walk into trap door"
3. Trying many commands, but can't go down stairs through trap door

What is the expected output or behavior?  What do you see instead?
** Run-time error: Living Room (object number 83) has
no property <number 0> to read **
     Halt! Excavation in Progress!
  Frobozz Magic Implementation Company
I see nothing special about the trap door

What version of Frotz are you using?
1.0.1

What version of iPhone/iPod Touch OS? (2.0, 2.0.1, 2.0.2)
3g iPhone v2.0.2
Please provide any additional information below.

Original issue reported on code.google.com by andrew....@gmail.com on 6 Sep 2008 at 12:35

[GoogleCodeExporter]

Huh. I could not reproduce this - assuming you mean Zork I. When I entered 
"walk into trap door" (after entering 
the living room and moving the rug, of course), the response was: "You should 
supply a direction!". When I 
entered "down" I went down into the dungeon.

This is on an iPod Touch v2.0.2 (5C1), 32 GB RAM.

Original comment by joelsanda on 6 Sep 2008 at 2:41

[GoogleCodeExporter]

Interesting. Mine is stuck in this state. I will have to try clearing the game 
data
and starting over.

There were other commands that would do the same thing. All errors are the same 
or
simlar and seem to be about missing data in the Living Room.

Original comment by andrew....@gmail.com on 6 Sep 2008 at 3:18

[GoogleCodeExporter]

I started a new game and get the same issue, but I can get it in different 
places
with the same command. Almost like the parser is trying to use the word "into" 
and
actually treat the item like a container.

From inside the cellar, trying to "walk into trap door" gives me the same error 
but
references a different object number: Cellar (object number 109)

I guess I can try a real reboot and see what happens.

Original comment by andrew....@gmail.com on 7 Sep 2008 at 8:23

[GoogleCodeExporter]

This is not a bug in Frotz itself but a bug in the Zork (MIT version Inform 
port) story file, which is several years 
old and is not likely to be updated.
The workaround is simply "Don't do that."
The bug fix would be merely to get rid of the error and replace it with 
something like "You should supply a 
direction" like Zork I (Infocom original) prints.
The Zork simply don't understand the language "walk into" or "walk through"  
Other more modern stories 
generally do accept this.

Original comment by spath...@gmail.com on 9 Sep 2008 at 7:58

• Changed state: WontFix

[GoogleCodeExporter]

Thanks,

I thought it was more an error in Zork interpreter and not Frotz, but I thought 
i
would post just in case. 

Original comment by andrew....@gmail.com on 17 Sep 2008 at 9:54