1
SCI Syntax Help / Re: SCI0: GoToIfSaid ?
« on: May 23, 2026, 05:12:02 AM »Wouldn't you need pathfinding support for "GoToIfSaid" type functionality? I don't think that was added until after SCI0.It seems to use Avoiders.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
SCI Syntax Help / Re: SCI0: GoToIfSaid ?
« on: May 22, 2026, 06:16:04 AM »
Considering they're both script functions, not engine or language features, the only reason they wouldn't be accepted is if you simply don't have that script file, or forgot to use it.
As for how it's used, looking at Sluicebox's decomp here's an example from [?]Codename ICEMAN[/i]'s beachHuts3.sc:
So it makes sure to turn toward the door if you need to turn toward it first, which stops the cond block. If you're already looking at the door, this condition fails and (Said 'look[<at]') gets a turn.
This script is also known as GotoSaid.sc in the leaked Larry 3 and 5 code, though it's unused there. The proper definitions of both IfSaid functions are:
As for how it's used, looking at Sluicebox's decomp here's an example from [?]Codename ICEMAN[/i]'s beachHuts3.sc:
Code: [Select]
((Said '[/door]>')
(cond
((TurnIfSaid self event 'look/*'))
((Said 'look[<at]') (Print 12 3) ; "This is the door to hut #2.")
Note that this is hutDoor::handleEvent, so self is the hut door.So it makes sure to turn toward the door if you need to turn toward it first, which stops the cond block. If you're already looking at the door, this condition fails and (Said 'look[<at]') gets a turn.
This script is also known as GotoSaid.sc in the leaked Larry 3 and 5 code, though it's unused there. The proper definitions of both IfSaid functions are:
Code: [Select]
(GoToIfSaid obj event theTargetOrX theDistanceOrY optSpec)
(TurnIfSaid obj event optSpec)
3
SCI Development Tools / SSCI, ScummVM, and polygons
« on: April 30, 2026, 05:39:59 PM »
Some two hours ago, another commit was made to ScummVM involving differences between its pathfinder and Sierra's. In this case, it involved SQ6 and a spike shape in one of the rooms' polygons which is removed by a script patch. Another commit fixes a barred-access poly that extends beyond a contained-access poly which trips up the logic. I've seen patches like this before where a problematic polygon shape needs to be tweaked (LB2 comes to mind, not sure if correctly) and now I have to wonder.
What exactly are the problematic shapes that ScummVM's pathfinder has trouble with? Knowing what to avoid and how could help home-made SCI games run correctly on both interpreters.
What exactly are the problematic shapes that ScummVM's pathfinder has trouble with? Knowing what to avoid and how could help home-made SCI games run correctly on both interpreters.
4
SCI Development Tools / Re: Converting Pics from SCI1 to SCI1.1 format
« on: April 15, 2026, 11:00:22 AM »I believe it's also the reason most actors keep to the first 16 (or 32) colors so they can move between all rooms without issue. The rest of the colors are then used for pics or per room objects.The global palette tends to be 64 colors (0-63, plus 255). Other than that you're basically on the money.
5
SCI Syntax Help / Re: QfGIVCD view corruption when editing 936.v56
« on: April 13, 2026, 03:14:06 PM »
Wait. How does that relate to view corruption?
6
AGI Development Tools / Re: The Plot [Pen Style] Thickens
« on: April 03, 2026, 03:23:57 AM »
Well, I guess I gotta eat my words now.
*nom*
*nom*
7
AGI Development Tools / Re: The Plot [Pen Style] Thickens
« on: March 26, 2026, 04:48:09 AM »
One week later, there are multiple pen tables in ScummVM. Mark my words.
*My beleaguered manservant Mark hands me my dictionary*
*My beleaguered manservant Mark hands me my dictionary*
8
AGI Development Tools / Re: The Plot [Pen Style] Thickens
« on: March 25, 2026, 08:56:43 AM »
That's quite a find. Congratulations!
9
The Games and other Sierra Adventure stuff / Re: Playing around with AI Image Conversion on Sierra titles
« on: March 25, 2026, 08:53:19 AM »
Your idea sounds pretty good, but I'd say if AI's involvement is that small you might as well leave those tweaks and checks to the user. I figure that could also help not make everyone's stuff look the same (1).
As for having the time and tools... FotoSketcher gives pretty good painterly results for free and has custom preset support. Color grading and other content tweaks can be done in anything from Paint.net to Photopea. It takes me more time to set up the original scenes and turn them into SCI backgrounds with priority screens and polygons, than it does to paintify them.
(1) Consider how you can pick out AI artwork so easily. Or the responses to DLSS5.
(2) haha you can type superscript digits all you want and they work in the preview but once they're stored... I hate this board's database settings I truly do XD
As for having the time and tools... FotoSketcher gives pretty good painterly results for free and has custom preset support. Color grading and other content tweaks can be done in anything from Paint.net to Photopea. It takes me more time to set up the original scenes and turn them into SCI backgrounds with priority screens and polygons, than it does to paintify them.
(1) Consider how you can pick out AI artwork so easily. Or the responses to DLSS5.
(2) haha you can type superscript digits all you want and they work in the preview but once they're stored... I hate this board's database settings I truly do XD
10
SCI Development Tools / Re: Script issues with QFG1VGA
« on: February 26, 2026, 05:35:18 AM »
I did indeed mean extracting HEP files as patches and using a hex editor. You'll find the local strings, if any, near the bottom of the file. Class and instance names count as local strings so you'll know it when you see it.
11
SCI Development Tools / Re: Script issues with QFG1VGA
« on: February 25, 2026, 06:03:54 PM »
If you want to avoid having to decompile and recompile scripts just to edit local strings, have you considered extracting their heap resources, editing them in a hex editor, and doing your best to keep the Dutch sentences at most the same length as the English originals?
Of course, for some places that won't work right like script 32, which has the line "It only took you %d game%s to win.", with the "s" to pluralize "game" right before it.. which could be adjusted to "len" despite being two bytes longer if you're willing and able to mess with the raw script bytecode. So of course I randomly picked that one to demonstrate the technique with. Just my luck.
(For the record and those playing along at home: oops code 4 would be "not an object".)
Of course, for some places that won't work right like script 32, which has the line "It only took you %d game%s to win.", with the "s" to pluralize "game" right before it.. which could be adjusted to "len" despite being two bytes longer if you're willing and able to mess with the raw script bytecode. So of course I randomly picked that one to demonstrate the technique with. Just my luck.
(For the record and those playing along at home: oops code 4 would be "not an object".)
12
SCI Development Tools / Re: Copyright state with games created in SCICompanion
« on: January 31, 2026, 03:18:02 AM »
He still uses the PMachine, with only a few more opcodes (some of them also available in SCI11+ for that matter). As I understand it, it is an SCI interpreter running in Unity with extra features bolted on. That's why his personal branch of SCI Companion has things like a particle system renderer that generates view resources.
13
SCI Development Tools / Re: Copyright state with games created in SCICompanion
« on: January 30, 2026, 09:59:52 AM »
Yeah, selling the games would muddy the waters a bunch. With freeware at least you have the excuse that, well, it's free, and it's a 30-something year old system.
Roland may be proactive about their ROMs, but until Sierra or whoever holds the rights at this time start making requests I'd just stick with freeware distribution.
(Besides, you don't need MT32 ROMs to play. Whatcha gonna do, include a copy of Munt? A shortcut to an eBay search for real MT32? I'd say just offer General MIDI and keep the MT32 as a bonus for whoever already has the ability to play that.)
Roland may be proactive about their ROMs, but until Sierra or whoever holds the rights at this time start making requests I'd just stick with freeware distribution.
(Besides, you don't need MT32 ROMs to play. Whatcha gonna do, include a copy of Munt? A shortcut to an eBay search for real MT32? I'd say just offer General MIDI and keep the MT32 as a bonus for whoever already has the ability to play that.)
14
Everything-Else / Re: What's up peeps!
« on: January 28, 2026, 08:28:45 AM »
Well, there's one or two features for SCI Companion that've been requested, but I really don't see myself implementing scaler support for the picture editor's fake ego so make of that what you will. I really ought to continue working on my SCI game too, but the only work recently done on that was to begin reworking the you-know-what at the end of the day, while the rest of the game remains unwritten.
I have non-SCI/AGI projects to work on too, but you didn't ask for any of those.
So yeah, it's been a time.
I have non-SCI/AGI projects to work on too, but you didn't ask for any of those.
So yeah, it's been a time.
15
SCI Development Tools / Re: SCI Companion V3 - alpha build notes/bugs/feature requests
« on: January 17, 2026, 05:53:52 AM »I thought the source code of SV was lost and unrecoverable?True enough. But who was talking about SV?
SMF 2.0.19 |
SMF © 2021, Simple Machines
Simple Audio Video Embedder
Page created in 0.05 seconds with 19 queries.