SCI Wiki - User contributions [en]

Main Page

2026-06-29T13:26:29Z

Andrew Branscom:

__NOTOC__

<div align="center" style="font-size: 14pt"><span class="Alert">The SCI Wiki has been merged into the new '''[https://wiki.sierrahelp.com/index.php/Main_Page Sierra Wiki]'''. This Wiki is now read only. It is being merged with the new Sierra Wiki. Any changes or addition will need to be made on new Wiki.

If you wish to add or edit any of the material on this Wiki, please request a Sierra Wiki account to make any additions or changes to any content since because of spammers, registrations for it had to be disabled. If you wish an account for it you will need to contact me. Note the new Wiki is a WIP. </span></div><br />

----

<span class="Inactive">
===Welcome to the SCI Programmers Wiki.===

A Wiki for the SCI Programming Community. SCI is the game engine created by [[Jeff Stephenson]] for [[Sierra On-Line]], which was used between the years of 1989 to 1997. It superseded Sierra's earlier AGI engine. It was used to create such games as ''[[King's Quest IV]]'' to VII, ''[[Space Quest III]]'' to ''[[Space Quest 6|6]]'', ''[[Quest for Glory I]]'' to ''[[Quest for Glory IV|IV]]'' and ''[[Gabriel Knight I]]'' and ''[[Beast Within: A Gabriel Knight Mystery, The|II]]''. With the availability of such tools as [[SCI Studio|Brian Provinciano's SCI Studio 3]] and [[SCI Companion|Phil Fortier's SCI Companion]], you can create your own games based on the same engine that Sierra used. This Wiki is a knowledgebase and collection of resources for those working with SCI. Additional help can always be found on the [[SCIPF:|SCI Programming Community Message Board]]. For help with Sierra's games, see [[SHP:|The Sierra Help Pages]].

===<br /> News ===

