Messages

1

The Games and other Sierra Adventure stuff / Re: Quest for Glory 1 - Restoring Glory Project

« on: September 06, 2020, 09:33:04 PM »

No, thank you!  I did think of another thing.  It may be a stylistic decision, though.  Giving all of your money to the thieves in the alleyway results in a point loss in the EGA 1.0 version.  This penalty was removed in VGA.

Give me time... I'll probably think of more. 

EDIT: Looking at the code, it seems like the penalty is in the code, but for whatever reason it isn't firing.

2

The Games and other Sierra Adventure stuff / Re: Quest for Glory 1 - Restoring Glory Project

« on: September 02, 2020, 11:11:43 AM »

This is just so great; something good in 2020.

One thing the VGA is missing is a few places where time-skips can happen.  For example, getting thrown out of the bar advances time significantly in EGA, but does nothing in VGA.  Also, you can "nap" or "sleep" at the barracks in EGA and it advances time to night.

3

SCI Syntax Help / Re: Memory Fragmentation in QFG2

« on: November 02, 2017, 09:53:17 AM »

MemoryInfo 1 is the free heap.  MemoryInfo 0 is the largest ptr.  I don't understand what u> is, so I don't know what kind of comparison it's looking for.

I don't know how to use 'f' to get to the debugger.  The only debug mode I can seem to access is the one you get by typing "Suck Blue Frog".

That's actually how to start it.  "suck blue frog" and then <ALT+F> to give the memory information.

I tried jumping to the end to create a save file, however it doesn't load the save file properly, so I'm out of luck on that account.

Bah.  Emulators. 

4

SCI Syntax Help / Memory Fragmentation in QFG2

« on: October 26, 2017, 11:11:13 PM »

Hey all.

I'm a speedrunner of the Quest for Glory series.  Right now, I'm helping to work on a tool-assisted speedrun of QFG2.  We worked already on a speedrun of the first game , and as we were finishing the second game, we're running into a fragmentation error at the literal (not figurative) worst possible spot in the run: the final screen transition after killing the final enemy.

In a normal playthrough, this isn't a problem.  In a TAS, it's a frustrating problem.  While we can look through the code, we're both very ignorant of memory and the SCI engine.  Is there anyone who can help us understand what's going on and how to avoid this?