SCI01 Template Game

[MusicallyInspired]

Why use a demo or minigame at all? The SCI0 template game used LSL3 as a base, IIRC. The SCI11 template game is based on a stripped SQ5. I don't see the issue with basing it on a full game, unless you're just thinking it would be easier to start with less and not have to strip stuff out?

Either way, I'm really looking forward to a SCI1 template game!

[EricOakford]

Okay, I've fixed part of the issue with saving games. Based on what I did for the QFG1VGA decompile, I managed to replace the SRDialog doit with that from SCI16, adapting it for SCI01. Now, the interpreter no longer creates duplicate saves with the same name. But the graphical issue with the menu after restoring a game remains, though. It's probably some kind of buffer overflow.

UPDATE 3/5/2019: And now I've managed to address the graphical issue! What I did was put a space before each menu item in the AddMenus. This was done in KQ1SCI and Codename Iceman.

[MusicallyInspired]

Nice!

[Doan Sephim]

Quick question. I just opened up the template game and have a question.

There appears to be duplicates of resources, like views. When I  rebuild resources, they persist.

I'm not used to this and I don't know if it has advantages, disadvantages, or is completely neutral.

What's the purpose?

[lskovlun]

I assume there'd be a hint in the table view? A bunch of patches lying around would be the most likely.

[Doan Sephim]

I assume there'd be a hint in the table view? A bunch of patches lying around would be the most likely.

That is the case. Suppose I edit a patch. Will that be a problem?

[MusicallyInspired]

I don't think so. I think it just saves over the patch file.

[EricOakford]

Why use a demo or minigame at all? The SCI0 template game used LSL3 as a base, IIRC. The SCI11 template game is based on a stripped SQ5. I don't see the issue with basing it on a full game, unless you're just thinking it would be easier to start with less and not have to strip stuff out?

In both of those templates, they have clear signs of their origins.

SCI0 had the option of window colors (which is specific to LSL3) and the "Order Hintbook" joke option in the death dialog (again, this is only in LSL2 and 3).

SCI1.1 has SQ5's specific fonts, subclasses, and status code.

My main focus was to make my templates as generic and minimalist as possible, and mainly use the stock SCI resources that can be found in game demos. Since they're officially freely available and have minimal game-specific scripts, it makes perfect sense to repurpose those.

[EricOakford]

Hmm... it seems I'd made a commit a month ago, but I'd forgotten to push it! Oops!   

Most of the changes were in the system scripts, thankfully.
The big change here? Support for sorted features! They were used in QFG2.

Now this is as as complete as it can get. Have fun.

[MusicallyInspired]

Nice!

[EricOakford]

A major update!
Going back to the decompiled SCI0 system scripts and comparing them with their SCI01 counterparts using ExamDiff, I have managed to fill in the blanks for nearly every system script. The temp variables and parameters have been identified.
I'd gotten this idea from my recent decompilations of the LSL1, LSL5, SQ1VGA, and PQ3 demos, where I took the extra step in painstakingly identifying all the params and temps I could in their system scripts.
Also, while I'd done this earlier, I'd also created a subclass of InvItem in the main script. This subclass will allow item descriptions to be placed in a Text resource, saving on heap space and simplifying potential translations.

And there you go, the definitive template for SCI parser games is just about complete!

To answer Doan Sephim's question: The reason you see duplicate resources may be because I set the template to be managed as patch files. This is for source control purposes. The interpreter prioritizes patch files over the contents of RESOURCE.000. I have been using Kawa's SCICompanion build.

[Kawa]

I have been using Kawa's SCICompanion build.

*feels validated*