{| width="100%" cellspacing="20"
|-
| style="border: 1px solid #C9AE56; background-color: #FFFBED" width="50%" valign="top" | <div style="padding: .4em .9em .9em">
'''March, 2016'''

* [[SEQTool]], another SCI Companion plugin is under development. This tool is based on [[Kawa|Kawa's]] [[SeqMaker]], a command line program. With SEQTool you can edit existing [[SEQ Resource|SEQ files]] (used for cut scenes in SCI1 and later Sierra games), create new ones from your own 320px x 200px paletted 8-bit color images, import animated GIFs to SEQ or export frames from SEQ files to individual image files.

'''Feb 07, 2016'''

* There is a new version of [[Phil Fortier|Phil Fortier's]] [[SCI Companion]]. SCI Companion v3 supports development of games from [[Sierra_Release_List#SCI0_.28early.29 | SCI0]] to [[Sierra_Release_List#SCI1.1 | SCI1.1]]. Besides VGA graphics you will now be able to add digital sound effects and lip synced speech to your SCI games.

* [[NSIS Publisher]], SCI Companion's first plugin has been released. NSIS Publisher allows you to publish your SCI Companion project using the [http://nsis.sourceforge.net/Main_Page Null Soft Install System (NSIS)] and can automatically compile a DOSBox installer for distribution of your game.
</div>
|}

===<br /> Getting started ===

New here? Visit the [[Getting Started]] page for information about how to create new SCI games, or understand the Tools behind editing them.

Please also take the time to visit the [[Community Portal]], which contains useful links for SCI and the SCI Wiki.

If you are interested in contributing to the Wiki see [[#How to Contribute|How to Contribute]] below.

===<br /> Links ===

Links for additional help and resources for help for your SCI needs.

[http://sciprogramming.com SCI Programming.com]   -   http://sciprogramming.com
: [http://sciprogramming.com/community/ SCI Programming.com message boards]   -   http://sciprogramming.com/community/
: [http://sciprogramming.com/scitools.php SCI Tools on SCI Programming.com]   -   http://sciprogramming.com/scitools.php
: [http://sciprogramming.com/fangames.php SCI fan games]   -   http://sciprogramming.com/fangames.php
[[scicomp:|SCI Companion]]<br />
[[scicompdoc:|SCI Companion Documentation]]<br />

[http://scistudio.sourceforge.net/ SCI Studio on SourceForge]   -   http://scistudio.sourceforge.net/<br>


===<br /> How to Contribute ===

No registration is required to view this Wiki. Anyone can view the various topics and guides on the SCI Wiki. However, to add or edit pages, you must be [[Special:Userlogin|logged in]]. If you are not registered, you may request an account editing privileges.

Contact Collector on the [[SCIPF:|SCI Programming Community Message Board]] or [[shp:forums|The Sierra Help Pages Forums]] if you wish to contribute.

<blockquote>
==== Notes for Editors: ====

Please familiarize yourself with [[Help:Contents | MediaWiki formatting]] before adding or editing pages. See the [[Notes_for_Editors|Notes for Editors]] page for SCI Wiki standards and news.
</blockquote>

[[Category:Wiki Help]]

Main Page

2026-06-29T13:26:04Z

Andrew Branscom:

__NOTOC__

<div align="center" style="font-size: 14pt"><span class="Alert">The SCI Wiki has been merged into the new '''[https://wiki.sierrahelp.com/index.php/Main_Page Sierra Wiki]'''. This Wiki is now read only. It is being merged with the new Sierra Wiki. Any changes or addition will need to be made on new Wiki.

If you wish to add or edit any of the material on this Wiki, please request a Sierra Wiki account to make any additions or changes to any content since because of spammers, registrations for it had to be disabled. If you wish an account for it you will need to contact me. Note the new Wiki is a WIP. </span></div><br />

----

===Welcome to the SCI Programmers Wiki.===

A Wiki for the SCI Programming Community. SCI is the game engine created by [[Jeff Stephenson]] for [[Sierra On-Line]], which was used between the years of 1989 to 1997. It superseded Sierra's earlier AGI engine. It was used to create such games as ''[[King's Quest IV]]'' to VII, ''[[Space Quest III]]'' to ''[[Space Quest 6|6]]'', ''[[Quest for Glory I]]'' to ''[[Quest for Glory IV|IV]]'' and ''[[Gabriel Knight I]]'' and ''[[Beast Within: A Gabriel Knight Mystery, The|II]]''. With the availability of such tools as [[SCI Studio|Brian Provinciano's SCI Studio 3]] and [[SCI Companion|Phil Fortier's SCI Companion]], you can create your own games based on the same engine that Sierra used. This Wiki is a knowledgebase and collection of resources for those working with SCI. Additional help can always be found on the [[SCIPF:|SCI Programming Community Message Board]]. For help with Sierra's games, see [[SHP:|The Sierra Help Pages]].

===<br /> News ===

{| width="100%" cellspacing="20"
|-
| style="border: 1px solid #C9AE56; background-color: #FFFBED" width="50%" valign="top" | <div style="padding: .4em .9em .9em">
'''March, 2016'''

* [[SEQTool]], another SCI Companion plugin is under development. This tool is based on [[Kawa|Kawa's]] [[SeqMaker]], a command line program. With SEQTool you can edit existing [[SEQ Resource|SEQ files]] (used for cut scenes in SCI1 and later Sierra games), create new ones from your own 320px x 200px paletted 8-bit color images, import animated GIFs to SEQ or export frames from SEQ files to individual image files.

'''Feb 07, 2016'''

* There is a new version of [[Phil Fortier|Phil Fortier's]] [[SCI Companion]]. SCI Companion v3 supports development of games from [[Sierra_Release_List#SCI0_.28early.29 | SCI0]] to [[Sierra_Release_List#SCI1.1 | SCI1.1]]. Besides VGA graphics you will now be able to add digital sound effects and lip synced speech to your SCI games.

* [[NSIS Publisher]], SCI Companion's first plugin has been released. NSIS Publisher allows you to publish your SCI Companion project using the [http://nsis.sourceforge.net/Main_Page Null Soft Install System (NSIS)] and can automatically compile a DOSBox installer for distribution of your game.
</div>
|}

===<br /> Getting started ===

New here? Visit the [[Getting Started]] page for information about how to create new SCI games, or understand the Tools behind editing them.

Please also take the time to visit the [[Community Portal]], which contains useful links for SCI and the SCI Wiki.

If you are interested in contributing to the Wiki see [[#How to Contribute|How to Contribute]] below.

===<br /> Links ===

Links for additional help and resources for help for your SCI needs.

[http://sciprogramming.com SCI Programming.com]   -   http://sciprogramming.com
: [http://sciprogramming.com/community/ SCI Programming.com message boards]   -   http://sciprogramming.com/community/
: [http://sciprogramming.com/scitools.php SCI Tools on SCI Programming.com]   -   http://sciprogramming.com/scitools.php
: [http://sciprogramming.com/fangames.php SCI fan games]   -   http://sciprogramming.com/fangames.php
[[scicomp:|SCI Companion]]<br />
[[scicompdoc:|SCI Companion Documentation]]<br />

[http://scistudio.sourceforge.net/ SCI Studio on SourceForge]   -   http://scistudio.sourceforge.net/<br>


===<br /> How to Contribute ===

No registration is required to view this Wiki. Anyone can view the various topics and guides on the SCI Wiki. However, to add or edit pages, you must be [[Special:Userlogin|logged in]]. If you are not registered, you may request an account editing privileges.

Contact Collector on the [[SCIPF:|SCI Programming Community Message Board]] or [[shp:forums|The Sierra Help Pages Forums]] if you wish to contribute.

<blockquote>
==== Notes for Editors: ====

Please familiarize yourself with [[Help:Contents | MediaWiki formatting]] before adding or editing pages. See the [[Notes_for_Editors|Notes for Editors]] page for SCI Wiki standards and news.
</blockquote>

[[Category:Wiki Help]]

Main Page

2026-02-02T03:25:51Z

Andrew Branscom:

__NOTOC__

;Note: The SCI Wiki has been merged into the new '''[https://wiki.sierrahelp.com/index.php/Main_Page Sierra Wiki]'''. If you wish to add or edit any of the material on this Wiki, please request a Sierra Wiki account to make any additions or changes to the SCI content. Note the new Wiki is a WIP.

===Welcome to the SCI Programmers Wiki.===

A Wiki for the SCI Programming Community. SCI is the game engine created by [[Jeff Stephenson]] for [[Sierra On-Line]], which was used between the years of 1989 to 1997. It superseded Sierra's earlier AGI engine. It was used to create such games as ''[[King's Quest IV]]'' to VII, ''[[Space Quest III]]'' to ''[[Space Quest 6|6]]'', ''[[Quest for Glory I]]'' to ''[[Quest for Glory IV|IV]]'' and ''[[Gabriel Knight I]]'' and ''[[Beast Within: A Gabriel Knight Mystery, The|II]]''. With the availability of such tools as [[SCI Studio|Brian Provinciano's SCI Studio 3]] and [[SCI Companion|Phil Fortier's SCI Companion]], you can create your own games based on the same engine that Sierra used. This Wiki is a knowledgebase and collection of resources for those working with SCI. Additional help can always be found on the [[SCIPF:|SCI Programming Community Message Board]]. For help with Sierra's games, see [[SHP:|The Sierra Help Pages]].

===<br /> News ===

{| width="100%" cellspacing="20"
|-
| style="border: 1px solid #C9AE56; background-color: #FFFBED" width="50%" valign="top" | <div style="padding: .4em .9em .9em">
'''March, 2016'''

* [[SEQTool]], another SCI Companion plugin is under development. This tool is based on [[Kawa|Kawa's]] [[SeqMaker]], a command line program. With SEQTool you can edit existing [[SEQ Resource|SEQ files]] (used for cut scenes in SCI1 and later Sierra games), create new ones from your own 320px x 200px paletted 8-bit color images, import animated GIFs to SEQ or export frames from SEQ files to individual image files.

'''Feb 07, 2016'''

* There is a new version of [[Phil Fortier|Phil Fortier's]] [[SCI Companion]]. SCI Companion v3 supports development of games from [[Sierra_Release_List#SCI0_.28early.29 | SCI0]] to [[Sierra_Release_List#SCI1.1 | SCI1.1]]. Besides VGA graphics you will now be able to add digital sound effects and lip synced speech to your SCI games.

* [[NSIS Publisher]], SCI Companion's first plugin has been released. NSIS Publisher allows you to publish your SCI Companion project using the [http://nsis.sourceforge.net/Main_Page Null Soft Install System (NSIS)] and can automatically compile a DOSBox installer for distribution of your game.
</div>
|}

===<br /> Getting started ===

New here? Visit the [[Getting Started]] page for information about how to create new SCI games, or understand the Tools behind editing them.

Please also take the time to visit the [[Community Portal]], which contains useful links for SCI and the SCI Wiki.

If you are interested in contributing to the Wiki see [[#How to Contribute|How to Contribute]] below.

===<br /> Links ===

Links for additional help and resources for help for your SCI needs.

[http://sciprogramming.com SCI Programming.com]   -   http://sciprogramming.com
: [http://sciprogramming.com/community/ SCI Programming.com message boards]   -   http://sciprogramming.com/community/
: [http://sciprogramming.com/scitools.php SCI Tools on SCI Programming.com]   -   http://sciprogramming.com/scitools.php
: [http://sciprogramming.com/fangames.php SCI fan games]   -   http://sciprogramming.com/fangames.php
[[scicomp:|SCI Companion]]<br />
[[scicompdoc:|SCI Companion Documentation]]<br />

[http://scistudio.sourceforge.net/ SCI Studio on SourceForge]   -   http://scistudio.sourceforge.net/<br>


===<br /> How to Contribute ===

No registration is required to view this Wiki. Anyone can view the various topics and guides on the SCI Wiki. However, to add or edit pages, you must be [[Special:Userlogin|logged in]]. If you are not registered, you may request an account editing privileges.

Contact Collector on the [[SCIPF:|SCI Programming Community Message Board]] or [[shp:forums|The Sierra Help Pages Forums]] if you wish to contribute.

<blockquote>
==== Notes for Editors: ====

Please familiarize yourself with [[Help:Contents | MediaWiki formatting]] before adding or editing pages. See the [[Notes_for_Editors|Notes for Editors]] page for SCI Wiki standards and news.
</blockquote>

[[Category:Wiki Help]]

Leisure Suit Larry 4: The Case of the Missing Floppies

2025-04-28T00:34:23Z

Andrew Branscom:

#REDIRECT [http://www.allowe.com/games/larry/inside-stories/is-lsl5-lsl4.html]
 
[[Category:Sierra Releases]]

Template:JeremiahNellisQ

2025-04-15T18:10:09Z

Andrew Branscom: Protected "Template:JeremiahNellisQ" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<includeonly>[[Jeremiah Nellis]][[Category:Jeremiah Nellis Quotes]]</includeonly><noinclude>

== Copy & Paste ==

<nowiki>{{</nowiki>{{PAGENAME}}<nowiki>}}</nowiki>

== Explanation ==

Use this for pages containing quotes by Jeremiah Nellis.

[[Category:Templates]]
[[Category:Quotation Templates]]
</noinclude>

Template:JeremiahNellisQ

2025-04-15T18:10:00Z

Andrew Branscom: Created page with "<includeonly>Jeremiah NellisCategory:Jeremiah Nellis Quotes</includeonly><noinclude> == Copy & Paste == <nowiki>{{</nowiki>{{PAGENAME}}<nowiki>}}</nowiki> == E..."

SCI Narration Demo

2025-04-15T18:09:16Z

Andrew Branscom:

<div align="center" style="font-size: 22pt">SCI Narration Demo</div><br />

{{FanSCIReleaseInfobox
| ReleaseName = SCI Narration Demo
| Image = [[Image:SCINarrationDemoSS.png|190px]]<br />
''SCI Narration Demo<br />''Title Screen
| MusicalTheme = 
| ReleaseDate = {{2012}}-08-05<ref>https://sciprogramming.com/community/index.php?topic=616.0</ref>
| ProjectStatus = {{CompletedFanSCI}}
| ReleaseVersion = UnknownVer
| Developer = {{JeremiahNellis}}
| Publisher = {{JeremiahNellis}}
| Designer = {{JeremiahNellis}}
| Source = {{NoSource}}
| Category = {{FanSCITechApp}}
| Type = {{FanSCIDemoTechApp}}
| Genre = {{ProofOfConcept}}
| Theme = {{Script/Logic}}, {{Sound}}
| Engine = {{SCI0}}
| Platform = {{DOS}}
| Localization = {{English}}
| Website = {{SCIPSCIURL}}
}}

<br />
==<br /> Description ==

<blockquote>
[[Jeremiah Nellis]]'s '''''SCI Narration Demo''''' is a [[SCI0]] {{Proof Of ConceptCategory}}.

{{ReleasePageStub}}
</blockquote>


==<br /> Synopsis ==

<blockquote>
N/A
</blockquote>

==<br /> About ==

<div class="Quote">
{{Quote|Attrib = {{JeremiahNellisQ}}<ref>https://sciprogramming.com/community/index.php?topic=616.0</ref>
}}
application which will read all the printed text displayed within a game. It calls the Google Translate API in real-time while a game is playing and speaks the displayed text to you.

It's a fun little project that I hacked together this weekend. It utilizes the ability for an SCI game to write to a file. It runs externally to the game, monitoring a file that I've modified the Controls.sc script to write all the print statements to. The application picks up the changes, ships them off to the api, saves the results to an MP3 and plays them.

Here's the script modification:

<pre> (if( <> STRINGS_EQUAL StrCmp("Enter Input:" @msgBuf))
(if( <> NULL (= hFile FOpen("print.txt" fCREATE)) )
FPuts(hFile @msgBuf)
FClose(hFile)
Wait(30) //wait a bit, so we can sync the text with the voice (sort of)
)
)</pre>

I've uploaded a modified template game demonstrating the app. The executables: SCI_Narrate.exe and madplay.exe (madplay is needed to play the MP3s). If you want to incorporate a 'narrator' into your game, just copy the exe's into your game dir & modify or replace your Controls.sc.

I've included the C# source code for those interested.
</div>

==<br /> Where to Get It ==

<blockquote>
* [[Image:ZIP.png|ZIP File]] [[File:SCI_Narration_Demo.zip|SCI Narration Demo]]<span class="DLInfo"> (ZIP file) [485 KB]</span>
</blockquote>

==<br /> References ==

<references />

==<br /> Related Links ==

* [[:Category:Fan Releases|Fan Releases]]
* [[w:Special:Search/|:Category:Fan Releases|Fan Releases on Wikipedia]]
* [[Fan SCI Release List]]

 

[[Category:Fan Releases]]
[[Category:Fan SCI Releases]]

Footsteps Sound Demo

2025-04-15T18:08:12Z

Andrew Branscom:

<div align="center" style="font-size: 22pt">Footsteps Sound Demo</div><br />

{{FanSCIReleaseInfobox
| ReleaseName = Footsteps Sound Demo
| Image = [[Image:FootstepsSoundDemoSS.png|190px]]<br />
''Footsteps Sound Demo Title Screen''
| MusicalTheme = 
| ReleaseVersion = {{UnknownVer}}
| ReleaseDate = Sept, {{2012}}
| ProjectStatus = {{CompletedFanSCI}}
| Developer = {{JeremiahNellis}}
| Publisher = {{JeremiahNellis}}
| Designer = {{JeremiahNellis}}
| Category = {{FanSCITechApp}}
| Type = {{FanSCITechDemo}}
| Source = {{Source}}Included in download
| Genre = {{HowTo}}
| Theme = {{Script/Logic}}, {{Sound}}
| Engine = {{SCI0}}
| Platform = {{DOS}}
| Localization = {{English}}
| Website = {{SCIPSCIURL}}
}}

del {{FanSCITechDemo}}

==<br /> Description ==

<blockquote>
[[Jeremiah Nellis]]'s '''''Footsteps Sound Demo''''' is a fan [[SCI0]] How To demonstration. Shows how to add footstep sounds to a walking character in an SCI0 game.
</blockquote>

==<br /> Screenshots ==

{| align="center" width="70%"
| align="center"|
| align="center"|
|}

==<br /> Synopsis ==

<blockquote>
N/A
</blockquote>

==<br /> About ==

<blockquote>
 
</blockquote>

==<br /> Where to Get It ==

* [[Image:ZIP.png|ZIP File]] [[scidl:FanGames/Footsteps_Sound_Demo.zip|Footsteps Sound Demo]]<span class="DLInfo"> (ZIP file) [232 KB]</span>

==<br /> Walkthroughs/Hints ==

* N/A

==<br /> Related Links ==

* [[:Category:Fan Releases|Fan Releases]]
* [[Fan Release List|Fan Release List]]
* [[Fan SCI Release List]]

File:FootstepsSoundDemoSS.png

2025-04-15T18:07:22Z

Andrew Branscom: Andrew Branscom moved page File:TemplateGameSS.png to File:FootstepsSoundDemoSS.png without leaving a redirect

Betrayed Alliance Book 2 Demo

2025-04-13T13:21:07Z

Andrew Branscom: /* Screenshots */

<div align="center" style="font-size: 22pt">Betrayed Alliance Book 2 Demo</div><br />

{{ReleaseInfobox
| ReleaseName = Betrayed Alliance Book 2 Demo
| Image = [[File:Betrayed Alliance Book 2.jpg|thumb|Betrayed Alliance Book 2]]<br />
''Betrayed Alliance Book 2 Demo'' Title Screen
| MusicalTheme = 
| ReleaseVersion = 1.0
| ReleaseDate = Feb 24, {{2023}}
| ProjectStatus = {{InDevelopmentFanSCI}}
| Developer = {{Ryan Slattery}}
| Publisher = {{Ryan Slattery}}
| Designer = {{Ryan Slattery}}
| Music = {{Brandon Blume}}
| Source = {{Source}}[[#Download|Yes]]
| Category = {{FanSCIGame}}
| Type = {{FanSCIGameDemo}}
| Genre = {{Adventure}}, {{RPG}}
| Theme = {{FantasyRPG}}, {{LegendAdven}}, {{MythAdven}}
| Engine = {{SCI0}}
| CopyProtection = N/A
| ESRBRating = N/A
| Platform = {{DOS}}
| Localization = {{English}}
| Website = https://rjslattery.com/
}}

<br />
==<br /><br /> Description ==

<blockquote>
'''''Betrayed Alliance Book 2''''' is a free fan-made [[SCI0]] adventure game. It was developed by [[Ryan Slattery]] (a.k.a. Doan Sephim) using [[Brian Provinciano|Brian Provinciano's]] [[SCI Studio|SCI Studio 3]] and Phil Fortier's [[SCI Companion]].

</blockquote>

==<br /> Versions ==

<blockquote>
{| class="wikitable sortable" width="800"
! width="435"|Game!!width="125"|Game Version!! width="165" |Interpreter Version!!width="75"|Date
|- valign="top"
| Betrayed Alliance Book 2 Demo||align="center"|1.0||align="center"|0.000.685||width="75" align="center"|[[2023|2023/2/24]]
|}
</blockquote>

==<br /> Screenshots ==

{| align="center" width="80%"
| align="center"|[[File:Rock building.jpg|320px]]
| align="center"|[[File:StatueBrother.jpg|320px]]
| align="center"|[[File:268.jpg|320px]]
|- align="center" valign="top"
|-
|  
|- align="center"
| align="center"|[[File:271.jpg|320px]]
| align="center"|[[File:Battle System.jpg|320px]]
| align="center"|[[File:Leg broke.jpg|320px]]
|- align="center" valign="top"
|-
|  
|- align="center"
| align="center"|[[File:257.jpg|320px]]
| align="center"|[[File:Puzzle stone2.jpg|320px]]
| align="center"|[[File:35.jpg|320px]]
| align="center"| 
|- align="center" valign="top"
|}

==<br /> Synopsis ==

<blockquote>
The Cursed Forest: Dark secrets lie buried, but you're not alone! Switch between two playable characters in this fantasy adventure. Each character has their own strengths. As the General, battle your way through enemies and monsters and upgrade a few combat stats. Leah von Spier, however, is not equipped for combat and must use a different skillset to overcome enemies.
This Forest was home to a ancient tribe divining the mysteries of the "Great Wizard." Their disappearance is an enigma, but they left behind ruins and arcane items to puzzle over.
Your goal is to escape the forest. But your way is barred by obstacles both natural and supernatural. You'll have to meet the challenges of the forest, discover and outsmart the Enchantress whose curse prohibits your escape, and uncover a few mysteries along the way - mysteries that will no doubt aid you on your quest!
</blockquote>

==<br /> About ==

<blockquote>
Betrayed Alliance is meant to be an original throwback to the SCI0 adventure games with a particular nod towards Quests for Glory 1 and 2. As an SCI0 game it features the characteristic type-interface as well as mouse controls.

Betrayed Alliance Book 2 also features music and sound compatible with many classic music drivers: Mt32, Adlib, Soundblaster, Tandy 3, PC speaker, and perhaps more to come!
</blockquote>

==<br /> Reviews ==

<blockquote>
[[Betrayed Alliance Book 2 Demo Reviews]]
</blockquote>

==<br /> Downloads ==

<blockquote>* [[Image:ZIP.png|ZIP File]] [[File:BA2_DEMO_Setup.zip|Betrayed Alliance Book 2 Demo Setup]]<span class="DLInfo"> (ZIP file) [3.77 MB]</span>


==<br /> Walkthroughs/Hints ==

<blockquote>
Nothing yet, sorry!
</blockquote>

==<br /> Related Links ==

* [[Betrayed Alliance Series]]
* [[Betrayed Alliance Book 1]]
* [https://rjslattery.com/betrayed-alliance/ https://rjslattery.com/betrayed-alliance/]
* [[Fan SCI Release List|Fan SCI Release List]]
* [[:Category:Fan Releases|Fan Releases]]

[[Category:Fan Releases]]
[[Category:Fan SCI Releases]]

ToDo/Sierra Game Versions

2025-04-07T18:17:45Z

Andrew Branscom: /* Introduction */

The list is sorted on interpreter version.

 
== Introduction ==


This only deals with PC versions of the games. Based on [http://web.archive.org/web/20071130073710/http://sierra.8bit.co.uk/SVLIST091.TXT this document]. [http://www.sqeagz.com/passigar/ PASSIGAR] also has a very good list of almost all known Sierra game versions.


SCI games were originally ported to:
{| class="wikitable" width="400"
|-
!Platform!!SCI0/SCI01!!SCI1/SCI1.1!!SCI32
|-
|IBM PC||align="center"|Yes*||align="center"|286+||align="center"|386+
|-
|Apple Macintosh||align="center"|Yes||align="center"|Yes||align="center"|Yes
|-
|Atari ST||align="center"|Yes||align="center"|No||align="center"|No
|-
|Commodore AMIGA||align="center"|Yes||align="center"|Yes||align="center"|No
|-
|Fujitsu FM-Towns||align="center"|No||align="center"|Yes||align="center"|No
|-
|NEC PC-9801||align="center"|Yes||align="center"|Yes||align="center"|No
|}

<nowiki>*</nowiki> Including PCjr & Tandy

This table will show information about translations/international versions:
{| class="wikitable" width="800"
|-
!Interpreter||Foreign Version||Language Known||Suspect||Notes
|-
|align="center"|SCI0||align="center"|None||align="center"|None||align="center"|None||No unicode support
|-
|align="center"|SCI01||align="center"|Bilingual||align="center"|Fr/Ger||align="center"|Jap||Converted SCI01 games
|-
|align="center"|SCI1||align="center"|Bilingual||align="center"|Fr/Ger/It/Sp||align="center"|None||
|-
|align="center"|SCI11||align="center"|Standalone||align="center"|Fr/Ger/It/Sp/Pt||align="center"|Jap||Only RESOURCE.MSG differs
|-
|align="center"|SCI32||align="center"|Standalone||align="center"|Fr/Ger/It/Sp/Pt||align="center"|Jap||Sometimes subtitles only
|}

There are no real SCI0 translations as the SCI0 interpreter did not include diacritical characters like accent grave, acute accent, umlaut, etc. The SCI0 games that are translated are converted to the hybrid SCI01.

All the SCI0(1) games are released on both 3.5" & 5.25" disks, except the 1988 Christmas Card, Astro Chicken & Fun Seeker's Guide, which of course were public domain.

All the games listed are disk versions unless noted otherwise.

SCI1 games were released as two versions: 16 color EGA and 256 color VGA versions. The 16 color versions are a lot "uglier" and also smaller in size, compared to their 256 color counterparts. This was done for people with CGA/EGA/TANDY video cards and a low-memory setup. SCI11 ended this tradition by adding a EGA graphics driver.

SCI2, SCI2.1, and SCI3 collectively are often referred to as SCI32 since the released original interpreters were 32-bit executables.

 

== SCI0 (early) ==

{| class="wikitable sortable" width="800"
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[King's Quest IV: The Perils of Rosella]]||width="125" align="center"| ||width="165" align="center"|0.000.247||width="75" align="center"| 
|-
| width="435"|[[King's Quest IV: The Perils of Rosella]]||width="125" align="center"| ||width="165" align="center"|0.000.253||width="75" align="center"| 
|-
| width="435"|[[King's Quest IV: The Perils of Rosella]]||width="125" align="center"|1.000.106||width="165" align="center"|0.000.274||width="75" align="center"|1988/9/19
|-
| width="435"|[[King's Quest IV: The Perils of Rosella]]||width="125" align="center"|1.000.111||width="165" align="center"|0.000.274||width="75" align="center"|1988/9/24/
|-
| width="435"|[[Sierra Christmas Card 1988]]||width="125" align="center"| ||width="165" align="center"|0.000.294||width="75" align="center"|1988
|-
| width="435"|[[Leisure Suit Larry Goes Looking for Love (In Several Wrong Places)|Leisure Suit Larry 2]]||width="125" align="center"|1.000.011||width="165" align="center"|0.000.343||width="75" align="center"|1988/10/27
|}

 
== SCI0 (late) ==

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[Police Quest 2: The Vengeance|Police Quest 2]]*||width="125" align="center"|1.001.000||width="165" align="center"|0.000.395||width="75" align="center"|1988/11/26
|-
| width="435"|[[King's Quest IV: The Perils of Rosella|King's Quest IV]]||width="125" align="center"|1.003.006||width="165" align="center"|0.000.409||width="75" align="center"| 
|-
| width="435"|[[Police Quest 2: The Vengeance|Police Quest 2]]||width="125" align="center"|1.001.006||width="165" align="center"|0.000.409||width="75" align="center"|1988/12/14
|-
| width="435"|[[Leisure Suit Larry Goes Looking for Love (In Several Wrong Places)|Leisure Suit Larry 2]]||width="125" align="center"|1.002.000||width="165" align="center"|0.000.409||width="75" align="center"|1989/01/11
|-
| width="435"|[[Police Quest II Demo]]||width="125" align="center"| ||width="165" align="center"|0.000.413||width="75" align="center"| 
|-
| width="435"|[[Astro Chicken]]||width="125" align="center"| ||width="165" align="center"|0.000.453||width="75" align="center"| 
|-
| width="435"|[[Space Quest III: The Pirates of Pestulon|Space Quest III]]||width="125" align="center"|1.0P||width="165" align="center"|0.000.453||width="75" align="center"|1989/03/22
|-
| width="435"|[[Space Quest III Demo]]||width="125" align="center"|1.0A||width="165" align="center"|0.000.453||width="75" align="center"|1989/03/23
|-
| width="435"|[[Space Quest III: The Pirates of Pestulon|Space Quest III]]||width="125" align="center"|1.0U||width="165" align="center"|0.000.453||width="75" align="center"|1989/04/13
|-
| width="435"|[[Police Quest 2: The Vengeance|Police Quest 2]]||width="125" align="center"|1.002.011||width="165" align="center"|0.000.490||width="75" align="center"| 
|-
| width="435"|[[King's Quest IV Demo|King's Quest IV Demo]]||width="125" align="center"| ||width="165" align="center"|0.000.494||width="75" align="center"|1989/6/27
|-
| width="435"|[[King's Quest IV: The Perils of Rosella|King's Quest IV]]||width="125" align="center"|1.006.003||width="165" align="center"|0.000.502||width="75" align="center"|1989/06/12
|-
| width="435"|[[King's Quest IV: The Perils of Rosella|King's Quest IV]]||width="125" align="center"|1.006.004||width="165" align="center"|0.000.502||width="75" align="center"|1989/08/07
|-
| width="435"|[[Fun Seeker's Guide]]||width="125" align="center"|1.02||width="165" align="center"|0.000.506||width="75" align="center"| 
|-
| width="435"|[[Hoyle Official Book of Games, Volume 1]]||width="125" align="center"|1.000.113 (?)||width="165" align="center"|0.000.530||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 3 Demo|Leisure Suit Larry 3 Demo]]||width="125" align="center"|0.249||width="165" align="center"|0.000.530||width="75" align="center"| 
|-
| width="435"|[[Hero's Quest: So You Want to Be a Hero|Hero's Quest]]||width="125" align="center"|1.000||width="165" align="center"|0.000.566||width="75" align="center"| 
|-
| width="435"|[[Hoyle Official Book of Games, Volume 2: Solitaire|Hoyle Official Book of Games, Volume 2]]||width="125" align="center"|1.000.011||width="165" align="center"|0.000.572||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 3: Passionate Patti in Pursuit of the Pulsating Pectorals|Leisure Suit Larry 3]]||width="125" align="center"|1.003||width="165" align="center"|0.000.572||width="75" align="center"|1989/10/27
|-
| width="435"|[[Leisure Suit Larry 3: Passionate Patti in Pursuit of the Pulsating Pectorals|Leisure Suit Larry 3]]||width="125" align="center"|1.021||width="165" align="center"|0.000.572||width="75" align="center"|1990/01/27
|-
| width="435"|[[Hero's Quest: So You Want to Be a Hero|Hero's Quest]]||width="125" align="center"|1.102||width="165" align="center"|0.000.629||width="75" align="center"| 
|-
| width="435"|[[Quest for Glory I|Quest for Glory I ]]**|| width="125" align="center"|1.200||width="165" align="center"|0.000.629||width="75" align="center"| 
|-
| width="435"|[[Colonel's Bequest, The|Colonel's Bequest, The]]||width="125" align="center"|1.000.046||width="165" align="center"|0.000.631||width="75" align="center"| 
|-
| width="435"|[[Code-Name: ICEMAN]]||width="125" align="center"|1.023||width="165" align="center"|0.000.668||width="75" align="center"| 
|-
| width="435"|[[Conquests of Camelot Demo]]||width="125" align="center"| ||width="165" align="center"|0.000.668||width="75" align="center"|1990/03/17
|-
| width="435"|[[Hoyle Official Book of Games, Volume 1]]||width="125" align="center"|1.000.115||width="165" align="center"|0.000.668||width="75" align="center"|1990
|-
| width="435"|[[Conquests of Camelot|Conquests of Camelot]]||width="125" align="center"|1.001.000||width="165" align="center"|0.000.685||width="75" align="center"| 
|-
| width="435"|[[Code-Name: ICEMAN]]|| width="125" align="center"|1.033||width="165" align="center"|0.000.685||width="75" align="center"| 
|-
| width="435"|[[Code-Name: ICEMAN Demo]]|| width="125" align="center"| ||width="165" align="center"|0.000.685||width="75" align="center"|1990/06/05
|-
| width="435"|[[Mixed-Up Mother Goose SCI]]||width="125" align="center"|1.011||width="165" align="center"|0.000.685||width="75" align="center"| 
|-
| width="435"|[[Hero's Quest Demo]]||width="125" align="center"| ||width="165" align="center"|0.000.685||width="75" align="center"|1990/06/05
|-
| width="435"|[[Space Quest III: The Pirates of Pestulon|Space Quest III]]||width="125" align="center"|1.018||width="165" align="center"|0.000.685||width="75" align="center"| 
|}

<nowiki>*</nowiki>   QA file claims int. ver 0.000.397<br/>
<nowiki>**</nowiki> Original SCI0 re-release of Hero's Quest under another name

0.000.629 (QfG1) - first interpreter version that supported kGetTime(2 and 3)<br/>
0.000.668 (Codename: ICEMAN) - first interpreter version that used a different mod implementation

 

== SCI01 ==

{| class="wikitable sortable" width="800"
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[King's Quest I: The Quest for the Crown (SCI remake)|King's Quest I SCI remake]]||width="125" align="center"|1.000.051||width="165" align="center"|S.old.010||width="75" align="center"| 
|-
| width="435"|[[King's Quest I SCI Demo|King's Quest I SCI remake demo]]||width="125" align="center"| ||width="165" align="center"|S.old.010||width="75" align="center"|1990/09/19
|-
| width="435"|[[Space Quest III: The Pirates of Pestulon|Space Quest III]] (Ger./Eng.)||width="125" align="center"|1.052||width="165" align="center"|S.old.114||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 3: Passionate Patti in Pursuit of the Pulsating Pectorals|Leisure Suit Larry 3]] (Fr./Eng.)||width="125" align="center"|1.050||width="165" align="center"|S.old.123||width="75" align="center"| 
|-
| width="435"|[[Quest for Glory I: So You Want to Be a Hero (EGA)|Quest for Glory I]] (Japanese/Eng. PC-98)||width="125" align="center"|1.000.006||width="165" align="center"|S.old.201||width="75" align="center"| 
|}

 
== SCI1 (EGA) ==

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[Quest for Glory II: Trial by Fire|Quest for Glory II]]||width="125" align="center"|1.000||width="165" align="center"|1.000.041||width="75" align="center"| 
|-
| width="435"|[[Quest for Glory II Demo|Quest for Glory II Demo]]||width="125" align="center"| ||width="165" align="center"|1.000.046||width="75" align="center"| 
|-
| width="435"|[[Quest for Glory II: Trial by Fire|Quest for Glory II]]||width="125" align="center"|1.102||width="165" align="center"|1.000.072||width="75" align="center"| 
|-
| width="435"|[[Quest for Glory II: Trial by Fire|Quest for Glory II]]||width="125" align="center"|1.105||width="165" align="center"|1.000.072||width="75" align="center"| 
|-
| width="435"|[[Quest for Glory II: Trial by Fire|Quest for Glory II (SCIV.OLD)]]||width="125" align="center"|1.105||width="165" align="center"|1.000.087||width="75" align="center"| 
|}

 
== SCI1 (early) ==

{| class="wikitable sortable" width="800"
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[King's Quest V: Absence Makes The Heart Go Yonder|King's Quest V]] VGA||width="125" align="center"|0.000.051||width="165" align="center"|1.000.060||width="75" align="center"| 
|-
| width="435"|[[King's Quest V: Absence Makes The Heart Go Yonder|King's Quest V]] VGA||width="125" align="center"|0.000.062||width="165" align="center"|1.000.060||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 1 VGA Demo|Leisure Suit Larry VGA Demo]]||width="125" align="center"| ||width="165" align="center"|1.000.084||width="75" align="center"| 
|-
| width="435"|[[Mixed-Up Fairy Tales|Mixed-Up Fairy Tales VGA]]||width="125" align="center"|1.000||width="165" align="center"|1.000.145||width="75" align="center"| 
|-
| width="435"|[[Christmas Card 1990 - The Seasoned Professional (EGA)|1990 Christmas Greeting Card EGA]]||width="125" align="center"| ||width="165" align="center"|1.000.172||width="75" align="center"|1990
|-
| width="435"|[[Christmas Card 1990 - The Seasoned Professional (VGA)|1990 Christmas Greeting Card VGA]]||width="125" align="center"| ||width="165" align="center"|1.000.174||width="75" align="center"|1990
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV]] VGA||width="125" align="center"|1.052||width="165" align="center"|1.000.753||width="75" align="center"| 
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV]] VGA||width="125" align="center"|1.1||width="165" align="center"|1.000.753||width="75" align="center"| 
|}

 

== SCI1 (middle) ==

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[Leisure Suit Larry 5 Demo|Leisure Suit Larry 5 Demo]]||width="125" align="center"| ||width="165" align="center"|1.000.181||width="75" align="center"| 
|-
| width="435"|[[Conquests of the Longbow Demo|Conquests of the Longbow Demo]]||width="125" align="center"|0.004||width="165" align="center"|1.000.181||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 1: In the Land of the Lounge Lizards|Leisure Suit Larry VGA remake]] (no copy protection)||width="125" align="center"|2.0||width="165" align="center"|1.000.510||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 1: In the Land of the Lounge Lizards|Leisure Suit Larry VGA remake]]||width="125" align="center"|2.1||width="165" align="center"|1.000.577||width="75" align="center"| 
|}

 
== SCI1 (late) ==

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[Castle of Dr. Brain Demo|Castle of Dr. Brain Demo]]||width="125" align="center"| ||width="165" align="center"|1.000.005||width="75" align="center"| 
|-
| width="435"|[[Castle of Dr. Brain|Castle of Dr. Brain]] VGA||width="125" align="center"|1.000||width="165" align="center"|1.000.044||width="75" align="center"| 
|-
| width="435"|[[Castle of Dr. Brain|Castle of Dr. Brain]] VGA (Sp./Eng.)||width="125" align="center"|1.004||width="165" align="center"|1.000.068||width="75" align="center"| 
|-
| width="435"|[[Conquests of the Longbow|Conquests of the Longbow]] VGA||width="125" align="center"|1.000||width="165" align="center"|1.000.168||width="75" align="center"| 
|-
| width="435"|[[Conquests of the Longbow|Conquests of the Longbow]] VGA (Ger./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.000.169||width="75" align="center"| 
|-
| width="435"|[[Space Quest I: The Sarien Encounter SCI|Space Quest I VGA Remake]]||width="125" align="center"| ||width="165" align="center"|1.000.181||width="75" align="center"| 
|-
| width="435"|[[Space Quest I: The Sarien Encounter SCI|Space Quest I SCI EGA Remake]]||width="125" align="center"|2.000||width="165" align="center"|1.SQ1.004||width="75" align="center"| 
|-
| width="435"|[[Space Quest I: The Sarien Encounter SCI|Space Quest I SCI VGA Remake]] ''patched''|| width="125" align="center"|2.000||width="165" align="center"|1.SQ1.004||width="75" align="center"| 
|-
| width="435"|[[Space Quest I: The Sarien Encounter SCI|Space Quest I SCI VGA Remake]]||width="125" align="center"|2.000||width="165" align="center"|T.A00.081||width="75" align="center"| 
|-
| width="435"|[[Space Quest I: The Sarien Encounter SCI|Space Quest I SCI VGA Remake]] (Sp./Eng.)||width="125" align="center"|2.000||width="165" align="center"|T.A00.081||width="75" align="center"| 
|-
| width="435"|[[King's Quest V: Absence Makes The Heart Go Yonder|King's Quest V]] VGA (Fr./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.000.784||width="75" align="center"| 
|-
| width="435"|[[King's Quest V: Absence Makes The Heart Go Yonder|King's Quest V]] VGA (Ger./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.000.784||width="75" align="center"| 
|-
| width="435"|[[King's Quest V: Absence Makes The Heart Go Yonder|King's Quest V]] VGA (Sp./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.000.784||width="75" align="center"| 
|-
| width="435"|[[Police Quest 3 Demo|Police Quest 3 Demo]]||width="125" align="center"| ||width="165" align="center"|T.A00.052||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 5: Passionate Patti Does a Little Undercover Work|Leisure Suit Larry 5]] VGA||width="125" align="center"|1.0||width="165" align="center"|T.A00.169||width="75" align="center"|1991/09/11
|-
| width="435"|[[Leisure Suit Larry 5: Passionate Patti Does a Little Undercover Work|Leisure Suit Larry 5]] VGA (Ger./Eng.)||width="125" align="center"|1.0||width="165" align="center"|T.A00.169||width="75" align="center"|1991/11/14
|-
| width="435"|[[Leisure Suit Larry 5: Passionate Patti Does a Little Undercover Work|Leisure Suit Larry 5]] VGA (Sp./Eng.)||width="125" align="center"|1.0||width="165" align="center"|1.LS5.006||width="75" align="center"|1992/04/21
|-
| width="435"|[[Leisure Suit Larry 5: Passionate Patti Does a Little Undercover Work|Leisure Suit Larry 5]] VGA (Fr./Eng.)||width="125" align="center"|1.0||width="165" align="center"|1.ls5.019||width="75" align="center"|1992/01/17
|-
| width="435"|[[Police Quest 3: The Kindred|Police Quest III]] VGA||width="125" align="center"|1.0||width="165" align="center"|T.A00.178||width="75" align="center"| 
|-
| width="435"|[[Police Quest 3: The Kindred|Police Quest III]] VGA (Ger./Eng.)||width="125" align="center"|1.000||width="165" align="center"|T.A00.178||width="75" align="center"| 
|-
| width="435"|[[Police Quest 3: The Kindred|Police Quest III]] VGA (Sp./Eng.)||width="125" align="center"|1.0||width="165" align="center"|1.pq3.021||width="75" align="center"|1993/10/08
|-
| width="435"|[[Ecoquest: The Search for Cetus|EcoQuest]] VGA||width="125" align="center"|1.000||width="165" align="center"|1.ECO.013||width="75" align="center"| 
|-
| width="435"|[[Ecoquest: The Search for Cetus|EcoQuest]] VGA (Fr./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.ECO.013||width="75" align="center"| 
|-
| width="435"|[[Ecoquest: The Search for Cetus|EcoQuest]] VGA (Sp./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.ECO.013||width="75" align="center"| 
|-
| width="435"|[[Mixed-Up Fairy Tales Demo|Mixed-Up Fairy Tales Demo]]||width="125" align="center"| ||width="165" align="center"|FAIRY.003||width="75" align="center"| 
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV]] VGA (Ger./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.SQ4.030||width="75" align="center"| 
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Leisure Suit Larry VGA remake]] (Sp./Eng.)||width="125" align="center"|1.0||width="165" align="center"|1.SQ4.057||width="75" align="center"| 
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV]] VGA (It./Eng.)||width="125" align="center"|1.3||width="165" align="center"|1.SQ4.057||width="75" align="center"| 
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV]] VGA (Fr./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.SQ4.057||width="75" align="center"| 
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV]] VGA (Sp./Eng.)||width="125" align="center"|1.000||width="165" align="center"|1.SQ4.057||width="75" align="center"| 
|}

<nowiki>*</nowiki> But NOT cracked, it's just missing from the game's script code

 

== SCI1 (unknown) ==

{| class="wikitable sortable" width="800"
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|[[Ms. Astro Chicken: Flight of the Pullet|Ms. Astro Chicken]]||width="125" align="center"|(x.yyy)||width="165" align="center"|1.000.679||width="75" align="center"| 
|-
| width="435"|[[King's Quest V: Absence Makes The Heart Go Yonder|King's Quest V EGA]]||width="125" align="center"|0.000.055||width="165" align="center"|1.000.058||width="75" align="center"| 
|-
| width="435"|[[King's Quest V: Absence Makes The Heart Go Yonder|King's Quest V EGA]]||width="125" align="center"|0.000.062||width="165" align="center"|1.000.073||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 1: In the Land of the Lounge Lizards|Leisure Suit Larry SCI EGA Remake]]||width="125" align="center"|2.0||width="165" align="center"|1.000.575||width="75" align="center"| 
|-
| width="435"|[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV EGA]]||width="125" align="center"|1.060||width="165" align="center"|1.000.744||width="75" align="center"| 
|-
| width="435"|[[Police Quest 3: The Kindred|Police Quest III EGA]]||width="125" align="center"|1.000||width="165" align="center"|1.pq3.018||width="75" align="center"| 
|-
| width="435"|[[Leisure Suit Larry 5: Passionate Patti Does a Little Undercover Work|Leisure Suit Larry 5 EGA]]||width="125" align="center"|1.0||width="165" align="center"|T.A00.159||width="75" align="center"|1991/09/24
|}

 
== SCI1.1 ==

{| class="wikitable sortable" width="825"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435" |[[Quest for Glory III Demo]]||width="125" align="center"|1.000||width="165" align="center"|1.001.021||width="75" align="center"|1991/06/12
|-
| width="435" |[[Police Quest 1: In Pursuit of the Death Angel VGA|Police Quest I VGA remake]]||width="125" align="center"|2.000||width="165" align="center"|1.001.029||width="75" align="center"| 
|-
| width="435" |[[Crazy Nick's Software Picks: King Graham's Board Game Challenge|King Graham's Board Game Challenge]]||width="125" align="center"|1.00||width="165" align="center"|1.001.029||width="75" align="center"|1992/06/05
|-
| width="435" |[[Crazy Nick's Software Picks: Leisure Suit Larry's Casino|Leisure Suit Larry's Casino]]||width="125" align="center"|1.00||width="165" align="center"|1.001.029||width="75" align="center"|1992/06/05
|-
| width="435" |[[Crazy Nick's Software Picks: Parlor Games with Laura Bow|Parlor Games with Laura Bow]]||width="125" align="center"|1.00||width="165" align="center"|1.001.029||width="75" align="center"|1992/06/05
|-
| width="435" |[[Crazy Nick's Software Picks: Robin Hood's Game of Skill and Chance|Robin Hood's Game of Skill and Chance]]||width="125" align="center"|1.00|| width="165" align="center"|1.001.029||width="75" align="center"|1992/06/05
|-
| width="435" |[[Crazy Nick's Software Picks: Roger Wilco's Spaced Out Game Pack|Roger Wilco's Spaced Out Game Pack]]||width="125" align="center"|1.00||width="165" align="center"|1.001.029||width="75" align="center"|1992/06/05
|-
| width="435" |[[Quest for Glory I VGA Remake Demo|Quest for Glory I VGA remake Demo]]||width="125" align="center"| ||width="165" align="center"|1.001.029||width="75" align="center"| 
|-
| width="435" |[[Mixed-Up Mother Goose VGA|Mixed-Up Mother Goose SCI11 remake]]||width="125" align="center"|2.000||width="165" align="center"|1.001.031||width="75" align="center"| 
|-
| width="435" |[[Quest for Glory III: Wages of War|Quest for Glory III]]||width="125" align="center"|1.0||width="165" align="center"|1.001.050**||width="75" align="center"| 
|-
| width="435" |[[Quest for Glory III: Wages of War|Quest for Glory III]]||width="125" align="center"|1.1||width="165" align="center"|1.001.050**||width="75" align="center"|1992/11/09
|-
| width="435" |[[Island of Dr. Brain]]||width="125" align="center"|1.0||width="165" align="center"|1.001.053||width="75" align="center"|1992/10/27
|-
| width="435" |[[Island of Dr. Brain Demo]]||width="125" align="center"| ||width="165" align="center"|1.001.053||width="75" align="center"| 
|-
| width="435" |[[King's Quest VI: Heir Today, Gone Tomorrow|King's Quest VI]]||width="125" align="center"|1.000||width="165" align="center"|1.001.054||width="75" align="center"| 
|-
| width="435" |[[King's Quest VI: Heir Today, Gone Tomorrow|King's Quest VI]] (Fr.)|| width="125" align="center"|1.000||width="165" align="center"|1.001.054||width="75" align="center"| 
|-
| width="435" |[[King's Quest VI: Heir Today, Gone Tomorrow|King's Quest VI]] (Ger.)||width="125" align="center"|1.000||width="165" align="center"|1.001.054||width="75" align="center"|1992/11/18
|-
| width="435" |[[Season's Greeting Card 1992]] || width="125" align="center"| 1.0||width="165" align="center"|1.001.055||width="75" align="center"|1992/12/1
|-
| width="435" |[[EcoQuest 2 Demo]]||width="125" align="center"|1.000||width="165" align="center"|1.001.055||width="75" align="center"| 
|-
| width="435" |[[King's Quest VI Demo]]||width="125" align="center"|1.000.000||width="165" align="center"|1.001.055||width="75" align="center"| 
|-
| width="435" |[[Pepper's Adventures in Time Demo|Pepper's Adventures in Time Demo]] (non-playable)||width="125" align="center"| ||width="165" align="center"|1.001.060||width="75" align="center"| 
|-
| width="435" |[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV CD]]||width="125" align="center"|1.0||width="165" align="center"|1.001.064||width="75" align="center"| 
|-
| width="435" |[[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV CD]] (Win)||width="125" align="center"|1.0||width="165" align="center"|1.001.064||width="75" align="center"| 
|-
| width="435" |[[EcoQuest: The Search for Cetus|EcoQuest 1 CD]]||width="125" align="center"|1.1||width="165" align="center"|1.001.064||width="75" align="center"| 
|-
| width="435" |[[EcoQuest 2: Lost Secret of The Rainforest|EcoQuest 2]]||width="125" align="center"|1.000.000||width="165" align="center"|1.001.065||width="75" align="center"|1993/02/05
|-
|width="435"|[[Space Quest V: The Next Mutation|Space Quest V]] (reviewer's copy -- debug activated)||width="125" align="center"|0.028||width="165" align="center"|1.001.067||width="75" align="center"|1992/10/22
|-
| width="435" |[[Space Quest V: The Next Mutation|Space Quest V]] (Win)||width="125" align="center"|0.028||width="165" align="center"|1.001.067||width="75" align="center"| 
|-
| width="435" |[[Space Quest V: The Next Mutation|Space Quest V]]||width="125" align="center"|1.03||width="165" align="center"|1.001.068||width="75" align="center"| 
|-
| width="435" |[[Space Quest V: The Next Mutation|Space Quest V]]||width="125" align="center"|1.04||width="165" align="center"|1.001.068||width="75" align="center"| 
|-
| width="435" |[[Space Quest V: The Next Mutation|Space Quest V]](Ger.)||width="125" align="center"|1.04||width="165" align="center"|1.001.068||width="75" align="center"| 
|-
| width="435" |[[Space Quest V: The Next Mutation|Space Quest V]] (It.)||width="125" align="center"|1.000||width="165" align="center"|1.001.068||width="75" align="center"|1993/09/20
|-
| width="435" |[[Space Quest V: The Next Mutation|Space Quest V]] (Fr.)||width="125" align="center"|1.04||width="165" align="center"|1.001.068||width="75" align="center"| 
|-
|width="435"|[[Space Quest V: The Next Mutation|Space Quest V]] (Sp.)||width="125" align="center"|1.000||width="165" align="center"|1.001.068||width="75" align="center"| 
|-
| width="435" |[[Hoyle Classic Card Games]] (Win)||width="125" align="center"|2.000||width="165" align="center"|1.001.069||width="75" align="center"|1993/03/26
|-
| width="435" |[[EcoQuest 2: Lost Secret of The Rainforest|EcoQuest 2]] (Win)||width="125" align="center"|1.000.000||width="165" align="center"|1.001.069||width="75" align="center"|1993/02/05
|-
| width="435" |[[Freddy Pharkas Demo]]||width="125" align="center"|1.000||width="165" align="center"|1.001.069||width="75" align="center"|1993/01/13
|-
|width="435"|[[King's Quest VI: Heir Today, Gone Tomorrow|King's Quest VI CD]] (Win)*||width="125" align="center"|1.034||width="165" align="center"|1.001.069||width="75" align="center"|1994/09/11
|-
|width="435"|[[Dagger of Amon Ra, The|Laura Bow 2 CD]] (Win)||width="125" align="center"|1.1||width="165" align="center"|1.001.069||width="75" align="center"| 
|-
|width="435"|[[Pepper's Adventures in Time]] (Win)||width="125" align="center"|1.000||width="165" align="center"|1.001.069||width="75" align="center"|1993/02/05
|-
|width="435"|[[Pepper's Adventures in Time]]||width="125" align="center"|1.000||width="165" align="center"|1.001.072||width="75" align="center"|1993/02/05
|-
|width="435"|[[Pepper's Adventures in Time Demo]] (playable)||width="125" align="center"| ||width="165" align="center"|1.001.072||width="75" align="center"| 
|-
|width="435"|[[Dagger of Amon Ra, The|Laura Bow 2 CD]]||width="125" align="center"|1.1||width="165" align="center"|1.001.072||width="75" align="center"| 
|-
|width="435"|[[EcoQuest 2: Lost Secret of The Rainforest|EcoQuest 2]] (Fr.)||width="125" align="center"|1.000.000||width="165" align="center"|1.001.081||width="75" align="center"|1994/05/03
|-
|width="435"|[[EcoQuest 2: Lost Secret of The Rainforest|EcoQuest 2]] (test version) (Sp.)||width="125" align="center"|9.999.999||width="165" align="center"|1.001.081||width="75" align="center"|1995/04/20
|-
|width="435"|[[Gabriel Knight 1 Demo]]||width="125" align="center"|000.000.001||width="165" align="center"|1.001.092||width="75" align="center"| 
|-
|width="435"|[[Freddy Pharkas: Frontier Pharmacist|Freddy Pharkas Frontier Pharmacist CD]] (Win)||width="125" align="center"|1.000||width="165" align="center"|1.001.095||width="75" align="center"| 
|-
|width="435"|[[Freddy Pharkas Demo|Freddy Pharkas Demo CD]] (Win)||width="125" align="center"|1.000||width="165" align="center"|1.001.095||width="75" align="center"| 
|-
|width="435"|[[Police Quest 4 Demo]]||width="125" align="center"| ||width="165" align="center"|1.001.096||width="75" align="center"| 
|-
|width="435"|[[Leisure Suit Larry 6: Shape Up or Slip Out!|Leisure Suit Larry 6]]||width="125" align="center"|1.000||width="165" align="center"|1.001.113||width="75" align="center"| 
|-
|width="435"|[[Leisure Suit Larry 6: Shape Up or Slip Out!|Leisure Suit Larry 6]] (Fr.)||width="125" align="center"|1.000||width="165" align="center"|1.001.113||width="75" align="center"| 
|-
|width="435"|[[Leisure Suit Larry 6: Shape Up or Slip Out!|Leisure Suit Larry 6]] (Ger.)||width="125" align="center"|1.000||width="165" align="center"|1.001.113||width="75" align="center"|1994/01/17
|-
|width="435"|[[Leisure Suit Larry 6: Shape Up or Slip Out!|Leisure Suit Larry 6]] (Sp.)||width="125" align="center"|1.000||width="165" align="center"|1.001.113||width="75" align="center"|1994/09/28
|-
|width="435"|[[Leisure Suit Larry 6: Shape Up or Slip Out!|Leisure Suit Larry 6 CD]] (lo-res)||width="125" align="center"|1.000.000||width="165" align="center"|1.001.115||width="75" align="center"| 
|-
|width="435"|[[Freddy Pharkas: Frontier Pharmacist|Freddy Pharkas Frontier Pharmacist CD]]||width="125" align="center"|1.000||width="165" align="center"|1.001.132||width="75" align="center"| 
|-
|width="435"|[[Dagger of Amon Ra, The|Laura Bow 2]]||width="125" align="center"|1.000||width="165" align="center"|2.000.274||width="75" align="center"| 
|-
|width="435"|[[Dagger of Amon Ra, The|Laura Bow 2]] (Fr.)||width="125" align="center"|1.1||width="165" align="center"|2.000.274||width="75" align="center"| 
|-
|width="435"|[[Dagger of Amon Ra, The|Laura Bow 2]] (Sp.)||width="125" align="center"|1.1||width="165" align="center"|2.000.274||width="75" align="center"| 
|-
|width="435"|[[EcoQuest: The Search for Cetus|EcoQuest 1]]||width="125" align="center"|1.10||width="165" align="center"|2.000.286||width="75" align="center"| 
|-
|width="435"|[[Quest for Glory I: So You Want to Be a Hero (VGA)|Quest for Glory I VGA Remake]]||width="125" align="center"|2.000||width="165" align="center"|2.000.411||width="75" align="center"| 
|-
|width="435"|[[Quest for Glory I: So You Want to Be a Hero (VGA)|Quest for Glory I VGA Remake]] ''patched''||width="125" align="center"|2.000||width="165" align="center"|L.rry.021||width="75" align="center"| 
|-
|width="435"|[[Quest for Glory III: Wages of War|Quest for Glory III]] (It.)||width="125" align="center"|1.1||width="165" align="center"|L.rry.083||width="75" align="center"|1993/04/26
|-
|width="435"|[[Quest for Glory III: Wages of War|Quest for Glory III]] (Ger.)||width="125" align="center"|1.1||width="165" align="center"|L.rry.083||width="75" align="center"|1992/11/16
|-
|width="435"|[[Quest for Glory III: Wages of War|Quest for Glory III]] (Fr.)||width="125" align="center"|1.1||width="165" align="center"|L.rry.083||width="75" align="center"|1993/03/03
|-
|width="435"|[[Quest for Glory III: Wages of War|Quest for Glory III]] (Sp.)||width="125" align="center"|1.000.000||width="165" align="center"|L.rry.083||width="75" align="center"|1994/06/30
|-
|width="435"|[[Hoyle Classic Card Games]]||width="125" align="center"|2.000||width="165" align="center"|no version number||width="75" align="center"|1992/09/12
|-
|width="435"|[[Quest for Glory IV Demo|Quest for Glory IV Demo]]||width="125" align="center"|1.000.001||width="165" align="center"|no version number||width="75" align="center"|1993/05/28
|-
|width="435"|[[Freddy Pharkas: Frontier Pharmacist]]||width="125" align="center"|1.000||width="165" align="center"|l.cfs.081||width="75" align="center"| 
|-
|width="435"|[[Freddy Pharkas: Frontier Pharmacist]] (Sp.)||width="125" align="center"|1.000||width="165" align="center"|l.cfs.081||width="75" align="center"|1995/03/30
|-
|width="435"|[[Freddy Pharkas: Frontier Pharmacist]] (Fr.)||width="125" align="center"|1.000||width="165" align="center"|l.cfs.081||width="75" align="center"|1993/08/18
|-
|width="435"|[[Freddy Pharkas: Frontier Pharmacist]] (Ger.)||width="125" align="center"|1.000||width="165" align="center"|l.cfs.081||width="75" align="center"|1993/08/11
|-
|width="435"|[[Slater & Charlie|Slater & Charlie]]||width="125" align="center"|1.000||width="165" align="center"|l.cfs.081||width="75" align="center"|1993/05/19
|-
|width="435"|[[Slater & Charlie Demo|Slater & Charlie Demo]]||width="125" align="center"| ||width="165" align="center"|l.cfs.081||width="75" align="center"| 
|-
|width="435"|[[King's Quest VI: Heir Today, Gone Tomorrow|King's Quest VI CD]]||width="125" align="center"| ||width="165" align="center"|l.cfs.158||width="75" align="center"| 
|-
|width="435"|[[King's Quest VI: Heir Today, Gone Tomorrow|King's Quest VI]] (Sp.)||width="125" align="center"|1.000||width="165" align="center"|l.cfs.158||width="75" align="center"|1994/07/05
|}

<nowiki>*</nowiki>   Version file says: KQ6 version 1.000.00G<br />
<nowiki>**</nowiki> 1.001.050 (QfG3) - first interpreter version that used palette copying instead of merging

 

== SCI2 ==

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435" |[[Gabriel Knight: Sins of the Fathers|Gabriel Knight]]|| width="125" align="center"|1.0||width="165" align="center"|2.000.000||width="75" align="center"|1993/11/22
|-
| width="435" |[[Gabriel Knight: Sins of the Fathers|Gabriel Knight CD]]||width="125" align="center"|01.100.000||width="165" align="center"|2.000.000||width="75" align="center"| 
|-
| width="435" |[[Gabriel Knight: Sins of the Fathers|Gabriel Knight CD]] (Win)||width="125" align="center"|01.100.000||width="165" align="center"|2.000.000||width="75" align="center"| 
|-
| width="435" |[[Gabriel Knight: Sins of the Fathers|Gabriel Knight]] (Fr.)|| width="125" align="center"|1.000||width="165" align="center"|2.000.000||width="75" align="center"|1994/01/14
|-
| width="435" |[[Gabriel Knight: Sins of the Fathers|Gabriel Knight]] (Sp.)||width="125" align="center"|1.000||width="165" align="center"|2.000.000||width="75" align="center"|1995/06/04
|-
| width="435" |[[Gabriel Knight: Sins of the Fathers|Gabriel Knight]] (Ger.)||width="125" align="center"|1.000||width="165" align="center"|2.000.000||width="75" align="center"| 
|-
| width="435" |[[Police Quest: Open Season|Police Quest IV]]|| width="125" align="center"|1.000||width="165" align="center"|2.000.000||width="75" align="center"|1993/11/27
|-
| width="435" |[[Police Quest: Open Season|Police Quest IV]] (Fr.)|| width="125" align="center"|1.000||width="165" align="center"|2.000.000||width="75" align="center"|1994/01/14
|-
| width="435" |[[Police Quest: Open Season|Police Quest IV]] (Ger.)||width="125" align="center"|1.002||width="165" align="center"|2.000.000||width="75" align="center"|1994/02/25
|-
| width="435" |[[Quest for Glory IV: Shadows of Darkness|Quest for Glory IV]]|| width="125" align="center"|1.000.000||width="165" align="center"|2.000.000||width="75" align="center"|1993/12/05
|-
| width="435" |[[Quest for Glory IV: Shadows of Darkness|Quest for Glory IV]]|| width="125" align="center"|1.1||width="165" align="center"|2.000.000||width="75" align="center"|1993/12/14
|}

 
== SCI2.1 (early) ==

These were versions between SCI2 and SCI21. They used a modified SCI2 kernel table. Most of these games maintain the "old school" Sierra graphics. Robot videos were firstly introduced here, in the DOS version of KQ7. VMD videos were not available.

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435" |[[Gabriel Knight 2 Demo]] (Win) || width="145" align="center"| ||width="165" align="center"|2.100.002 (+DEBUG)||width="75" align="center"| 
|-
| width="435" |[[King's Quest VII: The Princeless Bride|King's Quest VII]]|| width="145" align="center"| 1.4||width="165" align="center"|2.100.002||width="75" align="center"|1994/11/17
|-
| width="435" |[[Leisure Suit Larry 6|Leisure Suit Larry 6 CD]] (Hi-Res)|| width="145" align="center"| 1.000.000||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Leisure Suit Larry 6|Leisure Suit Larry 6 CD]] (Hi-Res) (Win)|| width="145" align="center"| 1.000.000||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Police Quest: Open Season|Police Quest IV CD]]|| width="145" align="center"| 1.100.000||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Police Quest: Open Season|Police Quest IV CD]] (Win)|| width="145" align="center"| 1.100.000||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Quest for Glory IV: Shadows of Darkness|Quest for Glory IV CD]]|| width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Quest for Glory IV: Shadows of Darkness|Quest for Glory IV CD]] (Win)|| width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|}

 
== SCI2.1 (middle) ==

These include the finalized kernel function table, also used in SCI3 games. VMD videos were introduced here, and a more heavy usage of robot videos. These games have the "new age" (cartoonish or 3D pre-rendered graphics with actors).

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435" |[[Beast Within: A Gabriel Knight Mystery, The|Gabriel Knight 2]]|| width="145" align="center"| 1.1||width="165" align="center"|2.100.002||width="75" align="center"|1997/03/17
|-
| width="435" |[[Beast Within: A Gabriel Knight Mystery, The|Gabriel Knight 2]] (Win) || width="145" align="center"| 1.1||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Inside The Chest/Behind the Developers' Shield]]|| width="145" align="center"|  ||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Inside The Chest/Behind the Developers' Shield]] (Win) || width="145" align="center"|  ||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[King's Quest VII: The Princeless Bride|King's Quest VII]] (Win only Release) || width="145" align="center"| 1.51||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[King's Quest VII: The Princeless Bride|King's Quest VII]]|| width="145" align="center"| 2.00b||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[King's Quest VII: The Princeless Bride|King's Quest VII]] (Win)|| width="145" align="center"| 2.00b||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[King's Questions]]|| width="145" align="center"|  ||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[King's Questions]] (Win)|| width="145" align="center"|  ||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Mixed-Up Mother Goose Deluxe]] (Win) (Eng./Sp.) || width="145" align="center"|  ||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Phantasmagoria]]|| width="145" align="center"| 1.000.000||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Phantasmagoria]]|| width="145" align="center"| 1.100.000||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Daryl F. Gates' Police Quest SWAT|Police Quest: SWAT]]|| width="145" align="center"| ???||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Police Quest: SWAT Demo]] (Win) || width="145" align="center"| 0.001.200||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Shivers]] (Win only) || width="145" align="center"| 1.02||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Shivers Demo]] (Win) || width="145" align="center"| ||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Space Quest 6]] || width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Space Quest 6 Demo]] || width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Torin's Passage|Torin's Passage]]|| width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Torin's Passage|Torin's Passage]] (Win)|| width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Torin's Passage|Torin's Passage]] (Eng./Fr./Ger./It.) || width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Torin's Passage|Torin's Passage]] (Win) (Eng./Fr./Ger./It.) || width="145" align="center"| 1.0||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Torin's Passage Demo]] || width="145" align="center"| ||width="165" align="center"|2.100.002||width="75" align="center"|1995/08/24
|}

 

== SCI2.1 (late) ==

These are mainly SCI21 game demos of SCI3 games and exhibit behavior where strings and arrays are mixed together (they were cleanly separated in earlier versions).

{| class="wikitable sortable" width="800"
|-
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435" |[[RAMA Demo]]|| width="145" align="center"| ||width="165" align="center"|2.100.002||width="75" align="center"| 
|-
| width="435" |[[Leisure Suit Larry 7 Demo]]|| width="145" align="center"|1.0 Demo|| width="165" align="center"|2.100.002||width="75" align="center"|1996/07/14
|-
| width="435" |[[Lighthouse Demo]]|| width="145" align="center"| 1.00||width="165" align="center"|2.100.002||width="75" align="center"|1995/10/27
|}

== SCI3 ==

{| class="wikitable sortable" width="800"
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435" |[[Leisure Suit Larry 7: Love for Sail!|Leisure Suit Larry 7]]|| width="125" align="center"|1.01||width="165" align="center"|3.000.000||width="75" align="center"| 
|-
| width="435" |[[Leisure Suit Larry 7: Love for Sail!|Leisure Suit Larry 7]]|| width="125" align="center"|1.20||width="165" align="center"|3.000.000||width="75" align="center"| 
|-
| width="435" |[[Lighthouse: The Dark Being|Lighthouse]]|| width="125" align="center"|1.0C||width="165" align="center"|3.000.000||width="75" align="center"|1996/09/09
|-
| width="435" |[[Lighthouse Demo]]|| width="125" align="center"| ||width="165" align="center"|3.000.000||width="75" align="center"|1996/09/09
|-
| width="435" |[[Phantasmagoria: A Puzzle of Flesh|Phantasmagoria II]]|| width="125" align="center"|001.0.000||width="165" align="center"|3.000.000||width="75" align="center"| 
|-
| width="435"|[[RAMA]]||width="125" align="center"|001.000.000||width="165" align="center"|3.000.000||width="75" align="center"|1996/11
|}

 

== Unknown Versions ==

{| class="wikitable sortable" width="800"
! width="435" | Game !! width="125" | Game version !! width="165" | Interpreter version !! width="75" | Date
|-
| width="435"|Hoyle Classic||width="125" align="center"|2.000||width="165" align="center"|"No version Number"*||width="75" align="center"| 
|-
| width="435"|Hoyle's Card Games 3 EGA (SCI1)||width="125" align="center"|1.000||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|Hoyle's Card Games (SCI1)||width="125" align="center"|1.000||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|Hoyle's Card Games 3 Demo (SCI1)||width="125" align="center"| ||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[Colonel's Bequest Demo]]||width="125" align="center"| ||width="165" align="center"|x.yyy.yyy**||width="75" align="center"|1989/09/21
|-
| width="435"|[[Leisure Suit Larry 2 Demo]]||width="125" align="center"| ||width="165" align="center"|x.yyy.yyy**||width="75" align="center"|1989/06/08
|-
| width="435"|[[Jones in the Fast Lane|Jones in the Fast Lane EGA]] (SCI1, with debugger)||width="125" align="center"|1.000.060||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[Jones in the Fast Lane|Jones in the Fast Lane VGA]] (SCI1, with debugger)||width="125" align="center"|1.000.060||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[Jones in the Fast Lane|Jones in the Fast Lane VGA CD]] (SCI1, no debugger)||width="125" align="center"|1.0||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[Jones in the Fast Lane|Jones in the Fast Lane CD]] (SCI1, with debugger)||width="125" align="center"|1.0||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[Jones in the Fast Lane|Jones in the Fast Lane CD]] (Win) (SCI1)||width="125" align="center"|1.0||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[King's Quest V: Absence Makes the Heart Go Yonder|King's Quest V CD]] (SCI1.1)||width="125" align="center"|1.000.052||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[Mixed-Up Mother Goose VGA|Mixed-Up Mother Goose CD]] (SCI1, with debugger)||width="125" align="center"| ||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[Dagger of Amon Ra Demo]] (SCI1.1)***||width="125" align="center"| ||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|-
| width="435"|[[EcoQuest 1 Demo]]||width="125" align="center"| ||width="165" align="center"|x.yyy.yyy**||width="75" align="center"| 
|}

