How to properly translate script files of LSL5?

[miracle.flame]

It worked! Script compiled without errors and saving works as it should.
Thanks a lot doomlazer!

[doomlazer]

You're welcome!

I've gone ahead and finished the other files that failed to decompile 100% (with two exceptions).

The following are now assembly free and formatted to work with SCICompanion's decompile:

rm258.sc (#258)
rm380.sc (#380)
rm700.sc (#700)
SRDialog.sc (#990)
game.sc (#994)
InvI.sc (#995)
obj.sc (#999)


The following are not fully decompiled:

sysLogger.sc (#952) - This script was used internally by Sierra's QA department to submit bugs to the devs. Unless you are trying to restore debugging for your translation, it can be safely ignored. If you really wanted, I could remove the ASM for this script as well.

RTRandCycle (#928) - This is a strange one. There are no string literals in this script that you will need to translate so it can be ignored. However, the reason it failed to decompile is because of this line:

Code: [Select]

(mouth setCycle: Unknown_Class_40 temp0)
If we look at the Sierra source code, it should be this:

Code: [Select]

...(mouth setCycle: MouthSync theAudio)...
MouthSync, in the Sierra source code, is defined in sync.sc (Script #929), but script 929 doesn't seem to exist in the LSL5 resource files at all!

Depending on how you're distributing, you might want to export a 928.sc patch from an unmodified LSL5 and import that into your project. Then Rebuild Resources and delete ./scr/RTRandCycle.sc & ./scr/RTRandCycle.sco. That should get the original bytecode back into the game's resource files.


Let me know if you have any trouble recompiling the files, all of which are included in the the zip attached below!

edit: removed bad attachment

[miracle.flame]

I've tried and the errors are:

[doomlazer]

Sorry about that. Those should now be fixed in the zip attached below.

[miracle.flame]

These all compiled well. Thank you very much! Not sure what it fixed but i believe it saved me a lot of troubles.

[doomlazer]

It may or may not have fixed anything, but it seemed like the best way to avoid possibly introducing bugs. Don't hesitate to reach out if you run into any problems or have questions!