Riven engine overview - Revision history

TitoDalCanton: Protected "Riven engine overview" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2011-11-19T20:50:43Z

Protected "Riven engine overview" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Tahg: added trap book card switch

2009-05-23T00:19:46Z

added trap book card switch

Clone2727: add Riven template here too

2008-09-07T22:42:02Z

add Riven template here too

Clone2727: the Riven demo uses just one archive for jspit's data

2008-09-05T19:29:06Z

the Riven demo uses just one archive for jspit's data

Clone2727: /* Notes on stack switching */ the DVD version uses a slightly different table for the special stack switching

2008-09-04T20:37:12Z

‎Notes on stack switching: the DVD version uses a slightly different table for the special stack switching

TitoDalCanton: the association is found in Riven.ini

2008-07-15T12:18:09Z

the association is found in Riven.ini

Clone2727: adding stack ID conversion for saved games

2008-07-14T17:27:50Z

adding stack ID conversion for saved games

TitoDalCanton: added link to the debug shell page

2008-04-06T10:10:49Z

added link to the debug shell page

Di gama: the stack switching notes have to go somewhere, if not the 'other' page

2008-02-12T22:06:21Z

the stack switching notes have to go somewhere, if not the 'other' page

TitoDalCanton: initial import

2008-02-09T15:01:17Z

initial import

New page

A Riven scenario is made of virtual objects called ''stacks'' and each stack is a list of virtual objects called ''cards''. This may remember HyperCard: it's the same approach. Each card has an associated ''script'', a sequence of commands to be executed in response of events happening to the card (for example, card creation). The player interacts with the game by means of invisible buttons, placed within cards and called ''hotspots''. Hotspots have associated scripts too, responding to events different than cards (for example, mouse clicks). Within cards can also be placed bitmaps and movies. Finally, sounds can be played.

Riven stacks are named
*aspit (main menu, books, setup screens)
*bspit (boiler island)
*gspit (garden island)
*jspit (jungle island)
*ospit (Gehn's office)
*pspit (prison island)
*rspit (rebel age)
*tspit (temple island).

Physically, a stack is described by a set of data blocks called ''resources''. Resources are identified by a 4-char ''type'' and an integer ''ID''. Optionally they can also have a name, but it seems completely ignored by the engine. The resource type tells what kind of data is stored in the resource; see the [[Riven_resources|resource type list]] for types used in Riven.

Resources belonging to a certain stack are archived inside an arbitrary number of [[Mohawk_archive_format|Mohawk files]]. The file "riven.cfg" tells which files compose each stack by associating stack and file names.

Saved games are Mohawk archives too, and they contain additional resource types as described in the [[Riven_resources|resource type list]].

@@ Line 76: / Line 76: @@
 |- style="background:#CCC"
 ! Stack !! Card ID !! Target stack !! Target card
 |-
 |bspit||447||ospit||1

← Older revision		Revision as of 22:42, 7 September 2008
Line 1:		Line 1:
		+	{{Riven}}
		+
	A Riven scenario is made of virtual objects called ''stacks'' and each stack is a list of virtual objects called ''cards''. This may remember HyperCard: it's the same approach. Each card has an associated ''script'', a sequence of commands to be executed in response of events happening to the card (for example, card creation). The player interacts with the game by means of invisible buttons, placed within cards and called ''hotspots''. Hotspots have associated scripts too, responding to events different than cards (for example, mouse clicks). Within cards can also be placed bitmaps and movies. Finally, sounds can be played.		A Riven scenario is made of virtual objects called ''stacks'' and each stack is a list of virtual objects called ''cards''. This may remember HyperCard: it's the same approach. Each card has an associated ''script'', a sequence of commands to be executed in response of events happening to the card (for example, card creation). The player interacts with the game by means of invisible buttons, placed within cards and called ''hotspots''. Hotspots have associated scripts too, responding to events different than cards (for example, mouse clicks). Within cards can also be placed bitmaps and movies. Finally, sounds can be played.

@@ Line 18: / Line 18: @@
 **r_Sounds.mhk
 *tspit (temple island).
-**t_Data.mhk (Riven 5CD)
+**t_Data.mhk (Riven 5CD/Demo)
 **t_Data1.mhk, t_Data2.mhk (Riven DVD)
 **t_Sounds.mhk
 *jspit (jungle island)
-**j_Data1.mhk
+**j_Data.mhk (Riven Demo)
-**j_Data2.mhk
+**j_Data1.mhk, j_Data2.mhk (Riven 5CD/DVD)
 **j_Sounds.mhk
 *bspit (boiler island)

@@ Line 39: / Line 39: @@
 ==Notes on stack switching==
 The current stack can be changed from scripts using [[Riven scripts#Command 27: go to stack|script command 27]]. For example, when the player activates a MagLev, first the car movie is played, and then command 27 is called to change the current stack to the new island. This command is also used in the "Play Riven" button. However, most linking books actually change stack simply by moving to another card which has no buttons and no scripts. Apparently, there is some hardcoded mechanism inside the engine which triggers the stack change when one of these "special" cards is entered. These cards are listed here.
 {| border=1 cellpadding=4 cellspacing=0 style="border:1px #000 solid;border-collapse:collapse;"
 |- style="background:#CCC"
@@ Line 66: / Line 68: @@
 |-
 |tspit||392||ospit||1
 |}

← Older revision		Revision as of 12:18, 15 July 2008
Line 91:		Line 91:
	\|8\|\|aspit		\|8\|\|aspit
	\|}		\|}
		+
		+	Such association seems to be defined in the Riven.ini file, in particular from its "StackNumber" section.

← Older revision	Revision as of 20:50, 19 November 2011
(No difference)

← Older revision		Revision as of 10:10, 6 April 2008
Line 34:		Line 34:

	Saved games are Mohawk archives too, and they contain additional resource types as described in the [[Riven_resources\|resource type list]].		Saved games are Mohawk archives too, and they contain additional resource types as described in the [[Riven_resources\|resource type list]].
		+
		+	The Riven engine has a secret, interesting [[Riven_debug_shell\|debug shell]].

	==Notes on stack switching==		==Notes on stack switching==

@@ Line 3: / Line 3: @@
 Riven stacks are named
 *aspit (main menu, books, setup screens)
-*bspit (boiler island)
+**a_Data.mhk
-*gspit (garden island)
+**a_Sounds.mhk
-*jspit (jungle island)
 *ospit (Gehn's office)
 *pspit (prison island)
 *rspit (rebel age)
 *tspit (temple island).
 Physically, a stack is described by a set of data blocks called ''resources''. Resources are identified by a 4-char ''type'' and an integer ''ID''. Optionally they can also have a name, but it seems completely ignored by the engine. The resource type tells what kind of data is stored in the resource; see the [[Riven_resources|resource type list]] for types used in Riven.
-Resources belonging to a certain stack are archived inside an arbitrary number of [[Mohawk_archive_format|Mohawk files]]. The file "riven.cfg" tells which files compose each stack by associating stack and file names.
+Resources belonging to a certain stack are archived inside an arbitrary number of [[Mohawk_archive_format|Mohawk files]] (listed above under their respective stacks). The file "riven.cfg" tells which files compose each stack by associating stack and file names.
 Saved games are Mohawk archives too, and they contain additional resource types as described in the [[Riven_resources|resource type list]].