Opened 17 years ago
Closed 2 years ago
#3493 closed defect (fixed)
SCUMM: Dig - Rat Trap Puzzle Error
Reported by: | SF/mthreepwood | Owned by: | AndywinXp |
---|---|---|---|
Priority: | normal | Component: | Engine: SCUMM |
Version: | Keywords: | ||
Cc: | Game: | The Dig |
Description
Win32 (WinXP SP2) 0.11.0svn (December 9, 2007) The Dig (Windows/English)
At the rat trap puzzle, after I set it up (the dowel, hook, cage, and rod), I accidentally hit the hook. It duplicated the image of the hook, and set the trap, trapping an invisible rat. Low even says his lines that the rat is trapped. I am still able to put the bracelet on the rat and let him loose (ie it does not hinder the game). Once released, the duplicate hook image disappears.
Screenshot attached, no saved game yet (sorry, didn't save before, will upload one later).
Ticket imported from: #1847454. Ticket imported from: bugs/3493.
Attachments (3)
Change History (12)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Aye, that was my guess too.
Er... *now* here's the screenshot.
Also, I have a saved game, but I can't reproduce it exactly. Still, it did occur. File Added: RatTrapError.PNG
comment:4 by , 16 years ago
Priority: | normal → high |
---|
comment:6 by , 12 years ago
Priority: | high → normal |
---|
by , 10 years ago
comment:7 by , 10 years ago
It took seven years, but I finally reproduced the bug.
dig.s07 is right before it happened, dig.s08 is right after. The glitch is still present in dig.s08.
From save 7, I had dug the tunnel to make it wider, went in, came out, and walked to the right without the rat being there. The trap animation just triggered and the glitch appeared.
comment:8 by , 4 years ago
Summary: | DIG: Rat Trap Puzzle Error → SCUMM: Dig - Rat Trap Puzzle Error |
---|
comment:10 by , 2 years ago
Owner: | set to |
---|---|
Resolution: | → fixed |
Status: | new → closed |
It seems nobody else was able to replicate this, so this might have been fixed as a side effect of some SCUMM v7 accuracy fixes. Closing this!
This sounds like a script bug might be at hand...