SCI Companion V3 - alpha build notes/bugs/feature requests

[Collector]

Hey Phil, have you added anything to call the publisher from Companion, yet? The latest build should do everything automatically just from using the project' path as an argument.

[troflip]

Not yet, I'll def give it a shot before I release the Companion beta though...

[Collector]

Grab the last build before you try it.

[Cloudee1]

There seems to be a script 19 that is popping up in the template game.

The source file isn't there, but the room can be decompiled. Looks like it contains a FakeView of Obj class and a public procedure which looks like it displays a message reporting the brTop and brBottom

Is this something which should still be hanging around?

[troflip]

I don't see this in the current version of the template game, so I must have cleaned it up at some point. There were definitely some turds left over.

[Cloudee1]

That's what I had expected, just making sure.

I am turning it into my own little cursor hot spot testing room.

[troflip]

Lol. Great minds think alike.

[troflip]

Hey Phil, have you added anything to call the publisher from Companion, yet? The latest build should do everything automatically just from using the project' path as an argument.

Done. I posted my experience in the sierra help forums. Looks great!

[Collector]

Looks good. Is there a link to the latest template game so I cam make a few tweaks to the app?

[troflip]

Latest is here:
https://github.com/icefallgames/SCICompanion/tree/master/SCICompanion/Files/TemplateGame

Those are still in Studio language though. The Sierra syntax will have the version string in {} (not "") most likely. But you probably need to handle both. Or just grab it from the first line of the version file? (which is what the SCI 1.1 tempalte game does).

Not sure how I'm going to handle choosing the scripting language yet. Conversion takes a while, so I either need to checkin the converted template games (which means I need to manually convert each time I make a change), or have them converted as part of the build process (which may take effort).

Attached is the Sierra Script version of Main.sc.
The parens will definitely be there. I may change the converter to use quotes instead of braces, not sure. Both are valid.

[Collector]

As I said I could also just do a RegEx to get just alphanumeric characters and periods. I have thought about this some when designing parts of SCI Developer. Many of the SCI0 fan games never have the name or version set in the scripts. It is not uncommon for fan games to use 'TEMPLATE' for the save file name. Add to it a VERSION file and it is one more thing that many developers will miss. My solution for Developer was to set it from the IDE's game property dialog, though I should add a check to see if the Main.sc script is open with unsaved changes before applying name/version changes.

Anyway, I will probably have multiple methods as a failsafe. It can try another way to get the info if the value returned is null.

[troflip]

It's just in the version file because that's the way SQ5 did it. I haven't given much thought to game name or version number. I'm open to changing it as long as the interpreter doesn't care if version is mission.

Where is the save game name set?

[Kawa]

Where is the save game name set?

I just got up so I may have misread your intent here, but... the savee game name is set in a few places in srdialog.sc for starters, also game.sc where the actual saving/restoring takes place.

Since half the stuff is ASM, here's save.sc:
line 90: (= numGames (GetSaveFiles (theGame name?) names nums))
line 229: (= fd (FileIO fileOpen (Format @str {%ssg.dir} (theGame name?))))
line 272: (= numGames (GetSaveFiles (theGame name?) @names @nums))
line 348: ((= fd (File new:)) name: (DeviceInfo MakeSaveDirName @str (theGame name?)), open: fTrunc)

And since "TEMPLATE" is too long (eight characters), the "SG" part that the engine adds is cut off, which is why we have "KQ6SG.010" but "TEMPLATE.002".

[Collector]

This is based on SCI0 games, but setting the '(instance public Template of Game' in the main script to the game name should be enough, but if the title contains spaces it will retain the previous name (i.e. 'TEMPLATE'). Enclosing the title in this line in curly brackets fixes this. In fact I would say that the line in the SCI0 template game should be changed to '(instance public {Template} of Game' . But again, it just trims it down to 8 characters so there is no room for the 'SG' as Kawa mentions. It would be nice if it auto-trimmed it to six characters to leave room for the SG. I have not looked into how it is set in the SCI1.1 template.

[Kawa]

The SCI11 template game, being class SQ5 of Game, uses SQ5SG.*.