Difference between revisions of "TsAGE/TODO"

Jump to navigation Jump to search
319 bytes removed ,  05:35, 22 May 2011
The scene 2100 assertion has been fixed by Strangerke.
(Added another piece to the scene 4150 glitch.)
(The scene 2100 assertion has been fixed by Strangerke.)
Line 21: Line 21:
Known hardcoded logic bugs in CD version:
Known hardcoded logic bugs in CD version:
*Scene 2320: If you try to activate the flycycle, it will appear but Quinn will say "Too bad you don't have time to take it out for a spin right now." and then the game becomes unresponsive. I'm guessing that there is a missing call to enableAction(), possibly in Action1::signal() or Action4::signal() since both those functions are being called a couple of times during the animation.
*Scene 2320: If you try to activate the flycycle, it will appear but Quinn will say "Too bad you don't have time to take it out for a spin right now." and then the game becomes unresponsive. I'm guessing that there is a missing call to enableAction(), possibly in Action1::signal() or Action4::signal() since both those functions are being called a couple of times during the animation.
*Scene 2100: Examining the middle console triggers an assertion: "./engines/tsage/globals.h:84: bool tSage::Globals::getFlag(int) const: Assertion `(flagNum > 0) && (flagNum < 256)' failed." This is because Scene2100::Hotspot14::doAction() calls _globals->getFlag(0), which will of course always trigger the assertion.
*Scene 4150: Using the duck produces the message, "You don't need to use your stunner, the fire is sufficient for heating their meal." which seems a bit out of place. Conversely, trying to stun the duck produces the message, "You don't need to steal their next meal."
*Scene 4150: Using the duck produces the message, "You don't need to use your stunner, the fire is sufficient for heating their meal." which seems a bit out of place. Conversely, trying to stun the duck produces the message, "You don't need to steal their next meal."


415

edits

Navigation menu