SQ5 preliminary decompiled source

[MusicallyInspired]

Well yeah, but these were only for the priority and control colours weren't they? There's only 16 of them even in SCI1+.

[Collector]

Maybe not SCI specifically, but I was talking generally.

[troflip]

For code clarity it's probably best to use a define to name the colors specific to what they do in that particular file.

e.g.

Code: [Select]

(define ctlSpringTrap $0004)
(define ctlDoorOpen $0008)


[lskovlun]

What happens is that these go into an ordered list. If frog is substituted for cables, then it will indeed come before restOfPod. What I was doing was I added it manually by calling frog::init from the ScummVM debugger, in which case frog goes in last. In that case, restOfPod must be removed for things to work.

The reasoning here is wrong, by the way. The entries in the list are prioritized by y coordinate (see the class OnMeAndLowY) if the cursor could be within several rectangles at once. The fix is as stated: Put frog in the list, remove restOfPod.

[Cloudee1]

Thanks for that reference Lars, I just spent some time trying to get a click on a feature to take precedence over the click on a view where the two overlapped.

Tried rearranging the order in which it was inited, with no change... and then I remembered that you had posted this.

Threw in a quick y value that was greater (visually lower) than the y property of the view and voila.

[troflip]

Probably a good thing to note in the "interactions" tutorial

[NewRisingSun]

However, apparently in NRS's SQ4 patch he re-enabled the "Time-O-Matic" which is attached to the frog instance. But I can't get it to work...care to take a look at his script with your decompiler?

However, I discovered that his patch does not include the Time-O-Matic time warp after all, it was another script written by someone called the "Time Pod Debug patch" available on the archived SQ.Net website.

My patch does include it, but it is disabled by default. To enable my additional debug features, create a file named "DEBUG.FLG" in the game's directory, and start a new game.

It's difficult to change the length of a script if you're just directly editing bytecode, so it makes sense that he had to "replace" one object with another.

For that patch, I was not editing bytecode, but disassembling and reassembling with the ability to change script lengths. Remember that the "room of deleted items" (room 271) had no script at all so I had to write one from scratch, and I could not have done that by directly hacking bytecode into a hex editor.

[MusicallyInspired]

Ah, thank you. And welcome!