<nowiki>*</nowiki> The version string contains the text: "No version number", it's the same interpreter with both of the games.<br />
<nowiki>**</nowiki> x.yyy.yyy is clearly a standard value, so these game do have different interpreters. The games which share the same interpreter are grouped by separating different versions with a blank line.<br />
<nowiki>***</nowiki> Has some aspect(s) of the SCI1 interpreter.

 
== Not SCI ==

* [[Shivers Two: Harvest of Souls|Shivers Two]] (game and demo): Does not contain SCI scripts, the room logic has been rewritten in native code placed in DLL files
* [[Leisure Suit Larry 6]] (demo): It's a collection of PCX screenshots played with an external player
* [[Space Quest V]] (demo): Uses the Dynamix DGDS engine
* Betrayal in Antara: It has SCI resources for the 2D parts (e.g. inside buildings), but it has its own modified SCI script system, plus a 3D engine
** Some of Antara's "ETC" resources are really [http://doom.wikia.com/wiki/WAD Doom PWAD] files.

 
= Possible Entries =

The following games are '''likely/known''' to exist:

 
== SCI0 ==

* [[Hero's Quest: So You Want to Be a Hero|Hero's Quest]] 1.001
* [[Hoyle Official Book of Games, Volume 1|Hoyle's Book of Games]] (Alt. version, 1.000.104 (1989-08-07))
* Interpreter Version 0.000.396 (LSL2??)

 
== SCI1 ==

* [[Castle of Dr. Brain]] EGA
* [[Castle of Dr. Brain]] VGA (Alt. version (1.1?), with SCI 1.000.068)
* [[Conquests of the Longbow]] EGA
* [[EcoQuest: The Search for Cetus|EcoQuest 1 EGA]]
* [[EcoQuest: The Search for Cetus|EcoQuest 1 VGA]] 1.000 (German)
* [[King's Quest V: Absence Makes the Heart Go Yonder|King's Quest V]] (Other versions?)
* [[Mixed-Up Mother Goose SCI|Mixed-Up Fairy Tales EGA]]
* [[Space Quest IV: Roger Wilco and the Time Rippers|Space Quest IV]] (Beta version released by THG)
* A couple of bilingual versions

 
== SCI11 ==

* [[Space Quest V: The Next Mutation|Space Quest V]] beta #2? (NFO file from the final release mentions it)
* [[Island of Dr. Brain]] (CD version? Probably the same as disk)
* Localized versions

 
== SCI32 ==

* Many localized versions

 
== Unknown ==

* [[Castle of Dr. Brain]] (CD version (if it actually differs))
* [[Leisure Suit Larry|Leisure Suit Larry 1]] (CD version (if it actually differs))

 
= Exclusions =

These games are not AGI or SCI (but are related to Sierra):

 
== [[w:Revolution Software|Revolution Software]] ==

* [[King's Quest VI: Heir Today, Gone Tomorrow|King's Quest VI]] Amiga port ([[w:Virtual Theatre|Virtual Theatre]])

== Other Genre Sierra Games ==

* [[moby:sierras-3-d-helicopter-simulator|3D Helicopter Simulator]] ''Only the demo'' of 3D Helicopter Simulator included in a demo-pack uses AGI. The full game does not.
* [[moby:oils-well|Oil's Well Remake]]
* [[w:Johnny Castaway|Johnny Castaway Screenantics Screensaver]]
* [[w:Leisure Suit Larry#Other_software|The Laffer Utilities]]
* [[w:The Incredible Machine (series)|The Incredible Machine Games]]
* [[w:Lode Runner: The Legend Returns|Lode Runner: The Legend Returns]]

Most of these titles often have the usual file names (RESOURCE, etc.) but they do not use the AGI/SCI interpreter.

 
== Early Sierra CD Titles ==

* [[Leisure Suit Larry 5: Passionate Patti Does a Little Undercover Work|Leisure Suit Larry 5]] (CD Release)

Same as disk version.

 
== Post-1997 Sierra Games ==

* [[w:Gabriel Knight 3: Blood of the Sacred, Blood of the Damned|Gabriel Knight 3]]
* [[w:Quest for Glory V: Dragon Fire|Quest for Glory V]]
* All Sierra games after 1997

After 1997, the SCI engine (and pretty much the adventure genre in general) was abandoned.

 
== Other SCI Games ==

* Most Russian Translations
* Every Chinese Translation
* Every SCI0 Translation
* Certain SCI1+ translations

Most (all?) of these are all hacks. It is unknown about later (SCI32) Russian ones, as some say they were indeed translated and sold officially.

 
== Notes ==

*The Russian SCI games are all (pretty well done) hacks. NEWSCIV is in fact an regular SCI interpreter, but with some intro (Taralej & Jabocrack SoftWare presents) attached to it.

 

[[Category:ToDo Pages]]

SCI Graphic Studio

2025-04-06T12:42:48Z

Andrew Branscom:

#REDIRECT [[SCI Resource Utilities#SCI Graphic Studio 150]]

SCI How To

2025-04-02T22:18:10Z

Andrew Branscom:

*[[Adding Sound Support]]
*[[Adding Troflip's alt Debugging]]
*[[Advanced Said() Strings - Part 2 - Qualifying Adjectives]]
*[[Advanced Said() Strings - Part 3 - Prepositions]]
*[[Automatic Doors]]
*[[Death Handler]]
*[[Determining Location of Mouse Cursor]]
*[[Fixing F2 (ToggleSound) Issue with Companion]]
*[[Generic Keypad Class]]
*[[Get and Use Specific Keyboard Keys]]
*[[How to Keep Your gTheSoundFX from iInterupting gTheMusic]]
*[[Manipulating the Parser - Part 1 - 'Complex' Nouns]]
*[[Manipulating the Parser - Part 2 - Addressing Actors]]
*[[Placing Inventory Descriptions in a Text Resource]]
*[[Resource Corruption from Rebuilding while Running]]
*[[Said() Strings - Comprehensive Examples]]
*[[Taking Inventory Item Away from Character]]
*[[Template Game Bug Fixes]]
*[[Timers]]
*[[Word Suffixes]]

 

[[Category:Examples]]

Taking Inventory Item Away from Character

2025-04-02T22:17:49Z

Andrew Branscom: Andrew Branscom moved page Taking Inventory Item away from character to Taking Inventory Item Away from Character without leaving a redirect

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Taking Inventory Item away from character</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

This is a pretty basic need, perhaps you have given the golden ring to the potion maker or say you eat the spinach dip, either way your character will need to "lose" the inventory item.

This is not covered in any of the tutorials, but has been covered enough at our old home that we all know how to do it, but any new members won't. I figured I had better stick this up here so anyone new to sci won't have to ask. I remember I asked when I first started out.

Anyway, if you have done the tutorial, which if you haven't you should, then you will remember that in order for your character to get an item you needed to use the code

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:get(INV_KEY))</syntaxhighlight>

Now to drop an item either when your character uses it, gives it away, or simply drops it, you could use put instead of get.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:put(INV_KEY))</syntaxhighlight>

in whatever room your character got the item, if you checked to see whether or not gEgo had it before initing it, then the item will reappear there since your character no longer has the item. This may seem strange if the person used the item, or gave it to someone else. Handling these type of instances will require using global variables.

However, with this method in whatever room your character got the item, if you checked to see whether or not gEgo had it before initing it, then the item will reappear there since your character no longer has the item. This may seem strange if the person used the item, or gave it to someone else. Handling these type of instances will require using global variables. In these cases, you really want to test whether an object is in the room or not. An inventory object has an owner property and an ownedBy() method. The way Sierra used to do things was set the owner field to the number of the room the object is in. The (ego get:), (ego put:) and (ego has:) methods simply use this property. You can then test for ownership by doing:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (send anItem:ownedBy(gRoomNumber)) ...)</syntaxhighlight>

This allows items to move around in the game. You can also use objects as owners, if you prefer; indeed, this is already done when an item is in the player's inventory. Additionally, you'd also want to know about:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:put(anItem gRoomNumber))</syntaxhighlight>

It will not take it from inventory and make it appear on the screen. The concept of an inventory item is completely different from the visual representation of it that you might see in the room. You would check to see if the room "owns" the inventory object prior to going ahead and initializing the Prop instance (or whatever) that represents that object in the room. Also, there is a position associated with it when it's in the room, but not in your inventory.

The initial "owner" room is specified in the inventory object:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(instance {Thermal Detonator} of InvI
(properties
said '/detonator'
description "Used for blowing stuff to little bits. It has an impact switch, so in other words...DON'T DROP IT!"
owner 69
view 242
loop 0
cel 12
)
)</syntaxhighlight>

 

[[Category:Inventory]]
[[Category:SCI Inventory]]
[[Category:Actors]]
[[Category:SCI Actors]]
[[Category:Examples]]
[[Category:SCI Examples]]

Automatic Doors

2025-04-02T22:04:58Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Automatic Doors</span><br />
'''By Cloudee1'''</div>

==<br /> Introduction ==

When using Doors and AutoDoors, I am not sure why but things always seemed to go awry. This little tutorial will have a simple Automatic Door (when the player walks near them, they open) up and running with two simple lines of code.

We begin at the very top of the script. We will need to tell the script that we are going to be using an automatic door and to include that functionality. This is done simply by adding in another use command where all of the others are.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(use "autodoor")</syntaxhighlight>

Now that one line is finished, lets go on to the second one, the hard one. Just kidding, there is nothing hard to this method of using automatic doors. The script can now handle AutoDoor instances now, but we are not making one of those, at least not the traditional way. In the rooms init method, where you init() your rooms views and actors, you will need to add in the call that inits the automatic door. the parameters are of the basic type, and I don't think it's necessary to go into detail about them.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(send (AutoDoor:new()):view(211)
setLoop(0)
posn(161 62)
setPri(2)
entranceTo(101)
init())</syntaxhighlight>

At this point, as long as you have added the doors view, and have set up the doors control colors Navy and Green (you won't need a Yellow one because this type of door does not get blocked) for when to open or transport to a new room. We don't need to create an instance or anything else, we are all done coding.

This simple type of door has some limitations though, because there is not an instance name to reference you won't be able to program interactions with it as the code stands now. So keep this in mind. This door can't be locked or blocked, if all you need is a door that opens when you near it, then this will work.

For more advanced needs, such as multiple doors in the same room, see [[Advanced Use of Control Areas]]

 

[[Category:Doors]]
[[Category:Control Areas]]
[[Category:SCI Control Areas]]
[[Category:Props]]
[[Category:SCI Props]]
[[Category:Examples]]
[[Category:SCI Examples]]

SCI How To

2025-04-02T22:02:18Z

Andrew Branscom:

*[[Adding Sound Support]]
*[[Adding Troflip's alt Debugging]]
*[[Advanced Said() Strings - Part 2 - Qualifying Adjectives]]
*[[Advanced Said() Strings - Part 3 - Prepositions]]
*[[Automatic Doors]]
*[[Death Handler]]
*[[Determining Location of Mouse Cursor]]
*[[Fixing F2 (ToggleSound) Issue with Companion]]
*[[Generic Keypad Class]]
*[[Get and Use Specific Keyboard Keys]]
*[[How to Keep Your gTheSoundFX from iInterupting gTheMusic]]
*[[Manipulating the Parser - Part 1 - 'Complex' Nouns]]
*[[Manipulating the Parser - Part 2 - Addressing Actors]]
*[[Placing Inventory Descriptions in a Text Resource]]
*[[Resource Corruption from Rebuilding while Running]]
*[[Said() Strings - Comprehensive Examples]]
*[[Taking Inventory Item away from character]]
*[[Template Game Bug Fixes]]
*[[Timers]]
*[[Word Suffixes]]

 

[[Category:Examples]]

Automatic Doors

2025-04-02T22:01:00Z

Andrew Branscom: Andrew Branscom moved page Automatic doors to Automatic Doors without leaving a redirect

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Automatic doors</span><br />
'''By Cloudee1'''</div>

==<br /> Introduction ==

When using Doors and AutoDoors, I am not sure why but things always seemed to go awry. This little tutorial will have a simple Automatic Door (when the player walks near them, they open) up and running with two simple lines of code.

We begin at the very top of the script. We will need to tell the script that we are going to be using an automatic door and to include that functionality. This is done simply by adding in another use command where all of the others are.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(use "autodoor")</syntaxhighlight>

Now that one line is finished, lets go on to the second one, the hard one. Just kidding, there is nothing hard to this method of using automatic doors. The script can now handle AutoDoor instances now, but we are not making one of those, at least not the traditional way. In the rooms init method, where you init() your rooms views and actors, you will need to add in the call that inits the automatic door. the parameters are of the basic type, and I don't think it's necessary to go into detail about them.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(send (AutoDoor:new()):view(211)
setLoop(0)
posn(161 62)
setPri(2)
entranceTo(101)
init())</syntaxhighlight>

At this point, as long as you have added the doors view, and have set up the doors control colors Navy and Green (you won't need a Yellow one because this type of door does not get blocked) for when to open or transport to a new room. We don't need to create an instance or anything else, we are all done coding.

This simple type of door has some limitations though, because there is not an instance name to reference you won't be able to program interactions with it as the code stands now. So keep this in mind. This door can't be locked or blocked, if all you need is a door that opens when you near it, then this will work.

For more advanced needs, such as multiple doors in the same room, see [[Advanced Use of Control Areas]]

 

[[Category:Doors]]
[[Category:Control Areas]]
[[Category:SCI Control Areas]]
[[Category:Props]]
[[Category:SCI Props]]
[[Category:Examples]]
[[Category:SCI Examples]]

Word Suffixes

2025-04-02T21:47:21Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Word Suffixes</span><br />
'''By Gumby'''</div>

<br />
==<br /> Introduction ==

Here is a complete list of word suffixes, with examples (located in the vocab.901) from the template game. My understanding is that these are used by the parser if the inputted word cannot be matched in the vocab.000. Then it attempts to find a match here, and if it does the parser will use the suffixed word class while parsing. This also explains why there are minimal/no pluralized words in the vocab - you should be able to use the root word & the parse will still work properly.

Note that you cannot use suffixed words in developing Said() strings (however, it may minimize the number of strings you need to write), it just helps out with the user input.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">
(if(Said('take/knife')) // This will respond to both 'take knife' & 'take knives'!
Print("taken")
)
(if(Said('take/knives')) // Will NOT compile, knives is not in the vocab!
Print("taken")
)</syntaxhighlight>

The asterisks in the table corresponds to the word stem (you can think of it as a wildcard of sorts).

{| class="wikitable" width="800"
|-
! class="Blue" | Suffixed<br />ending !! class="Blue" | Suffixed<br />word class !! class="Blue" | Original<br />ending !! class="Blue" | Original<br />word class !! align="left" class="Blue" valign="bottom" | Example
|-
| valign="top" align="center" | *s || valign="top" align="center" | noun || valign="top" align="center" | * || valign="top" align="center" | noun || valign="top" | Dogs – dog
|-
| valign="top" align="center" | *es || valign="top" align="center" | noun || valign="top" align="center" | * || valign="top" align="center" | noun || valign="top" | Bottles – bottle
|-
| valign="top" align="center" | *ies || valign="top" align="center" | noun || valign="top" align="center" | *y || valign="top" align="center" | noun || valign="top" | Bodies – body
|-
| valign="top" align="center" | *men || valign="top" align="center" | noun || valign="top" align="center" | *man || valign="top" align="center" | noun || valign="top" | Firemen – fireman
|-
| valign="top" align="center" | *ves || valign="top" align="center" | noun || valign="top" align="center" | *fe || valign="top" align="center" | noun || valign="top" | Knives – knife
|-
| valign="top" align="center" | *ves || valign="top" align="center" | noun || valign="top" align="center" | *f || valign="top" align="center" | noun || valign="top" | Thieves – thief
|-
| valign="top" align="center" | *people || valign="top" align="center" | noun || valign="top" align="center" | *person || valign="top" align="center" | noun || valign="top" |
|-
| valign="top" align="center" | *ing || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | * || valign="top" align="center" | imperative verb || valign="top" | Knocking – knock
|-
| valign="top" align="center" | *ing || valign="top" align="center" | article || valign="top" align="center" | * || valign="top" align="center" | article || valign="top" |
|-
| valign="top" align="center" | *ing || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | *e || valign="top" align="center" | imperative verb || valign="top" | Waking – wake
|-
| valign="top" align="center" | *ing || valign="top" align="center" | article || valign="top" align="center" | *e || valign="top" align="center" | article || valign="top" |
|-
| valign="top" align="center" | *nning || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | *n || valign="top" align="center" | imperative verb || valign="top" | Beginning – begin
|-
| valign="top" align="center" | *pping || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | *p || valign="top" align="center" | imperative verb || valign="top" | Tripping – trip
|-
| valign="top" align="center" | *mming || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | *m || valign="top" align="center" | imperative verb || valign="top" | Programming – program
|-
| valign="top" align="center" | *tting || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | *t || valign="top" align="center" | imperative verb || valign="top" | Getting – get
|-
| valign="top" align="center" | *rring || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | *r || valign="top" align="center" | imperative verb || valign="top" | Whirring – whir
|-
| valign="top" align="center" | *gging || valign="top" align="center" | imperative verb/noun/adj || valign="top" align="center" | *g || valign="top" align="center" | imperative verb || valign="top" | Bugging – bug
|-
| valign="top" align="center" | *ed || valign="top" align="center" | noun/adj || valign="top" align="center" | * || valign="top" align="center" | imperative verb || valign="top" | Killed – kill
|-
| valign="top" align="center" | *ed || valign="top" align="center" | noun/adj || valign="top" align="center" | *e || valign="top" align="center" | imperative verb || valign="top" | Praised – praise
|-
| valign="top" align="center" | *nned || valign="top" align="center" | noun/adj || valign="top" align="center" | *n || valign="top" align="center" | imperative verb || valign="top" | Scanned – scan
|-
| valign="top" align="center" | *pped || valign="top" align="center" | noun/adj || valign="top" align="center" | *p || valign="top" align="center" | imperative verb || valign="top" | Whipped – whip
|-
| valign="top" align="center" | *mmed || valign="top" align="center" | noun/adj || valign="top" align="center" | *m || valign="top" align="center" | imperative verb || valign="top" | Hemmed – hem
|-
| valign="top" align="center" | *tted || valign="top" align="center" | noun/adj || valign="top" align="center" | *t || valign="top" align="center" | imperative verb || valign="top" | Inputted – input
|-
| valign="top" align="center" | *rred || valign="top" align="center" | noun/adj || valign="top" align="center" | *r || valign="top" align="center" | imperative verb || valign="top" |
|-
| valign="top" align="center" | *gged || valign="top" align="center" | noun/adj || valign="top" align="center" | *g || valign="top" align="center" | imperative verb || valign="top" | Hugged – hug
|-
| valign="top" align="center" | *ied || valign="top" align="center" | noun/adj || valign="top" align="center" | *y || valign="top" align="center" | imperative verb || valign="top" | Empied – empty
|-
| valign="top" align="center" | *er || valign="top" align="center" | noun/adj || valign="top" align="center" | * || valign="top" align="center" | imperative verb/adj || valign="top" | Adjuster – adjust
|-
| valign="top" align="center" | *er || valign="top" align="center" | noun/adj || valign="top" align="center" | *e || valign="top" align="center" | imperative verb/adj || valign="top" | Tickler – tickle
|-
| valign="top" align="center" | *nner || valign="top" align="center" | noun/adj || valign="top" align="center" | *n || valign="top" align="center" | imperative verb/adj || valign="top" | Thin - thinner
|-
| valign="top" align="center" | *pper || valign="top" align="center" | noun/adj || valign="top" align="center" | *p || valign="top" align="center" | imperative verb/adj || valign="top" | Clapper – clap
|-
| valign="top" align="center" | *mmer || valign="top" align="center" | noun/adj || valign="top" align="center" | *m || valign="top" align="center" | imperative verb/adj || valign="top" | Slimmer – slim
|-
| valign="top" align="center" | *tter || valign="top" align="center" | noun/adj || valign="top" align="center" | *t || valign="top" align="center" | imperative verb/adj || valign="top" | Shutter – shut
|-
| valign="top" align="center" | *rrer || valign="top" align="center" | noun/adj || valign="top" align="center" | *r || valign="top" align="center" | imperative verb/adj || valign="top" |
|-
| valign="top" align="center" | *gger || valign="top" align="center" | noun/adj || valign="top" align="center" | *g || valign="top" align="center" | imperative verb/adj || valign="top" | Flagger – flag
|-
| valign="top" align="center" | *ier || valign="top" align="center" | noun/adj || valign="top" align="center" | *y || valign="top" align="center" | imperative verb/adj || valign="top" | Angrier – angry
|-
| valign="top" align="center" | *est || valign="top" align="center" | adjective || valign="top" align="center" | * || valign="top" align="center" | adjective || valign="top" | Sharpest – sharp
|-
| valign="top" align="center" | *est || valign="top" align="center" | adjective || valign="top" align="center" | *e || valign="top" align="center" | adjective || valign="top" |
|-
| valign="top" align="center" | *nnest || valign="top" align="center" | adjective || valign="top" align="center" | *n || valign="top" align="center" | adjective || valign="top" | Thinnest – thin
|-
| valign="top" align="center" | *ppest || valign="top" align="center" | adjective || valign="top" align="center" | *p || valign="top" align="center" | adjective || valign="top" |
|-
| valign="top" align="center" | *mmest || valign="top" align="center" | adjective || valign="top" align="center" | *m || valign="top" align="center" | adjective || valign="top" | Trimmest - trim
|-
| valign="top" align="center" | *ttest || valign="top" align="center" | adjective || valign="top" align="center" | *t || valign="top" align="center" | adjective || valign="top" | Hottest – hot
|-
| valign="top" align="center" | *rrest || valign="top" align="center" | adjective || valign="top" align="center" | *r || valign="top" align="center" | adjective || valign="top" |
|-
| valign="top" align="center" | *ggest || valign="top" align="center" | adjective || valign="top" align="center" | *g || valign="top" align="center" | adjective || valign="top" | Biggest – big
|-
| valign="top" align="center" | *iest || valign="top" align="center" | adjective || valign="top" align="center" | *y || valign="top" align="center" | adjective || valign="top" | Shiniest – shiny
|-
| valign="top" align="center" | *ly || valign="top" align="center" | adjective || valign="top" align="center" | * || valign="top" align="center" | adjective || valign="top" |
|-
| valign="top" align="center" | *y || valign="top" align="center" | adjective || valign="top" align="center" | * || valign="top" align="center" | noun || valign="top" | Watery – water
|-
| valign="top" align="center" | *ish || valign="top" align="center" | adjective || valign="top" align="center" | * || valign="top" align="center" | adjective || valign="top" | Yellowish – yellow
|}

 

[[Category:Suffixes]]
[[Category:SCI Suffixes]]
[[Category:The SCI Parser]]
[[Category:Vocabulary]]
[[Category:SCI Vocabulary]]
[[Category:Examples]]
[[Category:SCI Examples]]

Timers

2025-04-02T21:46:03Z

Andrew Branscom:

Timers

2025-04-02T21:45:51Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt"></span><br />
'''By Lars Skovlund'''</div>

<br />
==<br /> Introduction ==

The Timer class in the template game has gone largely unused, and that is a shame. So here's my attempt at explaining how to use it.

First, there is no need to instantiate an object unless you want to change the timeout later on. The class methods are designed to take care of that. Second, the Timer class works by queuing a script when it expires. I can't recall whether that's in the documentation or not, but it simply means incrementing the current state number by 1 and calling changeState. Third, the only real advantage of the Timer class is its mutator methods. All other functionality is available directly in the Script class, so if your timing needs are simple, you don't need this class at all.

Next, I'll describe the architecture of Timer (and Script, in this regard) objects. There are actually two separate properties devoted for timing: They are called 'cycles' ('cycleCnt' in the Timer class) and 'seconds'. The difference between them is (obviously) their resolution and, consequently, also their range. A cycle in SCI parlance is 1/60th of a second. Thus, the maximum range of a timer if you choose to use the cycle counter is about 18 minutes. If you choose to use the second counter, the range is about 45 hours.

The mutator functions I hinted at above are called setCycles, set, and setReal, respectively. The first one is simple; it takes a cycle count (which you would have to calculate yourself) and starts a new timer with that timeout. You would call it like so:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(Timer:setCycle(RoomScript 30))</syntaxhighlight>

where RoomScript is the script that will be cued when the timer expires. The timeout will be half a second (30/60).

The set method is a bit smarter. It automatically calculates the correct cycle count given a count of seconds, minutes, and hours. This method also adjusts the final count for the currently set game speed, which is not always what you want. And it uses the cycle counter (see above for a description); the real range of the Timer class may vary if you use this method. You would use it like so:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(Timer:set(RoomScript 30))</syntaxhighlight>

for a thirty-second delay.

Finally, there's the setReal method. Like set, it performs all calculations on its own, but it uses the seconds counter, and it does not adjust for game speed. Thus, it is ideal for game events that depend on how much "real time" passes. However, it does not work out of the box due to a typo in the template game. To fix it, find the doit method of the timer class (in Timer.sc), and the line that says:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (not seconds)
CueClient()
)</syntaxhighlight>

Fix the first line so it reads:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (not --seconds)</syntaxhighlight>

and you're all set.

Finally, the cases where you don't need a Timer object. As I've mentioned, the Script class has comparable properties (but no methods) to the Timer class. So you can simply use your room script and the cycles and seconds properties directly, if you are so inclined. This is what Sierra did in most cases; you don't really see the Timer class used much in the games. You would simply do

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(instance RoomScript of Script
(method (changeState newState)
(super:changeState(newState))
(switch (newState)
(case 1
= seconds 15)
(case 2
Print("Time's up!")))))</syntaxhighlight>

When using the Timer class, you would similarly put your initialization code in case 1 above (or in a room's init method).

[[SCIPF:index.php/topic,83.0.html|See feed back about this post on the forums]]

 

[[Category:Timers]]
[[Category:Examples]]

Template Game Bug Fixes

2025-04-02T21:44:52Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Template Game Bug Fixes</span><br /></div>

<br />
==<br /> Setting Inventory views to any cel, loop, or view ==

While trying to set the inventory items instance found in the main script, you will find that no matter how you set the loop or cel, only loop 0 and cel 0 is shown.

To fix this bug, simply change a couple of the default variable values found in the Iitem of InvI class found about halfway down the main script. In the showself method, the default inventory icon variables manually set the cel and loop to 0, just like it's doing. If you would like to be able to set these variables via the instance of the item located at the bottom of the main script, we simply need to change the zeros to loop and cel respectively.

In '''main.sc'''

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">/******************************************************************************/
(class Iitem of InvI
(properties
said 0
description 0
owner 0
view 0
loop 0
cel 0
script 0
)
(method (showSelf)
Print(
description
#title objectName
#icon view loop cel // Changed from: #icon view 0 0
)
)
)
/******************************************************************************/</syntaxhighlight>

'''A small typo in the doit method of timer class'''

This is actually a small snippet from Lars' post on how to use timers. Just in case your looking for a bug free template and you happened to overlook that post I'd thought that I'd copy it to here as well.

----

There's the setReal method. Like set, it
performs all calculations on its own, but it uses the seconds
counter, and it does not adjust for game speed. Thus, it is
ideal for game events that depend on how much "real time" passes.
However, it does not work out of the box due to a typo in the template
game. To fix it, find the doit method of the timer class (in
Timer.sc), and the line that says:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (not seconds)
CueClient()
)</syntaxhighlight>

Fix the first line so it reads:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (not --seconds)</syntaxhighlight>

and you're all set.

 

[[Category:Template Game]]
[[Category:SCI Template Game]]
[[Category:Maintenance]]
[[Category:SCI Maintenance]]
[[Category:Troubleshooting]]
[[Category:SCI Troubleshooting]]
[[Category:Examples]]
[[Category:SCI Examples]]

Taking Inventory Item Away from Character

2025-04-02T21:43:00Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Taking Inventory Item away from character</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

This is a pretty basic need, perhaps you have given the golden ring to the potion maker or say you eat the spinach dip, either way your character will need to "lose" the inventory item.

This is not covered in any of the tutorials, but has been covered enough at our old home that we all know how to do it, but any new members won't. I figured I had better stick this up here so anyone new to sci won't have to ask. I remember I asked when I first started out.

Anyway, if you have done the tutorial, which if you haven't you should, then you will remember that in order for your character to get an item you needed to use the code

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:get(INV_KEY))</syntaxhighlight>

Now to drop an item either when your character uses it, gives it away, or simply drops it, you could use put instead of get.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:put(INV_KEY))</syntaxhighlight>

in whatever room your character got the item, if you checked to see whether or not gEgo had it before initing it, then the item will reappear there since your character no longer has the item. This may seem strange if the person used the item, or gave it to someone else. Handling these type of instances will require using global variables.

However, with this method in whatever room your character got the item, if you checked to see whether or not gEgo had it before initing it, then the item will reappear there since your character no longer has the item. This may seem strange if the person used the item, or gave it to someone else. Handling these type of instances will require using global variables. In these cases, you really want to test whether an object is in the room or not. An inventory object has an owner property and an ownedBy() method. The way Sierra used to do things was set the owner field to the number of the room the object is in. The (ego get:), (ego put:) and (ego has:) methods simply use this property. You can then test for ownership by doing:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (send anItem:ownedBy(gRoomNumber)) ...)</syntaxhighlight>

This allows items to move around in the game. You can also use objects as owners, if you prefer; indeed, this is already done when an item is in the player's inventory. Additionally, you'd also want to know about:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:put(anItem gRoomNumber))</syntaxhighlight>

It will not take it from inventory and make it appear on the screen. The concept of an inventory item is completely different from the visual representation of it that you might see in the room. You would check to see if the room "owns" the inventory object prior to going ahead and initializing the Prop instance (or whatever) that represents that object in the room. Also, there is a position associated with it when it's in the room, but not in your inventory.

The initial "owner" room is specified in the inventory object:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(instance {Thermal Detonator} of InvI
(properties
said '/detonator'
description "Used for blowing stuff to little bits. It has an impact switch, so in other words...DON'T DROP IT!"
owner 69
view 242
loop 0
cel 12
)
)</syntaxhighlight>

 

[[Category:Inventory]]
[[Category:SCI Inventory]]
[[Category:Actors]]
[[Category:SCI Actors]]
[[Category:Examples]]
[[Category:SCI Examples]]

Taking Inventory Item Away from Character

2025-04-02T21:41:38Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Taking Inventory Item away from character</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

This is a pretty basic need, perhaps you have given the golden ring to the potion maker or say you eat the spinach dip, either way your character will need to "lose" the inventory item.

This is not covered in any of the tutorials, but has been covered enough at our old home that we all know how to do it, but any new members won't. I figured I had better stick this up here so anyone new to sci won't have to ask. I remember I asked when I first started out.

Anyway, if you have done the tutorial, which if you haven't you should, then you will remember that in order for your character to get an item you needed to use the code

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:get(INV_KEY))</syntaxhighlight>

Now to drop an item either when your character uses it, gives it away, or simply drops it, you could use put instead of get.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:put(INV_KEY))</syntaxhighlight>

in whatever room your character got the item, if you checked to see whether or not gEgo had it before initing it, then the item will reappear there since your character no longer has the item. This may seem strange if the person used the item, or gave it to someone else. Handling these type of instances will require using global variables.

However, with this method in whatever room your character got the item, if you checked to see whether or not gEgo had it before initing it, then the item will reappear there since your character no longer has the item. This may seem strange if the person used the item, or gave it to someone else. Handling these type of instances will require using global variables. In these cases, you really want to test whether an object is in the room or not. An inventory object has an owner property and an ownedBy() method. The way Sierra used to do things was set the owner field to the number of the room the object is in. The (ego get:), (ego put:) and (ego has:) methods simply use this property. You can then test for ownership by doing:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (send anItem:ownedBy(gRoomNumber)) ...)</syntaxhighlight>

