Opened 17 years ago
Closed 17 years ago
#3324 closed defect
GOB: unknown goblins 1 version
| Reported by: | SF/zjoker | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | Engine: Gob |
| Version: | Keywords: | detection | |
| Cc: | Game: | Gobliiins |
Description
scummvm 0.10 (Jun 17 2007 11:19:20) Features compiled in: Vorbis, FLAC, Mp3, zlib MPEG2
"Your game version appears to be unknown. Please report the following data to the scummvm team along with the game of the name you tried to add along with its version/language/etc:
"intro.stk" "26a9118c0770fa5ac93a9626761600b2", 233466 Gobliiins 1 Language version: Don't know but the load/save screen says "LOAD, QUIT" etc. so it seems to be english. It's a VGA Version of Gobliiins 1.
Ticket imported from: #1756448. Ticket imported from: bugs/3324.
Change History (7)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Summary: | unknown goblins 1 version → GOB: unknown goblins 1 version |
|---|
comment:3 by , 17 years ago
| Status: | new → pending |
|---|
comment:4 by , 17 years ago
This tracker item is pending response by the submitter; we cannot continue processing it before that happens. As a consequence, its status has been set to "Pending". It will automatically revert to "Open" once a new comment is made to this item. If no response is made within 14 days, it will automatically be closed.
Thank you.
comment:5 by , 17 years ago
Please readd the game configuration in ScummVM's launcher and retry, it should work - this version has been added from bug report #1201233. This issue might be occuring if you upgraded from an older version of ScummVM - you need to readd the game's configuration again to have your game working again
comment:6 by , 17 years ago
| Status: | pending → closed |
|---|
comment:7 by , 17 years ago
This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker).
I see this MD5 occurring in the current source, maybe it was added after the 0.10.0 release. Could you try with a current daily build to confirm?