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

[troflip]

Another feature that might be beneficial for playing with something like this is the ability to preview a Picture with other palettes (either from a selection of PAL resources, embedded palettes from other PICTURE resources, or importing a new palette). SCI Viewer can already do this natively, minus the imported palette option. I see that Companion can already preview in the editor with other palettes.

Can you describe in a little more detail? What I can see doing is to have the same functionality in the pic editor as there is in the view editor, where you can choose the palette to display the picture in. The list consists of the embedded palette, and all the pal resources in the game. Would that suffice?

Extracting palettes from other pics is probably not something I can do in UI-time (so I'd need to do this in the background or something), so having those in the list would be more difficult.

Regarding all the extra "demo" content for the template game, I think we should keep the template game as cut down as possible. Even remove the current screens and keep it as simple as SCI0's template game; a blank slate. Black title screen and an all white empty first room with basic interactions. Any feature/tutorial content we can rename the current template game into Demo Game, like Brian did for SCI0. But a starter game should always be a blank slate. Just a thought.

I agree with this. Once the template game is "finalized", I can make a final version with all the cruft removed.

[troflip]

Cat.sc, all these unused .sco files like Flo and Droole...

I'm pretty sure I removed all extraneous sco/sc files from the template game a while ago. (Flo and such are gone).

Cat.sc I left in, as I don't know it's purpose. It seems like a general purpose Actor class, but I'm not sure what it does.

[Kawa]

Cat.sc I left in, as I don't know it's purpose. It seems like a general purpose Actor class, but I'm not sure what it does.

Code: [Select]

Searching for: [^o]cat[^i]
Cat.sc(9): (class Cat of Actor
ClickMenu.sc(103): StrCat(@temp8 ": ")
ClickMenu.sc(105): StrCat(@temp8 " ")
ClickMenu.sc(106): StrCat(text @temp8)
Obj.sc(234): (if (not (self:isDuplicate(param1[temp1])))
Obj.sc(336): (method (isDuplicate)
Obj.sc(385): (if (not (self:isDuplicate(param1[temp0])))
Obj.sc(402): (if (not (self:isDuplicate(param1[temp0])))
Obj.sc(419): (if (not (self:isDuplicate(param2[temp0])))
Obj.sc(456): (method (isDuplicate param1)
rm1000.sc(107): (catwalk:
rm1000.sc(799): (instance catwalk of Feature
rm1001.sc(64): (catwalk:
rm1001.sc(438): (instance catwalk of Feature
Sq5InvItem.sc(119): add(Buckazoids {Floor Scrubber} {Safety Cones} {Distributor Cap} {Transporter Fuse} Antacid {Ship Opener} {Cutting Torch} Spike {Oxygen Tank} Communicator {Hole Punch} {Cloaking Device} {Space Monkeys Package} {Business Card} {Genetix Canister} {Liquid Nitro Tank} {Kiz Branch} {Kiz Fruit} frock {WD40 Head} {Oxygen Mask} Paper)
Sq5InvItem.sc(370): (instance Communicator of Sq5InvItem
sysLogger.sc(54): StrCat(@temp0 "
Found 17 occurrence(s) in 7 file(s)

Code: [Select]

Searching for: of Cat
ice\src\controlPanel.sc(452): (instance wheel of Cat
ice\src\controlPanel.sc(1128): (instance diveLever of Cat
ice\src\controlPanel.sc(1192): (instance engineLever of Cat
qfg1v\src\Rock.sc(352): (instance lasso of Cat
Found 4 occurrence(s) in 2 file(s)It doesn't seem to be used much at all.

[troflip]

Can anyone who played those games guess how it might have been used? It appears to be an animated object that you can click and drag.

[troflip]

Version 3.0.0.8 released a fix for the crash and a number of other improvements.

[MusicallyInspired]

If previewing palettes in the Pic editor like you've already got done in the View editor is the easiest thing to do then that will suffice, yes.

[lance.ewing]

Can anyone who played those games guess how it might have been used? It appears to be an animated object that you can click and drag.

Might be why it was called Cat then, i.e. because it interacts with the "mouse" in a certain way. Does it "catch" the mouse in some manner? I haven't yet looked at the source, so just thinking about what the name might mean.

[troflip]

Yeah, haha, that makes sense. It looks like it is just a view that follows the mouse when you drag on it. Not terribly useful, it can probably be removed.

[lskovlun]

Maybe not for games as such. It could be useful for toolmaking though.

[MusicallyInspired]

SQ5 must have used it in that scene where you're rummaging through the tool box. That's pretty useful. Think puzzle minigames.

[Kawa]

SQ5 must have used it in that scene where you're rummaging through the tool box. That's pretty useful. Think puzzle minigames.

False.

Code: [Select]

Searching for: of Cat
Searching for: Cat
Cat.sc(9): (class Cat of Actor
ClickMenu.sc(103): StrCat(@temp8 ": ")
ClickMenu.sc(105): StrCat(@temp8 " ")
ClickMenu.sc(106): StrCat(text @temp8)
sysLogger.sc(54): StrCat(@temp0 "
Found 5 occurrence(s) in 3 file(s)
The relevant script seems to be Tool.sc, actually rm226.

[MusicallyInspired]

Ah! It was only a guess.

[Kawa]

Here's something that I really felt I missed while working on my Larry-style question list: importing and exporting message tables in plaintext. Preferrably in the format used by SV, which is basically tab-delimited.

[troflip]

Would you want the nouns etc in number form or N_* form? Or both?

[Kawa]

My personal preference would go towards numerical, but I supposes a switch would be good.

Interesting detail on newlines in messages as SV exports them:

Code: [Select]

1 0 0 2 98 This is the first line.
This is the second.
1 0 0 3 98 This is another message.If a line starts with five tabs, it's part of the last message that didn't. So no "This is the first line.\nThis is the second."