This allows items to move around in the game. You can also use objects as owners, if you prefer; indeed, this is already done when an item is in the player's inventory. Additionally, you'd also want to know about:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(send gEgo:put(anItem gRoomNumber))</syntaxhighlight>

It will not take it from inventory and make it appear on the screen. The concept of an inventory item is completely different from the visual representation of it that you might see in the room. You would check to see if the room "owns" the inventory object prior to going ahead and initializing the Prop instance (or whatever) that represents that object in the room. Also, there is a position associated with it when it's in the room, but not in your inventory.

The initial "owner" room is specified in the inventory object:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(instance {Thermal Detonator} of InvI
(properties
said '/detonator'
description "Used for blowing stuff to little bits. It has an impact switch, so in other words...DON'T DROP IT!"
owner 69
view 242
loop 0
cel 12
)
)</syntaxhighlight>

 

[[Category:Inventory]]
[[Category:Actors]]
[[Category:Examples]]

Resource Corruption from Rebuilding while Running

2025-04-02T21:40:06Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Resource Corruption from Rebuilding while Running</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

Sooner or later it happens to everybody. You code in some room, added in a programControl() and had no way to exit the screen besides the windows button when you actually tested it. Then you were so eager to fix whatever you were testing that you forget to actually close the now minimized Dos window. Then you compiled and then it happens, you hit the rebuild game button. SciStudio does not like this one bit, not one bit at all.

