Opened 9 months ago

Closed 8 months ago

Last modified 7 months ago

#12338 closed defect (fixed)

AGS: Quest for Glory II Remake: Cheats (Debug and Battle modes) not working

Reported by: OmerMor Owned by: dreammaster
Priority: normal Component: Engine: AGS
Version: Keywords:
Cc: Game: Quest for Glory 2

Description

Quest for Glory II Remake has 2 unlockable cheats: Debug Mode and Battle Mode.
You can read here for more information: https://tcrf.net/Quest_for_Glory_II:_Trial_by_Fire_(2008)

To unlock these modes, you need to extract the 2 files in the attached zip file to the game's directory.

When you start the game with these files present you get the following indications:

  • Qfg2vga.010 does a frog sound when you start the game.
  • Qfg2vga.011 does a sword sound when you start the game.

This means the game detects these files.

However, pressing F10 to start the Debug Mode or F4 to start the Battle Mode has no effect.

Attachments (1)

QFG2VGA Blue Frog Files-20210321T225106Z-001.zip (564 bytes ) - added by OmerMor 9 months ago.

Download all attachments as: .zip

Change History (7)

comment:1 by OmerMor, 9 months ago

Component: --Unset--Engine: AGS
Game: Quest for Glory 2

comment:2 by dreammaster, 9 months ago

According to the page you linked to: "Note that neither of these will work if you launch the game through a newer Adventure Game Studio acwin.exe, as the game's built-in one stopped at v3.2.". So we'd need to figure out what changed between 3.2 and 3.5 that's preventing the cheat from working, and introduce a workaround, just for QFG2.

comment:3 by OmerMor, 9 months ago

Yes - I saw that.

I don't know which AGS version the game is currently shipped with (only that it's v3), but the cheats still work with it.

comment:4 by dreammaster, 8 months ago

Owner: set to dreammaster
Resolution: fixed
Status: newclosed

With the latest workaround commit, both cheats now work.

comment:5 by OmerMor, 8 months ago

Thank you!

comment:6 by dreammaster, 7 months ago

Fixed in commits 879a06fabfb48f70ed5693ee1ceb8f88fa683c3e and 5650217194a7fc836ae8f3fe42cb72e27b6db9a0, though we later backported the more permanent fix from upstream.

Note: See TracTickets for help on using tickets.