86
edits
Difference between revisions of "SCI/Debug Modes"
→Script Debugger: + notes
(removed leading spaces) |
(→Script Debugger: + notes) |
||
| Line 169: | Line 169: | ||
When the script debugger is activated, the following general commands are available: | When the script debugger is activated, the following general commands are available: | ||
[CTRL + left mouse click] - Instant movement (of ego) | [CTRL + left mouse click] - Instant movement (of ego) <ref>Does not work with Quest for Glory / Hero's Quest</ref> | ||
[SHIFT + left mouse click] - Show coordinates | [SHIFT + left mouse click] - Show coordinates | ||
<references/> | |||
===== Game specific: King's Quest 4 ===== | ===== Game specific: King's Quest 4 ===== | ||
| Line 247: | Line 247: | ||
[ALT + D] - Internal debug mode | [ALT + D] - Internal debug mode | ||
[ALT + F] - Internal debug will pop up when entering a new room | [ALT + F] - Internal debug will pop up when entering a new room | ||
[ALT + G] - Room tester | [ALT + G] - Room tester <ref>Before this will work, you'll have to place the SCI picture resource of the room you want to test in the game directory and rename it to "PIC.999". That specific picture/room will be shown and can be tested in the game.</ref> | ||
[ALT + C] - Show control lines | [ALT + C] - Show control lines | ||
[ALT + V] - Show visual screen | [ALT + V] - Show visual screen | ||
[ALT + M] - Show memory | [ALT + M] - Show memory | ||
Also, the self-running demo of LSL3 has the same debug mode, apart from a room-selector on the beginning. It can be activated by extracting SCRIPT.000 from the RESOURCE files (the easiest way being SCI DECODER v1.0) and in addition changing the byte at offset 0x00000064 to "00" (instead of the original "01"). Beware that it's not really worth it, since it's pretty much the same deal and lots of missing resources cause it to crash easily. | |||
<references/> | |||
===== Game specific: Mixed-up Mother Goose ===== | ===== Game specific: Mixed-up Mother Goose ===== | ||