Congratulations you have now corrupted your game all while watching sci studio crash to a something strange happened error. When the dust clears, you spot it. That DOSBox window,hiding out down there in the task bar looking all innocent. Don't worry, your game isn't lost in fact there is a really really simple way to get everything back up and running again.

Enter your game's folder. When you look at the file names, you should notice that there is no resource.001 file, instead there is something named respak.tmp. This weird new file is in fact your resource file and all you need to do to fix it is simply rename it to it's original resource.001

That's it, you have saved your game from the brink of utter destruction. Well it happens to me a lot anyway, and there's nothing so scary as that first time. Hope this makes someone else's first time a little less scary.

Applies to both [[SCI Studio]] and [[SCI Companion]].

 

[[Category:Maintenance]]
[[Category:SCI Maintenance]]
[[Category:Troubleshooting]]
[[Category:SCI Troubleshooting]]

Placing Inventory Descriptions in a Text Resource

2025-04-02T21:38:57Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Placing Inventory Descriptions in a Text Resource</span><br />
'''By Cloudee1''''''</div>

<br />
==<br /> Introduction ==

As your inventory item count grows, the list of instances at the bottom of the main script grows. every addition you make to the main script takes away from every other rooms memory allotment since it itself is used in every room. One way to minimize your impact on the main script and thereby your game overall, is to use text resources to hold all of your inventory items descriptions (and all other text strings but that's personal choice).

In order to do so, you must edit the main script. Remember whenever you edit the main script, you must compile all scripts, both editors have a button just for this. In the main script a hair passed halfway you will find the class Iitem of InvI. the showself method is basically just creating the print tag

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs"> (method (showSelf)
Print( description
#title objectName
#icon view loop cel // you did make this bug update right
)
)</syntaxhighlight>

In order to change the description from the string we are setting it in each item's instance, we want to display the text resource instead so for that we need two numbers. As you may know when printing from a text resource like say number 54 line 23 you would use Print(54 23). So for us to do the same here, we need to pick a text resource to use which all inventory item descriptions will be placed in and I don't see any reasons not to use 0. So we just change the first line of the print statement to read

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">Print(0 description</syntaxhighlight>

Now that that is done, we need to address the description found in each inventory items instance. By default we used "long text strings" but now that the first thing in the print statement is a number, the second thing better be too or something is going to break. The best part is that now the description in each instance simply needs to equal the line it is found on in text resource 0. So they should all look something like this.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(instance {Test Object} of Iitem
(properties
said 'object'
description 10
owner 0
view 800
loop 0
cel 0
script 0
)
)</syntaxhighlight>

Besides making editing them easier since you won't have to recompile all the scripts just for adding a comma, your heap space will last out that much longer for not having preloaded all that miscellaneous junk in there in every room to begin with.

 

[[Category:Inventory]]
[[Category:SCI Inventory]]
[[Category:Text Resources]]
[[Category:SCI Text Resources]]
[[Category:Examples]]
[[Category:SCI Examples]]

Placing Inventory Descriptions in a Text Resource

2025-04-02T21:38:41Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt"></span><br />
'''By Cloudee1''''''</div>

<br />
==<br /> Introduction ==

As your inventory item count grows, the list of instances at the bottom of the main script grows. every addition you make to the main script takes away from every other rooms memory allotment since it itself is used in every room. One way to minimize your impact on the main script and thereby your game overall, is to use text resources to hold all of your inventory items descriptions (and all other text strings but that's personal choice).

In order to do so, you must edit the main script. Remember whenever you edit the main script, you must compile all scripts, both editors have a button just for this. In the main script a hair passed halfway you will find the class Iitem of InvI. the showself method is basically just creating the print tag

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs"> (method (showSelf)
Print( description
#title objectName
#icon view loop cel // you did make this bug update right
)
)</syntaxhighlight>

In order to change the description from the string we are setting it in each item's instance, we want to display the text resource instead so for that we need two numbers. As you may know when printing from a text resource like say number 54 line 23 you would use Print(54 23). So for us to do the same here, we need to pick a text resource to use which all inventory item descriptions will be placed in and I don't see any reasons not to use 0. So we just change the first line of the print statement to read

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">Print(0 description</syntaxhighlight>

Now that that is done, we need to address the description found in each inventory items instance. By default we used "long text strings" but now that the first thing in the print statement is a number, the second thing better be too or something is going to break. The best part is that now the description in each instance simply needs to equal the line it is found on in text resource 0. So they should all look something like this.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(instance {Test Object} of Iitem
(properties
said 'object'
description 10
owner 0
view 800
loop 0
cel 0
script 0
)
)</syntaxhighlight>

Besides making editing them easier since you won't have to recompile all the scripts just for adding a comma, your heap space will last out that much longer for not having preloaded all that miscellaneous junk in there in every room to begin with.

 

[[Category:Inventory]]
[[Category:SCI Inventory]]
[[Category:Text Resources]]
[[Category:SCI Text Resources]]
[[Category:Examples]]
[[Category:SCI Examples]]

Manipulating the Parser - Part 2 - Addressing Actors

2025-04-02T21:37:37Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Manipulating the Parser - Part 2 - Addressing Actors</span><br />
'''By Gumby'''</div>

<br />
==<br /> Overview ==

Built on 'Manipulating the Parser - Part 1' we now will add support for addressing other actors in the game, usually in the form of giving them commands, like 'troll, put the axe on the ground'

==<br /> Problem ==

Since the built-in parser only splits an input into 3 different parts in a Said() string (Ex: 'put the axe on the ground' would create a Said() string of 'put/axe/ground') it does give us enough to direct the command at an actor/individual (in our case, the troll)

==<br /> Quick solution run-down ==

Using our 'preprocessing' functionality on the user input from Part 1, we will check the input string & see if an actor is the first token. If it is, we will set the actor variable & strip it from the input string, allowing the parser to handle the rest. Then we can put in some additional smarts at the time we evaluate the input & direct it to the actor in question. If no actor is referenced we will default the actor to the 'player'.

==<br /> Step-By-Step ==

: 1. Create a new text resource file & put all the actors of the game in it
Examples: graham, troll, thief, grue

: 2. In the game.sh file, define a new constant ACTORS_TEXT and assign it the number corresponding to your text resource file above. Then create a constant for each actor, corresponding to it's location in the text resource. Example:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs"> ...
(define COMPLEXNOUN_TEXT 0) // Text.000 - from Part 1
(define ACTORS_TEXT 1) // Text.001

(define ACTOR_PLAYER 0) // Actor in position 0 of the actors text resource (Text.001)
(define ACTOR_TROLL 1) // Actor in position 1 of the actors text resource (Text.001)
(define ACTOR_THIEF 2) // Actor in position 2 of the actors text resource (Text.001)
(define ACTOR_GRUE 3) // Actor in position 3 of the actors text resource (Text.001)</syntaxhighlight>

: 3. Add a new global variable 'gActor' in the Main.sc file (in the 'local' section with the other 'g' variables). Compile it.

: 4. Modify the ManipulateParse.sc file that you created in Part 1, adding the do/while loop for the actor handling

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(procedure public (manipulateParse inputStr pEvent)
(var i, complexNounFull[50], complexNounStripped[50], actor[50], newInputStr) // add the actor variable

/*
do/while loop for handling the complex nouns is here...
*/

// Determine the actor
= gActor ACTOR_PLAYER // set the default actor to the player in case user did not specify an actor at the beginning of the input
= i 0
(do
GetFarText( ACTORS_TEXT i @actor)
(if (containsStr(newInputStr @actor STARTS_WITH))
= gActor i

// Strip out of the actor name from the input string
findAndReplace(newInputStr newInputStr @actor "")

// Strip any leading commas
findAndReplace(newInputStr newInputStr "," "" STARTS_WITH)
)
++i
) while ( > StrLen(@actor) 0)

/*
Parse command is here, at bottom of manipulateParse procedure
*/</syntaxhighlight>

: 5. Don't forget to recompile the ManipulateParse.sc script. You can now use logic like this in your room scripts (or where-ever):

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (== gActor ACTOR_PLAYER)
(if(Said('dance')
// User input: 'dance'
// User input could also be: 'graham, dance'
// User input could also be: 'graham dance' - the user can use the comma or omit it

Print("You don't feel like dancing today...")
)
(if(Said('take/basketofgoodies')
// User input is 'take basket of goodies'

Print("You pick up the goodie basket.")
)
)

(if (== gActor ACTOR_TROLL)
(if(Said('dance')
// User input: 'troll, dance' or 'troll dance'
Print("The troll dances a jig, then with a swift stroke of his axe, removes your head.")
)
(if(Said('take/basketofgoodies')
// Note that we can combine the actor logic with the 'complex' noun logic...
Print("The troll picks up the goodie basket and swings it into your midsection, knocking the wind out of you.")
)
)

// ...etc for each actor that needs handling</syntaxhighlight>

Special note, whenever you compile the main script, compile ALL scripts afterwards otherwise you might run into problems.

 

[[Category:Actors]]
[[Category:SCI Actors]]
[[Category:The Parser]]
[[Category:The SCI Parser]]
[[Category:Examples]]
[[Category:SCI Examples]]

Manipulating the Parser - Part 2 - Addressing Actors

2025-04-02T21:37:20Z

Andrew Branscom: /* Quick solution run-down */

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt"></span><br />
'''By Gumby'''</div>

<br />
==<br /> Overview ==

Built on 'Manipulating the Parser - Part 1' we now will add support for addressing other actors in the game, usually in the form of giving them commands, like 'troll, put the axe on the ground'

==<br /> Problem ==

Since the built-in parser only splits an input into 3 different parts in a Said() string (Ex: 'put the axe on the ground' would create a Said() string of 'put/axe/ground') it does give us enough to direct the command at an actor/individual (in our case, the troll)

==<br /> Quick solution run-down ==

Using our 'preprocessing' functionality on the user input from Part 1, we will check the input string & see if an actor is the first token. If it is, we will set the actor variable & strip it from the input string, allowing the parser to handle the rest. Then we can put in some additional smarts at the time we evaluate the input & direct it to the actor in question. If no actor is referenced we will default the actor to the 'player'.

==<br /> Step-By-Step ==

: 1. Create a new text resource file & put all the actors of the game in it
Examples: graham, troll, thief, grue

: 2. In the game.sh file, define a new constant ACTORS_TEXT and assign it the number corresponding to your text resource file above. Then create a constant for each actor, corresponding to it's location in the text resource. Example:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs"> ...
(define COMPLEXNOUN_TEXT 0) // Text.000 - from Part 1
(define ACTORS_TEXT 1) // Text.001

(define ACTOR_PLAYER 0) // Actor in position 0 of the actors text resource (Text.001)
(define ACTOR_TROLL 1) // Actor in position 1 of the actors text resource (Text.001)
(define ACTOR_THIEF 2) // Actor in position 2 of the actors text resource (Text.001)
(define ACTOR_GRUE 3) // Actor in position 3 of the actors text resource (Text.001)</syntaxhighlight>

: 3. Add a new global variable 'gActor' in the Main.sc file (in the 'local' section with the other 'g' variables). Compile it.

: 4. Modify the ManipulateParse.sc file that you created in Part 1, adding the do/while loop for the actor handling

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(procedure public (manipulateParse inputStr pEvent)
(var i, complexNounFull[50], complexNounStripped[50], actor[50], newInputStr) // add the actor variable

/*
do/while loop for handling the complex nouns is here...
*/

// Determine the actor
= gActor ACTOR_PLAYER // set the default actor to the player in case user did not specify an actor at the beginning of the input
= i 0
(do
GetFarText( ACTORS_TEXT i @actor)
(if (containsStr(newInputStr @actor STARTS_WITH))
= gActor i

// Strip out of the actor name from the input string
findAndReplace(newInputStr newInputStr @actor "")

// Strip any leading commas
findAndReplace(newInputStr newInputStr "," "" STARTS_WITH)
)
++i
) while ( > StrLen(@actor) 0)

/*
Parse command is here, at bottom of manipulateParse procedure
*/</syntaxhighlight>

: 5. Don't forget to recompile the ManipulateParse.sc script. You can now use logic like this in your room scripts (or where-ever):

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (== gActor ACTOR_PLAYER)
(if(Said('dance')
// User input: 'dance'
// User input could also be: 'graham, dance'
// User input could also be: 'graham dance' - the user can use the comma or omit it

Print("You don't feel like dancing today...")
)
(if(Said('take/basketofgoodies')
// User input is 'take basket of goodies'

Print("You pick up the goodie basket.")
)
)

(if (== gActor ACTOR_TROLL)
(if(Said('dance')
// User input: 'troll, dance' or 'troll dance'
Print("The troll dances a jig, then with a swift stroke of his axe, removes your head.")
)
(if(Said('take/basketofgoodies')
// Note that we can combine the actor logic with the 'complex' noun logic...
Print("The troll picks up the goodie basket and swings it into your midsection, knocking the wind out of you.")
)
)

// ...etc for each actor that needs handling</syntaxhighlight>

Special note, whenever you compile the main script, compile ALL scripts afterwards otherwise you might run into problems.

 

[[Category:Actors]]
[[Category:SCI Actors]]
[[Category:The Parser]]
[[Category:The SCI Parser]]
[[Category:Examples]]
[[Category:SCI Examples]]

Manipulating the Parser - Part 2 - Addressing Actors

2025-04-02T21:37:05Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt"></span><br />
'''By Gumby'''</div>

<br />
==<br /> Overview ==

Built on 'Manipulating the Parser - Part 1' we now will add support for addressing other actors in the game, usually in the form of giving them commands, like 'troll, put the axe on the ground'

==<br /> Problem ==

Since the built-in parser only splits an input into 3 different parts in a Said() string (Ex: 'put the axe on the ground' would create a Said() string of 'put/axe/ground') it does give us enough to direct the command at an actor/individual (in our case, the troll)

==<br /> Quick solution run-down ==

Using our 'preprocessing' functionality on the user input from Part 1, we will check the input string & see if an actor is the first token. If it is, we will set the actor variable & strip it from the input string, allowing the parser to handle the rest. Then we can put in some additional smarts at the time we evaluate the input & direct it to the actor in question. If no actor is referenced we will default the actor to the 'player'.

==<br /> Step-By-Step:'''

: 1. Create a new text resource file & put all the actors of the game in it
Examples: graham, troll, thief, grue

: 2. In the game.sh file, define a new constant ACTORS_TEXT and assign it the number corresponding to your text resource file above. Then create a constant for each actor, corresponding to it's location in the text resource. Example:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs"> ...
(define COMPLEXNOUN_TEXT 0) // Text.000 - from Part 1
(define ACTORS_TEXT 1) // Text.001

(define ACTOR_PLAYER 0) // Actor in position 0 of the actors text resource (Text.001)
(define ACTOR_TROLL 1) // Actor in position 1 of the actors text resource (Text.001)
(define ACTOR_THIEF 2) // Actor in position 2 of the actors text resource (Text.001)
(define ACTOR_GRUE 3) // Actor in position 3 of the actors text resource (Text.001)</syntaxhighlight>

: 3. Add a new global variable 'gActor' in the Main.sc file (in the 'local' section with the other 'g' variables). Compile it.

: 4. Modify the ManipulateParse.sc file that you created in Part 1, adding the do/while loop for the actor handling

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(procedure public (manipulateParse inputStr pEvent)
(var i, complexNounFull[50], complexNounStripped[50], actor[50], newInputStr) // add the actor variable

/*
do/while loop for handling the complex nouns is here...
*/

// Determine the actor
= gActor ACTOR_PLAYER // set the default actor to the player in case user did not specify an actor at the beginning of the input
= i 0
(do
GetFarText( ACTORS_TEXT i @actor)
(if (containsStr(newInputStr @actor STARTS_WITH))
= gActor i

// Strip out of the actor name from the input string
findAndReplace(newInputStr newInputStr @actor "")

// Strip any leading commas
findAndReplace(newInputStr newInputStr "," "" STARTS_WITH)
)
++i
) while ( > StrLen(@actor) 0)

/*
Parse command is here, at bottom of manipulateParse procedure
*/</syntaxhighlight>

: 5. Don't forget to recompile the ManipulateParse.sc script. You can now use logic like this in your room scripts (or where-ever):

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if (== gActor ACTOR_PLAYER)
(if(Said('dance')
// User input: 'dance'
// User input could also be: 'graham, dance'
// User input could also be: 'graham dance' - the user can use the comma or omit it

Print("You don't feel like dancing today...")
)
(if(Said('take/basketofgoodies')
// User input is 'take basket of goodies'

Print("You pick up the goodie basket.")
)
)

(if (== gActor ACTOR_TROLL)
(if(Said('dance')
// User input: 'troll, dance' or 'troll dance'
Print("The troll dances a jig, then with a swift stroke of his axe, removes your head.")
)
(if(Said('take/basketofgoodies')
// Note that we can combine the actor logic with the 'complex' noun logic...
Print("The troll picks up the goodie basket and swings it into your midsection, knocking the wind out of you.")
)
)

// ...etc for each actor that needs handling</syntaxhighlight>

Special note, whenever you compile the main script, compile ALL scripts afterwards otherwise you might run into problems.

 

[[Category:Actors]]
[[Category:SCI Actors]]
[[Category:The Parser]]
[[Category:The SCI Parser]]
[[Category:Examples]]
[[Category:SCI Examples]]

Manipulating the Parser - Part 1 - 'Complex' Nouns

2025-04-02T21:35:42Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Manipulating the Parser - Part 1 - 'Complex' Nouns</span><br />
'''By Gumby'''</div>

<br />
==<br /> Introduction ==

Update: The handling of a 'complex' noun can (in fact) be handled correctly with the parser by making each word involved a noun & utilizing the semantic operator. See the Said() string documentation for more details.

'''Overview:'''<br />
When it comes to extremely complicated user input I have resorted to circumventing the parser. The techniques implemented here should work for number of oddball problems you may run across while working with the parser.

'''Problem:'''<br />
Let's first look at the problem with 'complex' nouns. There is no way to implement the user input command of 'take basket of goodies', the problem lying with treating 'basket of goodies' as a single noun so that we can successfully parse it.

'''Quick solution run-down:'''<br />
We will create a new noun in the vocabulary for 'basket of goodies', but we cannot have spaces in our word. Therefore, we will simply remove all whitespace between the words, resulting in 'basketofgoodies'. Upon each user input we will search for the phrase 'basket of goodies' and replace it with 'basketofgoodies'. In all of our coding we will now be able to use our new concatenated word just like any other 'simple' noun.

'''Step-By-Step:'''<br />

: 1. Create a new text resource file & put the full text of the nouns to be handled there
Examples: basket of goodies, pieces of eight, pile of bodies

: 2. Add new nouns to the vocab.000 file according to what you put in the text resource, without any whitespace
Examples: basketofgoodies, piecesofeight, pileofbodies

: 3. In the game.sh file, define a new constant COMPLEXNOUN_TEXT and assign it the number corresponding to your text resource file above

: 4 Create a new script file called ManipulateParse.sc and include the following code

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(define ANYWHERE 0)
(define STARTS_WITH 1)
(define ENDS_WITH 2)

(include "sci.sh")
(include "game.sh")
/******************************************************************************/
(script 972) // You may need to change the script number if the number is already in use
/******************************************************************************/
(use "main")

(procedure public (manipulateParse inputStr pEvent)
(var i, complexNounFull[50], complexNounStripped[50], newInputStr)

// Copy the input string into a new variable so we don't clobber the original
// (in case the user presses F3 we want to see the what was actually typed)
StrCpy(newInputStr inputStr)

// Do the 'complex' noun substitutions
= i 0
(do
GetFarText( COMPLEXNOUN_TEXT i @complexNounFull)
(if (containsStr(newInputStr @complexNounFull ANYWHERE))
findAndReplace(@complexNounFull @complexNounStripped " " "")
findAndReplace(newInputStr newInputStr @complexNounFull @complexNounStripped)
)
++i
) while ( > StrLen(@complexNounFull) 0)

// Parse our 'new' input string, replacing the original parse
Parse(newInputStr pEvent)
)

(procedure public (findAndReplace sourceStr destStr findStr replaceStr)
(var i, findStrIndex, char, findAndReplaceStr[50])

StrCpy(@findAndReplaceStr "")
= findStrIndex 0
(for (=i 0) (<i StrLen(sourceStr)) (++i)
(if (<> StrAt(sourceStr i) StrAt(findStr findStrIndex) )
Format(char "%c" StrAt(sourceStr i))
StrCat(@findAndReplaceStr char)
= findStrIndex 0
) (else
(while (== StrAt(sourceStr (+ i findStrIndex)) StrAt(findStr findStrIndex) and < findStrIndex StrLen(findStr))
++findStrIndex
)
(if (== findStrIndex StrLen(findStr))
StrCat(@findAndReplaceStr replaceStr)
= i (+ i (- findStrIndex 1))
= findStrIndex 0
) (else
Format(char "%c" StrAt(sourceStr i))
StrCat(@findAndReplaceStr char)
= findStrIndex 0
)
)
)
StrCpy(destStr @findAndReplaceStr)
)

(procedure public (containsStr sourceStr findStr matchType)
(var i, findStrIndex)

= findStrIndex 0
(for (=i 0) (<i StrLen(sourceStr)) (++i)
(if (== StrAt(sourceStr i) StrAt(findStr findStrIndex) )
(while (== StrAt(sourceStr (+ i findStrIndex)) StrAt(findStr findStrIndex) and < findStrIndex StrLen(findStr))
++findStrIndex
)
(if(== findStrIndex StrLen(findStr))
return TRUE
) (else
= findStrIndex 0
)
)
(if (== matchType STARTS_WITH)
return FALSE
)
)
return FALSE
)</syntaxhighlight>

: 5. Add the following code into the User.sc script
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(use "ManipulateParse") // add this near the top

// Then find this code block below & insert the line for the 'manipulateParse' procedure call
(if( (self:getInput(pEvent)) and Parse(@inputStr pEvent))
manipulateParse(@inputStr pEvent)
(send pEvent:type(evSAID))
(self:said(pEvent))
)</syntaxhighlight>

: 6. Don't forget to recompile the User.sc & ManipulateParse.sc scripts. You can now use logic like this in your room scripts (or where-ever):
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs"> (if(Said('move/pileofbodies'))
Print("Probably better to just leave those poor souls alone."
)
(if(Said('eat/basketofgoodies'))
Print("You eat the basket of goodies, and promptly toss your cookies!")
)
(if(Said('take/piecesofeight'))
Print("You pick up the pieces of eight without dropping a single one...")
)</syntaxhighlight>

 

[[Category:Nouns]]
[[Category:SCI Nouns]]
[[Category:Vocabulary]]
[[Category:SCI Vocabulary]]
[[Category:The Parser]]
[[Category:The SCI Parser]]
[[Category:Examples]]
[[Category:SCI Examples]]

SCI How To

2025-04-02T21:34:42Z

Andrew Branscom:

*[[Adding Sound Support]]
*[[Adding Troflip's alt Debugging]]
*[[Advanced Said() Strings - Part 2 - Qualifying Adjectives]]
*[[Advanced Said() Strings - Part 3 - Prepositions]]
*[[Automatic doors]]
*[[Death Handler]]
*[[Determining Location of Mouse Cursor]]
*[[Fixing F2 (ToggleSound) Issue with Companion]]
*[[Generic Keypad Class]]
*[[Get and Use Specific Keyboard Keys]]
*[[How to Keep Your gTheSoundFX from iInterupting gTheMusic]]
*[[Manipulating the Parser - Part 1 - 'Complex' Nouns]]
*[[Manipulating the Parser - Part 2 - Addressing Actors]]
*[[Placing Inventory Descriptions in a Text Resource]]
*[[Resource Corruption from Rebuilding while Running]]
*[[Said() Strings - Comprehensive Examples]]
*[[Taking Inventory Item away from character]]
*[[Template Game Bug Fixes]]
*[[Timers]]
*[[Word Suffixes]]

 

[[Category:Examples]]

How to Keep Your gTheSoundFX from iInterupting gTheMusic

2025-04-02T21:33:56Z

Andrew Branscom: Andrew Branscom moved page How to keep your gTheSoundFX from interupting gTheMusic to How to Keep Your gTheSoundFX from iInterupting gTheMusic without leaving a redirect

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">How to Keep Your gTheSoundFX from iInterupting gTheMusic</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

In the first room of my game has music playing as well as a repetitive SoundFX (water dripping) and every time it played it interfered with the music. First I tried playing around with a priority property, but nothing ever really came of that. Then I figured I would just make a timer and count down to when the music should be over but I didn't want to add any more than necessary to my main script. It turns out that both instances have a state property built in. Then it just became a matter of checking for 0.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if(== (send gTheMusic:state()) 0) (send gTheSoundFX:number(15)loop(1)play()))</syntaxhighlight>

With this the soundfFX will no longer play until after the music has finished.

 

[[Category:Audio]]
[[Category:SCI Audio]]
[[Category:Troubleshooting]]
[[Category:SCI Troubleshooting]]
[[Category:Examples]]
[[Category:SCI Examples]]

How to Keep Your gTheSoundFX from iInterupting gTheMusic

2025-04-02T21:33:34Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">How to Keep Your gTheSoundFX from iInterupting gTheMusic</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

In the first room of my game has music playing as well as a repetitive SoundFX (water dripping) and every time it played it interfered with the music. First I tried playing around with a priority property, but nothing ever really came of that. Then I figured I would just make a timer and count down to when the music should be over but I didn't want to add any more than necessary to my main script. It turns out that both instances have a state property built in. Then it just became a matter of checking for 0.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(if(== (send gTheMusic:state()) 0) (send gTheSoundFX:number(15)loop(1)play()))</syntaxhighlight>

With this the soundfFX will no longer play until after the music has finished.

 

[[Category:Audio]]
[[Category:SCI Audio]]
[[Category:Troubleshooting]]
[[Category:SCI Troubleshooting]]
[[Category:Examples]]
[[Category:SCI Examples]]

Get and Use Specific Keyboard Keys

2025-04-02T21:32:00Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Get and Use Specific Keyboard Keys</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

''This is a real old post that I dug up from the depths of Mega-Tokyo. I'm in the middle of a big mini game kick and in order to expand control options I am looking into using keys. But I wasn't sure how to check for the keys pressed because I didn't know the values to check for. This old post first describes how to check for the pressed buttons if they have been declared in the Keys.sh file and the second little bit of code describes how to output the value of a key pressed such that you wouldn't need to edit the keys file to check for it. So you can just go check for one anytime you need a keys value.''

==INTERCEPTING KEYBOARD AND MOUSE EVENTS==

For this demonstration, Ego will change into Brian if the player presses B (capital) and back to Ego when E (capital) is pressed.

Add Brian as a view as described in the Tutorial Chapter 19 (Resource->Add Sample->View->Brian and save it as view number 1.

In the instance of RoomScript add the following code:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">(instance RoomScript of Script
(properties)
(method (handleEvent pEvent)
(var str) //Local variable
(super:handleEvent(pEvent))

(switch( (send pEvent:type) )
(case evKEYBOARD
(if(== (send pEvent:message) KEY_B ) //Check if B was pressed
(send gEgo:view(1)) //switch to Brian
(send pEvent:claimed(TRUE))
)//if B

(if(== (send pEvent:message) KEY_E ) //Check if E was pressed
(send gEgo:view(0)) //switch to Ego
(send pEvent:claimed(TRUE))
)//if
)//evKEYBOARD

//For fun intercept the Mouse event as well
(case evMOUSEBUTTON
(Print("You pressed a Mouse Button!"))
)//evMOUSEBUTTON
)//switch
)//method
)//instance</syntaxhighlight>

The code: send pEvent:claimed(TRUE)): specified whether the event object can be used; in this case the :Said: command will ignore the event when the player presses either a B or E.

Compile and test. Ego will be transformed into Brian if you press a B and back to Ego if you press an E. If it does not work, the values may not be declared in the Keys.sh file. Open the file (..\SciStudio\include\Keys.sh) to view the defined values. You may want to expand the list with the lower case values (a=$61,..z=7a). If you want to trap other values, you can view the value of the key code by adding the following code just below the :case evKEYBOARD: statement:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci" class="cs">=str ""
(Format(str "str=%x" (send pEvent:message)))
(Print(str))</syntaxhighlight>

Test by pressing Ctrl-k. The value should be $0b. You can add the value in the Keys.sh file or using it directly in the statement (if(== (send pEvent:message) $0b) ext

 

[[Category:Keyboard]]
[[Category:I/O]]
[[Category:Examples]]
[[Category:SCI Examples]]

SCI How To

2025-04-02T21:31:22Z

Andrew Branscom:

*[[Adding Sound Support]]
*[[Adding Troflip's alt Debugging]]
*[[Advanced Said() Strings - Part 2 - Qualifying Adjectives]]
*[[Advanced Said() Strings - Part 3 - Prepositions]]
*[[Automatic doors]]
*[[Death Handler]]
*[[Determining Location of Mouse Cursor]]
*[[Fixing F2 (ToggleSound) Issue with Companion]]
*[[Generic Keypad Class]]
*[[Get and Use Specific Keyboard Keys]]
*[[How to keep your gTheSoundFX from interupting gTheMusic]]
*[[Manipulating the Parser - Part 1 - 'Complex' Nouns]]
*[[Manipulating the Parser - Part 2 - Addressing Actors]]
*[[Placing Inventory Descriptions in a Text Resource]]
*[[Resource Corruption from Rebuilding while Running]]
*[[Said() Strings - Comprehensive Examples]]
*[[Taking Inventory Item away from character]]
*[[Template Game Bug Fixes]]
*[[Timers]]
*[[Word Suffixes]]

 

[[Category:Examples]]

Generic Keypad Class

2025-04-02T21:30:55Z

Andrew Branscom: Andrew Branscom moved page Generic Keypad class to Generic Keypad Class without leaving a redirect

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Generic Keypad Class</span><br />
'''By Lars Skovlund'''</div>

<br />
==<br /> Introduction ==

Note that I use the ego view for buttons (as I said, I am not a graphic artist). The first the buttons from the left are number buttons, and add the numbers 1, 2 and 3 to the keypad text. The next button cancels, the one after that is backspace, and the last one OK. It would be great if someone would help me make better graphics for the demo code. Instructions are in the documentation. You will also need to add the word 'keypad' to your vocabulary.

Code in the attached file, along with documentation.

[http://sierrahelp.com/download.php?file=Files/SCI/GenericKeypadClass.zip Generic Keypad Class Files]

Lars

The Keypad SCI class<br />
Lars Skovlund<br />
January 17, 2007<br />
 

==1 Introduction==

This is the documentation for the Keypad SCI class, written by Lars Skovlund. I have attempted to make the class as general as possible. Therefore, the class and its descendant DisplayKeypad support arbitrarily long strings of any kind, so it is possible, for instance, to have each button represent a word so the user can construct sentences. The DisplayKeypad class prints the input string somewhere on the screen via the Display kernel call (all parameters are selectable via properties).

The following is a complete feature list for the keypad:

* No keyboard input, for generality reasons.
* Special button functionality, such as enter, backspace and cancel.
* Optionally invokes a script when initially showing the keypad and when the enter button is pressed.
* Optional auto exit mode in which the keypad triggers as soon as the input string reaches its maximum length, as if the user explicitly pressed the enter button.
* Can require a specific number of buttons to be pressed, or accept any number of button presses.
* Can play a sound when a button is pressed.
* Optional text display (DisplayKeypad).
* A background view can be used or not.

==2 Example of use==

===2.1 Declarations===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(local kptxt[5])

(instance myKeyPad of DisplayKeypad
(properties
maxLength 4
autoExit FALSE
script 0
longestText 1 /* one character */
color clBLACK
back clWHITE
x 20
y 160
requireMax TRUE
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key1 of KeypadButton
(properties
x 100
y 100
view 0
loop 0
text "1"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key2 of KeypadButton
(properties
x 120
y 100
view 0
loop 2
text "2"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key3 of KeypadButton
(properties
x 140
y 100
view 0
loop 1
text "3"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key4 of KeypadButton
(properties
x 160
y 100
view 0
loop 5
special KEYPAD_SPECIAL_CANCEL
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key5 of KeypadButton
(properties
x 180
y 100
view 0
loop 6
special KEYPAD_SPECIAL_BKSP
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key6 of KeypadButton
(properties
x 200
y 100
view 0
loop 3
special KEYPAD_SPECIAL_ENTER
)
)</syntaxhighlight>

===2.2 Handling the enter and cancel buttons===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance KeypadScript of Script
(properties)
(method (changeState newState)
(super:changeState(newState))
(switch (newState)
(case KEYPAD_DONE_STATE
((send client:hide(FALSE))
FormatPrint("You typed: %s" @kptxt)))
(case KEYPAD_ERROR_STATE
(FormatPrint("You need to press %d buttons."
(send client:maxLength()))))
)
)
)</syntaxhighlight>

===2.3 Initialization and activation===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(myKeyPad:setScript(KeypadScript) outputString(@kptxt)
init(key1 key2 key3 key4 key5 key6))

(myKeyPad:init() show()) /* The init ensures that the keypad can
be used any number of times. */</syntaxhighlight>

==3 What to draw==

You will need a view consisting of several loops, one for each button. Each loop should contain two cels: The button in its normal and depressed state, respectively. It is important that the cels are ordered in this way; the code depends on it, and you should not set the cel property to anything when declaring KeypadButtons.

If you want a background view you can draw this as a separate loop. Declare it in your code as an instance of the Prop class. Then refer to it in your Keypad instance using the backView property.

==4 Class reference==

===4.1 Keypad class===

'''Superclass: EventHandler'''

This class provides the base functionality for keypads.

====''Methods of the Keypad class:''====

'''(Keypad init: buttons . . . )'''

This function initializes the object, as is the case with every SCI class. In particular, it resets the input string and notifies the controlling script. Buttons is a list of button views (instances of KeypadButton) to include in the keypad.

'''(Keypad show:)'''

Displays the keypad. The player is prevented from moving until the keypad is dismissed.

'''(Keypad hide: doCue)'''

Hides the keypad. DoCue should be set to TRUE if the “enter” button was pressed, FALSE otherwise. When the script is called, the buttons have not yet been removed from the screen. If you want this, your script must explicitly call hide with a FALSE parameter (to avoid infinite recursion)—this is what the example code does, see section 2.2.

'''(Keypad backspace:)'''

Self-explanatory. You will need to override this if you use text of varying lengths for the buttons.

'''(Keypad draw:)'''

'''(Keypad setSize:)'''

Do nothing. They are only here to prevent the game from crashing in certain situations (in particular, restoring the game to a position where the keypad is displayed).

'''(Keypad depress: which)'''

Simulates the pressing of a button. Which refers to an actual instance of KeypadButton.

'''(Keypad setScript: newScript params)'''

Sets the controlling script of the keypad. This script is called once when the keypad is initially displayed and once when the user presses “enter”. It is not called if the user cancels the dialog.

====''Properties of the Keypad class:''====

'''outputString''' Points to the output buffer. Remember to set this at run time, and remember that it must be big enough for anything the player might press. Use a local variable, as shown in section 2.1.

'''maxLength''' Indicates the length of the output buffer.

'''autoExit''' Boolean variable which toggles the “auto exit” mode, described in the introduction.

'''backView''' Points to an instance of Prop which is displayed when the keypad is activated. It is meant to be used for a background, hence the name.

'''backPri''' Indicates the priority of the background. May be omitted; the priority of the buttons is always 1 greater than this value, if specified.

'''btnSound''' Points to an instance of Sound which is played whenever the user presses a button.

'''longestText''' Indicates the length of the longest button text.

'''script''' Indicates the controlling script. Use setScript to set this, never set it directly.

'''state''' Boolean variable. Indicates whether the keypad is currently shown or not.

'''special''' Not used for anything. Works around a chicken-and-egg problem regarding selector names in SCI Studio.

'''requireMax''' Setting this to true makes the keypad require maxLength characters to be filled in. If this requirement is not met when the player presses enter, the attached script executes its keypad error state. You can do whatever you want here, including doing nothing, displaying an error message, or blowing up the universe. The keypad remains functional after the script returns.

;Notes

For the predefined script, three states are predefined. Constants are provided
in the enclosed header file.

===4.2 KeypadButton class===

'''Superclass: Prop'''

This class provides the button views to be used for the keypad; they provide an event handler and a special feed-back interface for the <u>Keypad</u> class. None of the overridden methods are meant to be called directly.

'''''Methods of the KeypadButton class:'''''

'''(KeypadButton init: theClient priority)'''

'''(KeypadButton handleEvent: event)'''

'''''Properties of the KeypadButton class:'''''

'''text''' The text to add when the button is pressed.

'''special''' The special meaning that this button is to have.

'''client''' A pointer to the keypad which “owns” this button. Filled in automatically.

;Notes

Three special button types are provided beside the default, namely enter, backspace and cancel.

===4.3 DisplayKeypad class===

'''Superclass: Keypad'''

This class provides the additional functionality of displaying the current text string at a predetermined position on the screen. All of the listed properties have the same format as those passed to the Display kernel function.

'''''Properties of the DisplayKeypad class:'''''

'''underBits''' stores a handle to the screen area under the text string.

'''x'''

'''y''' Coordinates where the text string is to be displayed.

'''font''' The font to use.

'''color''' The foreground color.

'''back''' The background color.

'''width''' The width to use for wrapping the text, if that should ever be necessary.

'''align''' The alignment to use.

==5 Constant reference==

(define KEYPAD_INIT_STATE 0)<br />
(define KEYPAD_DONE_STATE 1)<br />
(define KEYPAD_ERROR_STATE 2)

(define KEYPAD_SPECIAL_NONE 0)<br />
(define KEYPAD_SPECIAL_ENTER 1)<br />
(define KEYPAD_SPECIAL_BKSP 2)<br />
(define KEYPAD_SPECIAL_CANCEL 3)

 

[[Category:Keyboard]]
[[Category:Classes]]
[[Category:I/O]]
[[Category:Examples]]
[[Category:SCI Examples]]

Generic Keypad Class

2025-04-02T21:30:32Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Generic Keypad Class</span><br />
'''By Lars Skovlund'''</div>

<br />
==<br /> Introduction ==

Note that I use the ego view for buttons (as I said, I am not a graphic artist). The first the buttons from the left are number buttons, and add the numbers 1, 2 and 3 to the keypad text. The next button cancels, the one after that is backspace, and the last one OK. It would be great if someone would help me make better graphics for the demo code. Instructions are in the documentation. You will also need to add the word 'keypad' to your vocabulary.

Code in the attached file, along with documentation.

[http://sierrahelp.com/download.php?file=Files/SCI/GenericKeypadClass.zip Generic Keypad Class Files]

Lars

The Keypad SCI class<br />
Lars Skovlund<br />
January 17, 2007<br />
 

==1 Introduction==

This is the documentation for the Keypad SCI class, written by Lars Skovlund. I have attempted to make the class as general as possible. Therefore, the class and its descendant DisplayKeypad support arbitrarily long strings of any kind, so it is possible, for instance, to have each button represent a word so the user can construct sentences. The DisplayKeypad class prints the input string somewhere on the screen via the Display kernel call (all parameters are selectable via properties).

The following is a complete feature list for the keypad:

* No keyboard input, for generality reasons.
* Special button functionality, such as enter, backspace and cancel.
* Optionally invokes a script when initially showing the keypad and when the enter button is pressed.
* Optional auto exit mode in which the keypad triggers as soon as the input string reaches its maximum length, as if the user explicitly pressed the enter button.
* Can require a specific number of buttons to be pressed, or accept any number of button presses.
* Can play a sound when a button is pressed.
* Optional text display (DisplayKeypad).
* A background view can be used or not.

==2 Example of use==

===2.1 Declarations===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(local kptxt[5])

(instance myKeyPad of DisplayKeypad
(properties
maxLength 4
autoExit FALSE
script 0
longestText 1 /* one character */
color clBLACK
back clWHITE
x 20
y 160
requireMax TRUE
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key1 of KeypadButton
(properties
x 100
y 100
view 0
loop 0
text "1"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key2 of KeypadButton
(properties
x 120
y 100
view 0
loop 2
text "2"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key3 of KeypadButton
(properties
x 140
y 100
view 0
loop 1
text "3"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key4 of KeypadButton
(properties
x 160
y 100
view 0
loop 5
special KEYPAD_SPECIAL_CANCEL
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key5 of KeypadButton
(properties
x 180
y 100
view 0
loop 6
special KEYPAD_SPECIAL_BKSP
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key6 of KeypadButton
(properties
x 200
y 100
view 0
loop 3
special KEYPAD_SPECIAL_ENTER
)
)</syntaxhighlight>

===2.2 Handling the enter and cancel buttons===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance KeypadScript of Script
(properties)
(method (changeState newState)
(super:changeState(newState))
(switch (newState)
(case KEYPAD_DONE_STATE
((send client:hide(FALSE))
FormatPrint("You typed: %s" @kptxt)))
(case KEYPAD_ERROR_STATE
(FormatPrint("You need to press %d buttons."
(send client:maxLength()))))
)
)
)</syntaxhighlight>

===2.3 Initialization and activation===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(myKeyPad:setScript(KeypadScript) outputString(@kptxt)
init(key1 key2 key3 key4 key5 key6))

(myKeyPad:init() show()) /* The init ensures that the keypad can
be used any number of times. */</syntaxhighlight>

==3 What to draw==

You will need a view consisting of several loops, one for each button. Each loop should contain two cels: The button in its normal and depressed state, respectively. It is important that the cels are ordered in this way; the code depends on it, and you should not set the cel property to anything when declaring KeypadButtons.

If you want a background view you can draw this as a separate loop. Declare it in your code as an instance of the Prop class. Then refer to it in your Keypad instance using the backView property.

==4 Class reference==

===4.1 Keypad class===

'''Superclass: EventHandler'''

This class provides the base functionality for keypads.

====''Methods of the Keypad class:''====

'''(Keypad init: buttons . . . )'''

This function initializes the object, as is the case with every SCI class. In particular, it resets the input string and notifies the controlling script. Buttons is a list of button views (instances of KeypadButton) to include in the keypad.

'''(Keypad show:)'''

Displays the keypad. The player is prevented from moving until the keypad is dismissed.

'''(Keypad hide: doCue)'''

Hides the keypad. DoCue should be set to TRUE if the “enter” button was pressed, FALSE otherwise. When the script is called, the buttons have not yet been removed from the screen. If you want this, your script must explicitly call hide with a FALSE parameter (to avoid infinite recursion)—this is what the example code does, see section 2.2.

'''(Keypad backspace:)'''

Self-explanatory. You will need to override this if you use text of varying lengths for the buttons.

'''(Keypad draw:)'''

'''(Keypad setSize:)'''

Do nothing. They are only here to prevent the game from crashing in certain situations (in particular, restoring the game to a position where the keypad is displayed).

'''(Keypad depress: which)'''

Simulates the pressing of a button. Which refers to an actual instance of KeypadButton.

'''(Keypad setScript: newScript params)'''

Sets the controlling script of the keypad. This script is called once when the keypad is initially displayed and once when the user presses “enter”. It is not called if the user cancels the dialog.

====''Properties of the Keypad class:''====

'''outputString''' Points to the output buffer. Remember to set this at run time, and remember that it must be big enough for anything the player might press. Use a local variable, as shown in section 2.1.

'''maxLength''' Indicates the length of the output buffer.

'''autoExit''' Boolean variable which toggles the “auto exit” mode, described in the introduction.

'''backView''' Points to an instance of Prop which is displayed when the keypad is activated. It is meant to be used for a background, hence the name.

'''backPri''' Indicates the priority of the background. May be omitted; the priority of the buttons is always 1 greater than this value, if specified.

'''btnSound''' Points to an instance of Sound which is played whenever the user presses a button.

'''longestText''' Indicates the length of the longest button text.

'''script''' Indicates the controlling script. Use setScript to set this, never set it directly.

'''state''' Boolean variable. Indicates whether the keypad is currently shown or not.

'''special''' Not used for anything. Works around a chicken-and-egg problem regarding selector names in SCI Studio.

'''requireMax''' Setting this to true makes the keypad require maxLength characters to be filled in. If this requirement is not met when the player presses enter, the attached script executes its keypad error state. You can do whatever you want here, including doing nothing, displaying an error message, or blowing up the universe. The keypad remains functional after the script returns.

;Notes

For the predefined script, three states are predefined. Constants are provided
in the enclosed header file.

===4.2 KeypadButton class===

'''Superclass: Prop'''

This class provides the button views to be used for the keypad; they provide an event handler and a special feed-back interface for the <u>Keypad</u> class. None of the overridden methods are meant to be called directly.

'''''Methods of the KeypadButton class:'''''

'''(KeypadButton init: theClient priority)'''

'''(KeypadButton handleEvent: event)'''

'''''Properties of the KeypadButton class:'''''

'''text''' The text to add when the button is pressed.

'''special''' The special meaning that this button is to have.

'''client''' A pointer to the keypad which “owns” this button. Filled in automatically.

;Notes

Three special button types are provided beside the default, namely enter, backspace and cancel.

===4.3 DisplayKeypad class===

'''Superclass: Keypad'''

This class provides the additional functionality of displaying the current text string at a predetermined position on the screen. All of the listed properties have the same format as those passed to the Display kernel function.

'''''Properties of the DisplayKeypad class:'''''

'''underBits''' stores a handle to the screen area under the text string.

'''x'''

'''y''' Coordinates where the text string is to be displayed.

'''font''' The font to use.

'''color''' The foreground color.

'''back''' The background color.

'''width''' The width to use for wrapping the text, if that should ever be necessary.

'''align''' The alignment to use.

==5 Constant reference==

(define KEYPAD_INIT_STATE 0)<br />
(define KEYPAD_DONE_STATE 1)<br />
(define KEYPAD_ERROR_STATE 2)

(define KEYPAD_SPECIAL_NONE 0)<br />
(define KEYPAD_SPECIAL_ENTER 1)<br />
(define KEYPAD_SPECIAL_BKSP 2)<br />
(define KEYPAD_SPECIAL_CANCEL 3)

 

[[Category:Keyboard]]
[[Category:Classes]]
[[Category:I/O]]
[[Category:Examples]]
[[Category:SCI Examples]]

Generic Keypad Class

2025-04-02T21:30:09Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt"></span><br />
'''By Lars Skovlund'''</div>

<br />
==<br /> Introduction ==

Note that I use the ego view for buttons (as I said, I am not a graphic artist). The first the buttons from the left are number buttons, and add the numbers 1, 2 and 3 to the keypad text. The next button cancels, the one after that is backspace, and the last one OK. It would be great if someone would help me make better graphics for the demo code. Instructions are in the documentation. You will also need to add the word 'keypad' to your vocabulary.

Code in the attached file, along with documentation.

[http://sierrahelp.com/download.php?file=Files/SCI/GenericKeypadClass.zip Generic Keypad Class Files]

Lars

The Keypad SCI class<br />
Lars Skovlund<br />
January 17, 2007<br />
 

==1 Introduction==

This is the documentation for the Keypad SCI class, written by Lars Skovlund. I have attempted to make the class as general as possible. Therefore, the class and its descendant DisplayKeypad support arbitrarily long strings of any kind, so it is possible, for instance, to have each button represent a word so the user can construct sentences. The DisplayKeypad class prints the input string somewhere on the screen via the Display kernel call (all parameters are selectable via properties).

The following is a complete feature list for the keypad:

* No keyboard input, for generality reasons.
* Special button functionality, such as enter, backspace and cancel.
* Optionally invokes a script when initially showing the keypad and when the enter button is pressed.
* Optional auto exit mode in which the keypad triggers as soon as the input string reaches its maximum length, as if the user explicitly pressed the enter button.
* Can require a specific number of buttons to be pressed, or accept any number of button presses.
* Can play a sound when a button is pressed.
* Optional text display (DisplayKeypad).
* A background view can be used or not.

==2 Example of use==

===2.1 Declarations===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(local kptxt[5])

(instance myKeyPad of DisplayKeypad
(properties
maxLength 4
autoExit FALSE
script 0
longestText 1 /* one character */
color clBLACK
back clWHITE
x 20
y 160
requireMax TRUE
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key1 of KeypadButton
(properties
x 100
y 100
view 0
loop 0
text "1"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key2 of KeypadButton
(properties
x 120
y 100
view 0
loop 2
text "2"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key3 of KeypadButton
(properties
x 140
y 100
view 0
loop 1
text "3"
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key4 of KeypadButton
(properties
x 160
y 100
view 0
loop 5
special KEYPAD_SPECIAL_CANCEL
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key5 of KeypadButton
(properties
x 180
y 100
view 0
loop 6
special KEYPAD_SPECIAL_BKSP
)
)</syntaxhighlight>

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance key6 of KeypadButton
(properties
x 200
y 100
view 0
loop 3
special KEYPAD_SPECIAL_ENTER
)
)</syntaxhighlight>

===2.2 Handling the enter and cancel buttons===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance KeypadScript of Script
(properties)
(method (changeState newState)
(super:changeState(newState))
(switch (newState)
(case KEYPAD_DONE_STATE
((send client:hide(FALSE))
FormatPrint("You typed: %s" @kptxt)))
(case KEYPAD_ERROR_STATE
(FormatPrint("You need to press %d buttons."
(send client:maxLength()))))
)
)
)</syntaxhighlight>

===2.3 Initialization and activation===

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(myKeyPad:setScript(KeypadScript) outputString(@kptxt)
init(key1 key2 key3 key4 key5 key6))

(myKeyPad:init() show()) /* The init ensures that the keypad can
be used any number of times. */</syntaxhighlight>

==3 What to draw==

You will need a view consisting of several loops, one for each button. Each loop should contain two cels: The button in its normal and depressed state, respectively. It is important that the cels are ordered in this way; the code depends on it, and you should not set the cel property to anything when declaring KeypadButtons.

If you want a background view you can draw this as a separate loop. Declare it in your code as an instance of the Prop class. Then refer to it in your Keypad instance using the backView property.

==4 Class reference==

===4.1 Keypad class===

'''Superclass: EventHandler'''

This class provides the base functionality for keypads.

====''Methods of the Keypad class:''====

'''(Keypad init: buttons . . . )'''

This function initializes the object, as is the case with every SCI class. In particular, it resets the input string and notifies the controlling script. Buttons is a list of button views (instances of KeypadButton) to include in the keypad.

'''(Keypad show:)'''

Displays the keypad. The player is prevented from moving until the keypad is dismissed.

'''(Keypad hide: doCue)'''

Hides the keypad. DoCue should be set to TRUE if the “enter” button was pressed, FALSE otherwise. When the script is called, the buttons have not yet been removed from the screen. If you want this, your script must explicitly call hide with a FALSE parameter (to avoid infinite recursion)—this is what the example code does, see section 2.2.

'''(Keypad backspace:)'''

Self-explanatory. You will need to override this if you use text of varying lengths for the buttons.

'''(Keypad draw:)'''

'''(Keypad setSize:)'''

Do nothing. They are only here to prevent the game from crashing in certain situations (in particular, restoring the game to a position where the keypad is displayed).

'''(Keypad depress: which)'''

Simulates the pressing of a button. Which refers to an actual instance of KeypadButton.

'''(Keypad setScript: newScript params)'''

Sets the controlling script of the keypad. This script is called once when the keypad is initially displayed and once when the user presses “enter”. It is not called if the user cancels the dialog.

====''Properties of the Keypad class:''====

'''outputString''' Points to the output buffer. Remember to set this at run time, and remember that it must be big enough for anything the player might press. Use a local variable, as shown in section 2.1.

'''maxLength''' Indicates the length of the output buffer.

'''autoExit''' Boolean variable which toggles the “auto exit” mode, described in the introduction.

'''backView''' Points to an instance of Prop which is displayed when the keypad is activated. It is meant to be used for a background, hence the name.

'''backPri''' Indicates the priority of the background. May be omitted; the priority of the buttons is always 1 greater than this value, if specified.

'''btnSound''' Points to an instance of Sound which is played whenever the user presses a button.

'''longestText''' Indicates the length of the longest button text.

'''script''' Indicates the controlling script. Use setScript to set this, never set it directly.

'''state''' Boolean variable. Indicates whether the keypad is currently shown or not.

'''special''' Not used for anything. Works around a chicken-and-egg problem regarding selector names in SCI Studio.

'''requireMax''' Setting this to true makes the keypad require maxLength characters to be filled in. If this requirement is not met when the player presses enter, the attached script executes its keypad error state. You can do whatever you want here, including doing nothing, displaying an error message, or blowing up the universe. The keypad remains functional after the script returns.

;Notes

For the predefined script, three states are predefined. Constants are provided
in the enclosed header file.

===4.2 KeypadButton class===

'''Superclass: Prop'''

This class provides the button views to be used for the keypad; they provide an event handler and a special feed-back interface for the <u>Keypad</u> class. None of the overridden methods are meant to be called directly.

'''''Methods of the KeypadButton class:'''''

'''(KeypadButton init: theClient priority)'''

'''(KeypadButton handleEvent: event)'''

'''''Properties of the KeypadButton class:'''''

'''text''' The text to add when the button is pressed.

'''special''' The special meaning that this button is to have.

'''client''' A pointer to the keypad which “owns” this button. Filled in automatically.

;Notes

Three special button types are provided beside the default, namely enter, backspace and cancel.

===4.3 DisplayKeypad class===

'''Superclass: Keypad'''

This class provides the additional functionality of displaying the current text string at a predetermined position on the screen. All of the listed properties have the same format as those passed to the Display kernel function.

'''''Properties of the DisplayKeypad class:'''''

'''underBits''' stores a handle to the screen area under the text string.

'''x'''

'''y''' Coordinates where the text string is to be displayed.

'''font''' The font to use.

'''color''' The foreground color.

'''back''' The background color.

'''width''' The width to use for wrapping the text, if that should ever be necessary.

'''align''' The alignment to use.

==5 Constant reference==

(define KEYPAD_INIT_STATE 0)<br />
(define KEYPAD_DONE_STATE 1)<br />
(define KEYPAD_ERROR_STATE 2)

(define KEYPAD_SPECIAL_NONE 0)<br />
(define KEYPAD_SPECIAL_ENTER 1)<br />
(define KEYPAD_SPECIAL_BKSP 2)<br />
(define KEYPAD_SPECIAL_CANCEL 3)

 

[[Category:Keyboard]]
[[Category:Classes]]
[[Category:I/O]]
[[Category:Examples]]
[[Category:SCI Examples]]

Fixing F2 (ToggleSound) Issue with Companion

2025-04-02T21:29:07Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Fixing F2 (ToggleSound) Issue with Companion</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

As [[User:MusicallyInspired|Brandon]] has noted, sometimes it appears as though F2, or toggle sound, works and sometimes it does not. The problem arises out of sci companion's compiler. While there are no errors thrown, the compiled script fails to mute or unmute the sounds.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(procedure public (ToggleSound)
(var SOUND_OFF)
= SOUND_OFF DoSound(sndSET_SOUND)
= SOUND_OFF DoSound( sndSET_SOUND not(SOUND_OFF) )
(if(SOUND_OFF)
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn On")
)(else
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn Off")
)
)</syntaxhighlight>

Luckily, fixing the procedure isn't too difficult. The logic of the procedure, if you can play the sound then mute, otherwise unmute. Simple enough right? So here it is.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(procedure public (ToggleSound) // mute, unmute
(if(DoSound(sndSET_SOUND)) // if true, mute
DoSound(sndSET_SOUND FALSE)
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn On")
)
(else // must be false, unmute
DoSound(sndSET_SOUND TRUE)
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn Off")
)
)</syntaxhighlight>

Simply replace the whole procedure with this new one and the game will respond correctly regardless of which editor you use to compile the script.

 

[[Category:Troubleshooting]]
[[Category:SCI Troubleshooting]]
[[Category:Maintenance]]
[[Category:SCI Maintenance]]
[[Category:Audio]]
[[Category:SCI Audio]]
[[Category:Examples]]
[[Category:SCI Examples]]

SCI How To

2025-04-02T21:27:38Z

Andrew Branscom:

*[[Adding Sound Support]]
*[[Adding Troflip's alt Debugging]]
*[[Advanced Said() Strings - Part 2 - Qualifying Adjectives]]
*[[Advanced Said() Strings - Part 3 - Prepositions]]
*[[Automatic doors]]
*[[Death Handler]]
*[[Determining Location of Mouse Cursor]]
*[[Fixing F2 (ToggleSound) Issue with Companion]]
*[[Generic Keypad class]]
*[[Get and Use Specific Keyboard Keys]]
*[[How to keep your gTheSoundFX from interupting gTheMusic]]
*[[Manipulating the Parser - Part 1 - 'Complex' Nouns]]
*[[Manipulating the Parser - Part 2 - Addressing Actors]]
*[[Placing Inventory Descriptions in a Text Resource]]
*[[Resource Corruption from Rebuilding while Running]]
*[[Said() Strings - Comprehensive Examples]]
*[[Taking Inventory Item away from character]]
*[[Template Game Bug Fixes]]
*[[Timers]]
*[[Word Suffixes]]

 

[[Category:Examples]]

Fixing F2 (ToggleSound) Issue with Companion

2025-04-02T21:27:03Z

Andrew Branscom: Andrew Branscom moved page Fixing F2 (ToggleSound) issue with Companion to Fixing F2 (ToggleSound) Issue with Companion without leaving a redirect

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]
'''By Cloudee1'''

As [[User:MusicallyInspired|Brandon]] has noted, sometimes it appears as though F2, or toggle sound, works and sometimes it does not. The problem arises out of sci companion's compiler. While there are no errors thrown, the compiled script fails to mute or unmute the sounds.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(procedure public (ToggleSound)
(var SOUND_OFF)
= SOUND_OFF DoSound(sndSET_SOUND)
= SOUND_OFF DoSound( sndSET_SOUND not(SOUND_OFF) )
(if(SOUND_OFF)
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn On")
)(else
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn Off")
)
)</syntaxhighlight>

Luckily, fixing the procedure isn't too difficult. The logic of the procedure, if you can play the sound then mute, otherwise unmute. Simple enough right? So here it is.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(procedure public (ToggleSound) // mute, unmute
(if(DoSound(sndSET_SOUND)) // if true, mute
DoSound(sndSET_SOUND FALSE)
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn On")
)
(else // must be false, unmute
DoSound(sndSET_SOUND TRUE)
SetMenu(MENU_TOGGLESOUND smMENU_TEXT "Turn Off")
)
)</syntaxhighlight>

Simply replace the whole procedure with this new one and the game will respond correctly regardless of which editor you use to compile the script.

 

[[Category:Troubleshooting]]
[[Category:SCI Troubleshooting]]
[[Category:Maintenance]]
[[Category:SCI Maintenance]]
[[Category:Audio]]
[[Category:SCI Audio]]
[[Category:Examples]]
[[Category:SCI Examples]]

SCI How To

2025-04-02T21:26:34Z

Andrew Branscom:

*[[Adding Sound Support]]
*[[Adding Troflip's alt Debugging]]
*[[Advanced Said() Strings - Part 2 - Qualifying Adjectives]]
*[[Advanced Said() Strings - Part 3 - Prepositions]]
*[[Automatic doors]]
*[[Death Handler]]
*[[Determining Location of Mouse Cursor]]
*[[Fixing F2 (ToggleSound) issue with Companion]]
*[[Generic Keypad class]]
*[[Get and Use Specific Keyboard Keys]]
*[[How to keep your gTheSoundFX from interupting gTheMusic]]
*[[Manipulating the Parser - Part 1 - 'Complex' Nouns]]
*[[Manipulating the Parser - Part 2 - Addressing Actors]]
*[[Placing Inventory Descriptions in a Text Resource]]
*[[Resource Corruption from Rebuilding while Running]]
*[[Said() Strings - Comprehensive Examples]]
*[[Taking Inventory Item away from character]]
*[[Template Game Bug Fixes]]
*[[Timers]]
*[[Word Suffixes]]

 

[[Category:Examples]]

Determining Location of Mouse Cursor

2025-04-02T21:25:59Z

Andrew Branscom: Andrew Branscom moved page Determining location of mouse cursor to Determining Location of Mouse Cursor without leaving a redirect

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Determining Location of Mouse Cursor</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

This is a question that I recently asked at Mega-Tokyo in which Troflip was good enough to write up some code illustrating that exact functionality. This is a little snippet of code which I had hoped Troflip could enter here, but as he has not signed up yet and I really didn't want to lose this snippet as I plan to find a use for it, I have moved it here.

Troflip's code to get a view to follow the cursor broken up with small explanations added by me.

We first need to create an instance of an Actor, it needs to be an actor so that it can move around the screen. An init method has been included in the instance telling the actor to do what that script says.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">
(instance thing of Act
(properties
x 100
y 100
view 800
)
(method (init)
(super:init())
(self:setScript(thingScript))
)
)</syntaxhighlight>

Now that the instance is complete, we also need to create the script which the instances init method references.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance thingScript of Script
(properties)
(method (doit)
(var myEvent)
(super:doit())
(= myEvent Event:new(evNULL))
(send client:setMotion(MoveTo (send myEvent:x) (send myEvent:y)))
(send myEvent:dispose())
)
)</syntaxhighlight>

...and then of course do (thing:init()) in your room's init method.

 

[[Category:Cursors]]
[[Category:Mouse]]
[[Category:I/O]]
[[Category:SCI I/O]]
[[Category:Examples]]
[[Category:SCI Examples]]

Determining Location of Mouse Cursor

2025-04-02T21:25:39Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Determining Location of Mouse Cursor</span><br />
'''By Cloudee1'''</div>

<br />
==<br /> Introduction ==

This is a question that I recently asked at Mega-Tokyo in which Troflip was good enough to write up some code illustrating that exact functionality. This is a little snippet of code which I had hoped Troflip could enter here, but as he has not signed up yet and I really didn't want to lose this snippet as I plan to find a use for it, I have moved it here.

Troflip's code to get a view to follow the cursor broken up with small explanations added by me.

We first need to create an instance of an Actor, it needs to be an actor so that it can move around the screen. An init method has been included in the instance telling the actor to do what that script says.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">
(instance thing of Act
(properties
x 100
y 100
view 800
)
(method (init)
(super:init())
(self:setScript(thingScript))
)
)</syntaxhighlight>

Now that the instance is complete, we also need to create the script which the instances init method references.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(instance thingScript of Script
(properties)
(method (doit)
(var myEvent)
(super:doit())
(= myEvent Event:new(evNULL))
(send client:setMotion(MoveTo (send myEvent:x) (send myEvent:y)))
(send myEvent:dispose())
)
)</syntaxhighlight>

...and then of course do (thing:init()) in your room's init method.

 

[[Category:Cursors]]
[[Category:Mouse]]
[[Category:I/O]]
[[Category:SCI I/O]]
[[Category:Examples]]
[[Category:SCI Examples]]

Death Handler

2025-04-02T21:24:03Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Death Handler</span><br />
'''By Cloudee1'''</div>

==<br /> Examples of Utilizing the Death Handler ==

Most cases of a death event can be done in the same way, by adding in a doit method. For instance being too close to a character or view, crossing a road or perhaps standing in the wrong spot, like under a piano. Would all be handled in the doit method.

Kill the character whenever something else gets too close. We will of course need to have an instance of the oPPonent actor, as well as having it inited, but otherwise to activate the death script.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(method (doit)
(var dyingScript) // don't forget this line
(super:doit())

(if(not(gProgramControl))
(if(< (send gEgo:distanceTo(oPPonent)) 40)
ProgramControl()
// (oPPonent:cel(0)loop(4)setMotion(NULL)setCycle(Fwd)) // switch opponent to attacking
// (send gEgo:view(1)cel(0)setMotion(NULL)setCycle(Fwd))// switch ego to getting attacked

= dyingScript ScriptID(DYING_SCRIPT)
(send dyingScript:
caller(3)
register("You're dead")
)
(send gGame:setScript(dyingScript))
)
)
) // end method</syntaxhighlight>

Similarly, if ego were to attempt crossing an uncrossable road. Rather than measure the distance between ego and something you can just simply lay down say a purple control color line on the road where ego can't cross. For this you will still need a doit method but the car which is still an actor since we need to apply motion to it, but you won't need to init it when you do all the normal things, but rather right when it's needed, after all, it may never actually be needed.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(method (doit)
(var dyingScript)
(super:doit())

(if(not(gProgramControl))
(if(== (send gEgo:onControl()) $0021)// purple and black
ProgramControl()
(oPPonent:cel(0)loop(4)setMotion(walk)MoveTo(0 165)init()) // Car starts down road
(send gEgo:view(1)cel(0)setMotion(NULL)setCycle(End))// switch ego to getting hit

= dyingScript ScriptID(DYING_SCRIPT)
(send dyingScript:
caller(3)
register("You're dead")
)
(send gGame:setScript(dyingScript))

)
)
) // end method</syntaxhighlight>

Another way of doing it would also be to check if ego was in a rectangle and whenever they are trigger the events. It's exactly the last two examples except the beginning if statement, which is essentially what typing the word die in is in that section of the tutorial, it is simply the trigger to start the death event. The best way by far, giving the most room for animations is to place the death handler at the end of a changestate.

 

[[Category:Death]]
[[Category:Events]]
[[Category:SCI Events]]
[[Category:Examples]]
[[Category:SCI Examples]]

Death Handler

2025-04-02T21:23:42Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Death Handler</span><br />
'''By Cloudee1'''</div>

== Examples of Utilizing the Death Handler ==

Most cases of a death event can be done in the same way, by adding in a doit method. For instance being too close to a character or view, crossing a road or perhaps standing in the wrong spot, like under a piano. Would all be handled in the doit method.

Kill the character whenever something else gets too close. We will of course need to have an instance of the oPPonent actor, as well as having it inited, but otherwise to activate the death script.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(method (doit)
(var dyingScript) // don't forget this line
(super:doit())

(if(not(gProgramControl))
(if(< (send gEgo:distanceTo(oPPonent)) 40)
ProgramControl()
// (oPPonent:cel(0)loop(4)setMotion(NULL)setCycle(Fwd)) // switch opponent to attacking
// (send gEgo:view(1)cel(0)setMotion(NULL)setCycle(Fwd))// switch ego to getting attacked

= dyingScript ScriptID(DYING_SCRIPT)
(send dyingScript:
caller(3)
register("You're dead")
)
(send gGame:setScript(dyingScript))
)
)
) // end method</syntaxhighlight>

Similarly, if ego were to attempt crossing an uncrossable road. Rather than measure the distance between ego and something you can just simply lay down say a purple control color line on the road where ego can't cross. For this you will still need a doit method but the car which is still an actor since we need to apply motion to it, but you won't need to init it when you do all the normal things, but rather right when it's needed, after all, it may never actually be needed.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(method (doit)
(var dyingScript)
(super:doit())

(if(not(gProgramControl))
(if(== (send gEgo:onControl()) $0021)// purple and black
ProgramControl()
(oPPonent:cel(0)loop(4)setMotion(walk)MoveTo(0 165)init()) // Car starts down road
(send gEgo:view(1)cel(0)setMotion(NULL)setCycle(End))// switch ego to getting hit

= dyingScript ScriptID(DYING_SCRIPT)
(send dyingScript:
caller(3)
register("You're dead")
)
(send gGame:setScript(dyingScript))

)
)
) // end method</syntaxhighlight>

Another way of doing it would also be to check if ego was in a rectangle and whenever they are trigger the events. It's exactly the last two examples except the beginning if statement, which is essentially what typing the word die in is in that section of the tutorial, it is simply the trigger to start the death event. The best way by far, giving the most room for animations is to place the death handler at the end of a changestate.

 

[[Category:Death]]
[[Category:Events]]
[[Category:SCI Events]]
[[Category:Examples]]
[[Category:SCI Examples]]

Death Handler

2025-04-02T21:22:57Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Death Handler</span><br />
'''By '''</div><br />
'''By Cloudee1'''</div>

== Examples of Utilizing the Death Handler ==

Most cases of a death event can be done in the same way, by adding in a doit method. For instance being too close to a character or view, crossing a road or perhaps standing in the wrong spot, like under a piano. Would all be handled in the doit method.

Kill the character whenever something else gets too close. We will of course need to have an instance of the oPPonent actor, as well as having it inited, but otherwise to activate the death script.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(method (doit)
(var dyingScript) // don't forget this line
(super:doit())

(if(not(gProgramControl))
(if(< (send gEgo:distanceTo(oPPonent)) 40)
ProgramControl()
// (oPPonent:cel(0)loop(4)setMotion(NULL)setCycle(Fwd)) // switch opponent to attacking
// (send gEgo:view(1)cel(0)setMotion(NULL)setCycle(Fwd))// switch ego to getting attacked

= dyingScript ScriptID(DYING_SCRIPT)
(send dyingScript:
caller(3)
register("You're dead")
)
(send gGame:setScript(dyingScript))
)
)
) // end method</syntaxhighlight>

Similarly, if ego were to attempt crossing an uncrossable road. Rather than measure the distance between ego and something you can just simply lay down say a purple control color line on the road where ego can't cross. For this you will still need a doit method but the car which is still an actor since we need to apply motion to it, but you won't need to init it when you do all the normal things, but rather right when it's needed, after all, it may never actually be needed.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(method (doit)
(var dyingScript)
(super:doit())

(if(not(gProgramControl))
(if(== (send gEgo:onControl()) $0021)// purple and black
ProgramControl()
(oPPonent:cel(0)loop(4)setMotion(walk)MoveTo(0 165)init()) // Car starts down road
(send gEgo:view(1)cel(0)setMotion(NULL)setCycle(End))// switch ego to getting hit

= dyingScript ScriptID(DYING_SCRIPT)
(send dyingScript:
caller(3)
register("You're dead")
)
(send gGame:setScript(dyingScript))

)
)
) // end method</syntaxhighlight>

Another way of doing it would also be to check if ego was in a rectangle and whenever they are trigger the events. It's exactly the last two examples except the beginning if statement, which is essentially what typing the word die in is in that section of the tutorial, it is simply the trigger to start the death event. The best way by far, giving the most room for animations is to place the death handler at the end of a changestate.

 

[[Category:Death]]
[[Category:Events]]
[[Category:SCI Events]]
[[Category:Examples]]
[[Category:SCI Examples]]

Automatic Doors

2025-04-02T21:21:51Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Automatic doors</span><br />
'''By Cloudee1'''</div>

==<br /> Introduction ==

When using Doors and AutoDoors, I am not sure why but things always seemed to go awry. This little tutorial will have a simple Automatic Door (when the player walks near them, they open) up and running with two simple lines of code.

We begin at the very top of the script. We will need to tell the script that we are going to be using an automatic door and to include that functionality. This is done simply by adding in another use command where all of the others are.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(use "autodoor")</syntaxhighlight>

Now that one line is finished, lets go on to the second one, the hard one. Just kidding, there is nothing hard to this method of using automatic doors. The script can now handle AutoDoor instances now, but we are not making one of those, at least not the traditional way. In the rooms init method, where you init() your rooms views and actors, you will need to add in the call that inits the automatic door. the parameters are of the basic type, and I don't think it's necessary to go into detail about them.

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">(send (AutoDoor:new()):view(211)
setLoop(0)
posn(161 62)
setPri(2)
entranceTo(101)
init())</syntaxhighlight>

At this point, as long as you have added the doors view, and have set up the doors control colors Navy and Green (you won't need a Yellow one because this type of door does not get blocked) for when to open or transport to a new room. We don't need to create an instance or anything else, we are all done coding.

This simple type of door has some limitations though, because there is not an instance name to reference you won't be able to program interactions with it as the code stands now. So keep this in mind. This door can't be locked or blocked, if all you need is a door that opens when you near it, then this will work.

For more advanced needs, such as multiple doors in the same room, see [[Advanced Use of Control Areas]]

 

[[Category:Doors]]
[[Category:Control Areas]]
[[Category:SCI Control Areas]]
[[Category:Props]]
[[Category:SCI Props]]
[[Category:Examples]]
[[Category:SCI Examples]]

Automatic Doors

2025-04-02T21:21:34Z

Andrew Branscom:

Advanced Said() Strings - Part 3 - Prepositions

2025-04-02T21:20:18Z

Andrew Branscom:

[[Category:SCI Pages]]
[[Category:Temp SCI Import Pages]]
[[Category:Temp SCI Tutorials]]
[[SCI Tutorials]]
[[SCI Tutorials and Guides]]

<div align="center"><span style="font-size: 22pt">Advanced Said() Strings - Part 3 - Prepositions</span><br />
'''By Gumby'''</div>

<br />
==<br /> Prepositions (and Unclassified words) ==

Example of the preposition 'in', which is classified in the vocab as a preposition (in the template game):
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci"> // Responds to user input of: 'put key in lock'
(if(Said('put<in/key/lock'))
Print("You put the key in the lock")
)</syntaxhighlight>

Example of the preposition 'with', but has an unclassified word class in the template game:

<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci"> // Responds to user input of: 'open door with key'
(if(Said('open/door/key<with'))
Print("You open the door with the key")
)</syntaxhighlight>

Don't despair with this discrepancy. By setting 'with' to a preposition it will behave just like the 'in' preposition example.

 

[[Category:Prepositions]]
[[Category:SCI Prepositions]]
[[Category:Said() Strings]]
[[Category:SCI Said() Strings]]
[[Category:The Parser]]
[[Category:The SCI Parser]]
[[Category:Examples]]
[[Category:SCI Examples]]